A SysOps Administrator is investigating malicious outbound HTTP traffic originating from a VPC. Multiple Amazon EC2 instances reside in private subnets and route their outbound traffic to the internet through a NAT Gateway. The administrator has enabled VPC Flow Logs on the public subnet's network interface where the NAT Gateway resides. However, in the default flow logs, the `srcaddr` field for all outbound packets shows the NAT Gateway's private IP address, making it impossible to identify which specific EC2 instance is generating the malicious traffic.
The administrator wants to resolve this issue and successfully configure the logs to be published to a CloudWatch Logs log group.
Which of the following actions should the administrator take to achieve this? (Select TWO.)
- Create a new VPC Flow Log with a custom format that includes the `pkt-srcaddr` field to capture the original packet-level source IP address of the traffic passing through the NAT Gateway.Cevap
- Create a new VPC Flow Log targeting the private subnets where the EC2 instances reside to capture the traffic at the instance network interfaces before NAT translation.Cevap
- CCreate the CloudWatch Logs delivery role and assign the `sts:AssumeRole` action to the administrator's IAM policy, omitting the `iam:PassRole` action as it is not required for VPC Flow Logs creation.
- DModify the route tables of the private subnets to delete the S3 Gateway Endpoint and route all S3-bound traffic through the NAT Gateway so that all outbound traffic is consolidated and captured in the public subnet's default flow logs.
- ECreate the CloudWatch Logs log group and set its retention policy to 'Never expire' to ensure the logs are not deleted, as CloudWatch log groups default to a 14-day retention limit that cannot be modified after the group is created.