Amazon Web Services expanded functionality of Amazon Virtual Private Cloud (Amazon VPC).
Before today, customers of Amazon EC2 could provision a private, isolated section of the AWS cloud (called an Amazon VPC) and launch AWS resources into that VPC that were only accessible via a Virtual Private Network connection to an existing enterprise datacenter. Amazon VPC wasn’t directly accessible to the Internet. With today’s announcement enterprises no longer need a VPN or existing infrastructure resources in order to leverage Amazon VPC.
Enterprises can now define a virtual network topology in Amazon VPC that closely resembles a traditional network that they might operate in their own datacenter. Customers have complete control over the VPN environment, including selection of IP address range, creation of subnets, and configuration of route tables and network gateways. Users can easily customize the network configuration for Amazon VPC, for e.g. creating a public-facing subnet for web servers that’ve access to the Internet, and placing backend systems such as databases or app servers in a private-facing subnet with no Internet access. Enterprises can continue to choose to connect Amazon VPC to their own existing IT infrastructure with an encrypted VPN connection, extending enterprises’ existing security and management policies to Amazon VPC instances as if they were running within an existing datacenter.
To learn more and to get started using visit, Amazon VPC.