Multi-VPC ENI Attachments
AWS announces the general availability of multi-Virtual Private Cloud (VPC) elastic network interface (ENI) attachments for Amazon Elastic Compute Cloud (EC2) instances. With this capability, customers can now launch an instance with a primary ENI in one VPC and attach a secondary ENI from another VPC. With multi-VPC ENI attachments, customers can maintain VPC level segregation between networks, while allowing select workloads like centralized appliances and databases to communicate between them.
AWS announces the general availability of multi-Virtual Private Cloud (VPC) elastic network interface (ENI) attachments for Amazon Elastic Compute Cloud (EC2) instances. With this capability, customers can now launch an instance with a primary ENI in one VPC and attach a secondary ENI from another VPC. With multi-VPC ENI attachments, customers can maintain VPC level segregation between networks, while allowing select workloads like centralized appliances and databases to communicate between them.
Customers such as telecommunication providers that send different types of network traffic within AWS regions as well as between on-premises and AWS need logical separation for their workload. Using different VPCs for different types of network traffic such as control and data plane traffic, customers can now segment their traffic at the VPC level, while shared workloads like virtual routers, firewalls, and databases can maintain connectivity between the two. With multi-VPC ENI attachments, customers can run connected workloads between these otherwise segmented VPCs to ensure specific functions can communicate with each VPC.
Multi-VPC ENI attachments are now available in all commercial regions, the AWS GovCloud (US) Regions, and the Amazon Web Services China (Beijing) Region, operated by Sinnet and Amazon Web Services China (Ningxia) Region, operated by NWCD. For more information, please visit the EC2 user guide.