A company has deployed an application on Amazon EC2 instances in a single VPC. The company has placed the EC2 instances in a private subnet in the VPC. The EC2 instances need access to Amazon S3…

Question

Options

• ACreate an S3 gateway endpoint that uses the default gateway endpoint policy. Associate the
• BCreate an S3 interface endpoint. Associate the EC2 instances with the interface endpoint.
• CConfigure a NAT gateway. Associate the private subnet with the NAT gateway.
• DConfigure a proxy EC2 instance. Update the private subnet route tables to route traffic through

• A
  81% (17)
• B
  5% (1)
• C
  5% (1)
• D
  10% (2)

Explanation

Amazon S3 supports both gateway endpoints and interface endpoints. With a gateway endpoint, you can access Amazon S3 from your VPC, without requiring an internet gateway or NAT device for your VPC, and with no additional cost. However, gateway endpoints do not allow access from on-premises networks, from peered VPCs in other AWS Regions, or through a transit gateway. For those scenarios, you must use an interface endpoint, which is available for an additional cost. https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html Interface endpoints - These endpoints are directly accessible from applications that are on premises over VPN and AWS Direct Connect, or in a different AWS Region over VPC peering. https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html

No community discussion yet for this question.