App Mesh on Amazon Outposts - Amazon App Mesh
PrerequisitesLimitationsNetwork connectivity considerationsCreating an App Mesh Envoy proxy on an Outpost
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

App Mesh on Amazon Outposts

Important

End of support notice: On September 30, 2026, Amazon will discontinue support for Amazon App Mesh. After September 30, 2026, you will no longer be able to access the Amazon App Mesh console or Amazon App Mesh resources. For more information, visit this blog post Migrating from Amazon App Mesh to Amazon ECS Service Connect.

Amazon Outposts enables native Amazon services, infrastructure, and operating models in on-premises facilities. In Amazon Outposts environments, you can use the same Amazon APIs, tools, and infrastructure that you use in the Amazon Cloud. App Mesh on Amazon Outposts is ideal for low-latency workloads that need to be run in close proximity to on-premises data and applications. For more information about Amazon Outposts, see the Amazon Outposts User Guide.

Prerequisites

The following are the prerequisites for using App Mesh on Amazon Outposts:

  • You must have installed and configured an Outpost in your on-premises data center.

  • You must have a reliable network connection between your Outpost and its Amazon Region.

  • The Amazon Region for the Outpost must support Amazon App Mesh. For a list of supported Regions, see Amazon App Mesh Endpoints and Quotas in the Amazon Web Services General Reference.

Limitations

The following are the limitations of using App Mesh on Amazon Outposts:

  • Amazon Identity and Access Management, Application Load Balancer, Network Load Balancer, Classic Load Balancer, and Amazon Route 53 run in the Amazon Region, not on Outposts. This will increase latencies between these services and the containers.

Network connectivity considerations

The following are network connectivity considerations for Amazon EKS Amazon Outposts:

  • If network connectivity between your Outpost and its Amazon Region is lost, the App Mesh Envoy proxies will continue to run. However you will not be able to modify your service mesh until connectivity is restored.

  • We recommend that you provide reliable, highly available, and low-latency connectivity between your Outpost and its Amazon Region.

Creating an App Mesh Envoy proxy on an Outpost

An Outpost is an extension of an Amazon Region, and you can extend an Amazon VPC in an account to span multiple Availability Zones and any associated Outpost locations. When you configure your Outpost, you associate a subnet with it to extend your Regional VPC environment to your on-premises facility. Instances on an Outpost appear as part of your Regional VPC, similar to an Availability Zone with associated subnets.

Amazon Web Services Region with VPC, subnets, and Outpost extension showing network connectivity.

To create an App Mesh Envoy proxy on an Outpost, add the App Mesh Envoy container image to the Amazon ECS task or Amazon EKS pod running on an Outpost. For more information, see Amazon Elastic Container Service on Amazon Outposts in the Amazon Elastic Container Service Developer Guide and Amazon Elastic Kubernetes Service on Amazon Outposts in the Amazon EKS User Guide.