to allow an instance in your VPC to initiate outbound connections to
the
internet but prevent unsolicited inbound connections from the internet, you can
use
a network address translation (NAT) device for IPv4 traffic
A NAT device has an Elastic
IP address and is connected to the internet through an internet gateway.
By default, each instance that you launch into a nondefault subnet has a private IPv4
address, but no public IPv4 address, unless you specifically assign one at launch,
or you modify the subnet's public IP address attribute.
Amazon VPC is the networking layer for Amazon EC2.
A virtual private cloud (VPC) is a virtual network dedicated to your
AWS account. It is logically isolated from other virtual networks in the AWS Cloud.
Instances can connect to the internet over IPv6
through an internet gateway
IPv6 traffic is separate from
IPv4 traffic; your route tables must include separate routes for IPv6
traffic.
You can optionally connect your VPC to your own corporate data center using an IPsec
AWS
managed VPN connection, making the AWS Cloud an extension of your data
center.
A VPN connection consists of a virtual private gateway attached to your VPC and a
customer gateway located in your data center.
A virtual private gateway is the
VPN
concentrator on the Amazon side of the VPN connection. A customer gateway is a
physical device or software appliance on your side of the VPN connection.
AWS PrivateLink is a highly available, scalable technology that enables you to privately
connect your VPC to supported AWS services, services hosted by other AWS
accounts (VPC endpoint services)
Traffic between your VPC and the
service does not leave the Amazon network
To use AWS PrivateLink, create an interface VPC endpoint for a service in your VPC.
This
creates an elastic network interface in your subnet with a private IP address that
serves as an entry point for traffic destined to the service.
create your own AWS PrivateLink-powered service (endpoint service) and enable
other AWS customers to access your service.