Struct aws_sdk_ec2::input::CreateFlowLogsInput

source · [−]

#[non_exhaustive]
pub struct CreateFlowLogsInput { /* private fields */ }

Implementations

source

impl CreateFlowLogsInput

source

pub async fn make_operation(
&self,
_config: &Config
) -> Result<Operation<CreateFlowLogs, AwsErrorRetryPolicy>, BuildError>

Consumes the builder and constructs an Operation<CreateFlowLogs>

source

pub fn builder() -> Builder

Creates a new builder-style object to manufacture CreateFlowLogsInput.

source

Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.

source

pub fn client_token(&self) -> Option<&str>

Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. For more information, see How to ensure idempotency.

source

pub fn deliver_logs_permission_arn(&self) -> Option<&str>

The ARN for the IAM role that permits Amazon EC2 to publish flow logs to a CloudWatch Logs log group in your account.

If you specify LogDestinationType as s3, do not specify DeliverLogsPermissionArn or LogGroupName.

source

pub fn log_group_name(&self) -> Option<&str>

The name of a new or existing CloudWatch Logs log group where Amazon EC2 publishes your flow logs.

If you specify LogDestinationType as s3, do not specify DeliverLogsPermissionArn or LogGroupName.

source

pub fn resource_ids(&self) -> Option<&[String]>

The ID of the subnet, network interface, or VPC for which you want to create a flow log.

Constraints: Maximum of 1000 resources

source

pub fn resource_type(&self) -> Option<&FlowLogsResourceType>

The type of resource for which to create the flow log. For example, if you specified a VPC ID for the ResourceId property, specify VPC for this property.

source

pub fn traffic_type(&self) -> Option<&TrafficType>

The type of traffic to log. You can log traffic that the resource accepts or rejects, or all traffic.

source

pub fn log_destination_type(&self) -> Option<&LogDestinationType>

The type of destination to which the flow log data is to be published. Flow log data can be published to CloudWatch Logs or Amazon S3. To publish flow log data to CloudWatch Logs, specify cloud-watch-logs. To publish flow log data to Amazon S3, specify s3.

If you specify LogDestinationType as s3, do not specify DeliverLogsPermissionArn or LogGroupName.

Default: cloud-watch-logs

source

pub fn log_destination(&self) -> Option<&str>

The destination to which the flow log data is to be published. Flow log data can be published to a CloudWatch Logs log group or an Amazon S3 bucket. The value specified for this parameter depends on the value specified for LogDestinationType.

If LogDestinationType is not specified or cloud-watch-logs, specify the Amazon Resource Name (ARN) of the CloudWatch Logs log group. For example, to publish to a log group called my-logs, specify arn:aws:logs:us-east-1:123456789012:log-group:my-logs. Alternatively, use LogGroupName instead.

If LogDestinationType is s3, specify the ARN of the Amazon S3 bucket. You can also specify a subfolder in the bucket. To specify a subfolder in the bucket, use the following ARN format: bucket_ARN/subfolder_name/. For example, to specify a subfolder named my-logs in a bucket named my-bucket, use the following ARN: arn:aws:s3:::my-bucket/my-logs/. You cannot use AWSLogs as a subfolder name. This is a reserved term.

source

pub fn log_format(&self) -> Option<&str>

The fields to include in the flow log record, in the order in which they should appear. For a list of available fields, see Flow log records. If you omit this parameter, the flow log is created using the default format. If you specify this parameter, you must specify at least one field.

Specify the fields using the ${field-id} format, separated by spaces. For the CLI, surround this parameter value with single quotes on Linux or double quotes on Windows.

source

pub fn tag_specifications(&self) -> Option<&[TagSpecification]>

The tags to apply to the flow logs.

source

pub fn max_aggregation_interval(&self) -> Option<i32>

The maximum interval of time during which a flow of packets is captured and aggregated into a flow log record. You can specify 60 seconds (1 minute) or 600 seconds (10 minutes).

When a network interface is attached to a Nitro-based instance, the aggregation interval is always 60 seconds or less, regardless of the value that you specify.

Default: 600

source