Local gateway ingress routing for AWS Outposts rack is now available
You can now create Outposts rack local gateway (LGW) inbound routes to redirect incoming traffic to an elastic network interface (ENI) attached to an Amazon EC2 instance before the traffic reaches your enterprise workloads running on your Outpost. The EC2 instance may run virtual network appliance software to inspect, modify, or filter network traffic before relaying the traffic to other EC2 instances.
You can now create Outposts rack local gateway (LGW) inbound routes to redirect incoming traffic to an elastic network interface (ENI) attached to an Amazon EC2 instance before the traffic reaches your enterprise workloads running on your Outpost. The EC2 instance may run virtual network appliance software to inspect, modify, or filter network traffic before relaying the traffic to other EC2 instances.
AWS Outposts rack installed at customer locations uses LGW for communication between your Outpost and on-premises traffic. With AWS Outposts rack LGW ingress routing, you can now create an ENI for your virtual network appliance to receive traffic from the local network destined for any IP address range that do not belong to VPCs on Outposts rack. This enables you to use LGW ingress routing to steer traffic to an EC2 instance on the Outposts rack functioning as a virtual network appliance, thereby creating the fine-grained network and security policies for your workload.
To learn more about Outposts rack local gateway ingress routing, read this blog. To find out more about Outposts rack, visit the AWS Outposts website and user guide. To get started, visit the AWS Management Console.