|
Today, we introduced direct VPC routing for AWS Outposts rack. This lets you join Outposts racks and on-premises networks utilizing simplified IP handle administration. Direct VPC routing robotically advertises Amazon Virtual Private Cloud (Amazon VPC) subnet CIDR addresses to on-premises networks. This lets you use the personal IP addresses of sources in your VPC when speaking together with your on-premises community. Furthermore, you’ll be able to allow direct VPC routing utilizing a self-serve course of while not having to contact AWS.
If you’re unfamiliar, AWS Outposts rack, part of the Outposts household, is a fully-managed service that provides the identical AWS infrastructure, AWS providers, APIs, and instruments to nearly any on-premises datacenter or co-location house for a constant hybrid expertise. They’re perfect for workloads that require low-latency entry to on-premises techniques, native information processing, information residency, and migration of purposes with native system interdependencies. Once put in, your Outposts rack turns into an extension of your VPC, and it’s managed utilizing the identical APIs, instruments, and administration controls that you simply already use within the cloud.
With direct VPC routing, you now have two choices to configure and join your Outposts rack to your on-premises networks. Previously, to configure community routing between an on-premises community and an Outposts rack, you wanted to make use of Customer-owned IP addresses (CoIP). During an Outposts rack set up, this concerned offering a separate IP handle vary/CIDR out of your on-premises community for AWS to create an handle pool, which is called a CoIP pool. When an Amazon Elastic Compute Cloud (Amazon EC2) occasion in your Outposts rack wanted to speak together with your on-premises community, Outposts rack would carry out a 1:1 community handle translation (NAT) from the VPC personal IP handle to a CoIP handle within the CoIP pool. Using CoIP implies that it’s essential to handle each VPC and CoIP handle swimming pools, with out overlap, and configure route propagation between the 2 units of addresses. When including a subnet to a VPC, you additionally wanted to observe a number of steps to replace route propagation between your networks to acknowledge the brand new subnet addresses.
Managing IP handle ranges for AWS cloud and onsite sources, in addition to coping with CoIP ranges on Outposts rack, may be an operational burden. Although the choice to make use of CoIP remains to be out there and can proceed to be absolutely supported, the brand new direct VPC routing choice simplifies your IP handle administration. Automatic commercial of CIDR addresses for subnets, together with new subnets added sooner or later, between the VPC and your Outposts rack, removes the necessity so that you can reconfigure IP addresses. This additionally retains route propagation up-to-date, thereby saving you effort and time. Furthermore, as talked about earlier, you’ll be able to allow all of this with a self-serve choice.
Enabling Direct VPC Routing
You can choose both CoIP or direct VPC routing approaches and make the most of a brand new self-service API, CreateLocalGatewayRouteTable, to configure direct VPC routing for each new and present Outposts racks. This eliminates the necessity to contact AWS to allow the configuration. To allow direct VPC routing, merely set the mode property within the CreateLocalGatewayRouteTable API’s request parameters to the worth direct-vpc-routing. If you’re already utilizing CoIP, then it’s essential to delete and recreate the route desk that’s propagating visitors between the Outposts rack and your on-premises community.
The following instance diagram, taken from the consumer information, illustrates the setup for an Outposts rack working a number of Amazon EC2 situations and linked to an on-premises community, with automated handle commercial. Note that personal IP handle ranges are utilized throughout the Outposts rack sources and the on-premises community.
Get began with Direct VPC Routing right this moment
The choice to allow direct VPC routing is obtainable now for each new and present Outposts racks. As talked about earlier, the choice to make use of CoIP will proceed to be supported, however now you’ll be able to select between direct VPC routing and CoIP primarily based in your on-premises networking wants. Direct VPC routing is obtainable in all AWS Regions the place Outposts rack is supported.
Find extra data on this matter within the AWS Outposts User Guide. More data on AWS Outposts rack is obtainable right here.