Architecting for seamless on-premises connectivity with AWS Outposts servers
Compute Blog
The article discusses networking considerations for AWS Outposts servers, focusing on how to configure network connectivity for EC2 instances in an on-premises environment.
- Outposts servers use two network interfaces: Elastic Network Interface (ENI) and Local Network Interface (LNI)
- ENI connects to the AWS VPC, while LNI provides local network connectivity
- By default, EC2 instances route traffic through the ENI, but can be configured to use LNI for local and internet traffic
- A user-data script can be used to modify routing tables and enable local network connectivity
- The example demonstrates launching an EC2 instance with both ENI and LNI interfaces
The solution allows organizations to run AWS services on-premises with low latency while maintaining connectivity to existing infrastructure.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Mar 18
2025
2025
Migrating your on-premises workloads to AWS Outposts Rack
Jul 10
2026
2026
Architecting for IOPS and throughput performance on AWS Outposts racks
Mar 3
2025
2025
Announcing AWS Outposts racks for high throughput, network-intensive workloads (Preview)
Apr 1
2025
2025
Anchoring AWS Outposts servers with AWS Direct Connect
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.