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, AwsResponseRetryClassifier>, 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 of the IAM role that allows Amazon EC2 to publish flow logs to a CloudWatch Logs log group in your account.

This parameter is required if the destination type is cloud-watch-logs and unsupported otherwise.

source

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

The ARN of the IAM role that allows Amazon EC2 to publish flow logs across accounts.

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.

This parameter is valid only if the destination type is cloud-watch-logs.

source

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

The IDs of the resources to monitor. For example, if the resource type is VPC, specify the IDs of the VPCs.

Constraints: Maximum of 25 for transit gateway resource types. Maximum of 1000 for the other resource types.

source

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

The type of resource to monitor.

source

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

The type of traffic to monitor (accepted traffic, rejected traffic, or all traffic). This parameter is not supported for transit gateway resource types. It is required for the other resource types.

source

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

The type of destination for the flow log data.

Default: cloud-watch-logs

source

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

The destination for the flow log data. The meaning of this parameter depends on the destination type.

If the destination type is cloud-watch-logs, specify the ARN of a CloudWatch Logs log group. For example:

arn:aws:logs:region:account_id:log-group:my_group

Alternatively, use the LogGroupName parameter.
If the destination type is s3, specify the ARN of an S3 bucket. For example:

arn:aws:s3:::my_bucket/my_subfolder/

The subfolder is optional. Note that you can't use AWSLogs as a subfolder name.
If the destination type is kinesis-data-firehose, specify the ARN of a Kinesis Data Firehose delivery stream. For example:

arn:aws:firehose:region:account_id:deliverystream:my_stream

source

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

The fields to include in the flow log record. List the fields in the order in which they should appear. If you omit this parameter, the flow log is created using the default format. If you specify this parameter, you must include at least one field. For more information about the available fields, see Flow log records in the Amazon VPC User Guide or Transit Gateway Flow Log records in the Amazon Web Services Transit Gateway Guide.

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. The possible values are 60 seconds (1 minute) or 600 seconds (10 minutes). This parameter must be 60 seconds for transit gateway resource types.

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