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
Mar 3
2025
2025
Announcing AWS Outposts racks for high throughput, network-intensive workloads (Preview)
Apr 29
2025
2025
Announcing second-generation AWS Outposts racks with breakthrough performance and scalability on-premises
Apr 19
2024
2024
Architecting for Disaster Recovery on AWS Outposts Racks with AWS Elastic Disaster Recovery
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.