Private EC2 Instances in VPC without Internet Gateway, NAT Device, Public IP, or VPN
Question
Which of the following allows private EC2 Instances in your VPC have the ability to work with AWS resources without the need of an an internet gateway, NAT device, public IP address, or VPN connection.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - C.
The AWS documentation mentions the following.
AWS PrivateLink is a highly available, scalable technology that enables you to privately access some AWS services from your VPC.
You do not require an internet gateway, NAT device, public IP address, or VPN connection to communicate with the supported AWS service.
Traffic between your VPC and the service does not leave the Amazon network.
For more information on the PrivateLink, please refer to the below URL:
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Introduction.html#what-is-privatelinkThe correct answer is C. PrivateLink.
PrivateLink is a service that allows you to securely access AWS services from your VPC without requiring an internet gateway, NAT device, public IP address, or VPN connection. With PrivateLink, you can access AWS services via private IP addresses in your VPC, which allows you to keep all traffic between your VPC and the AWS service within the AWS network.
VPCLink and AWSLink are not valid AWS services. PublicLink is a service that allows you to expose your own services to other AWS accounts or VPCs over the AWS network, but it is not relevant to the question.
In summary, PrivateLink provides a secure and efficient way to access AWS services from your VPC without requiring any internet-facing infrastructure, which is especially useful when dealing with sensitive data or compliance requirements.
