App Mesh Preview Channel - AWS App Mesh

App Mesh Preview Channel

Important

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

The App Mesh Preview Channel is a distinct variant of the App Mesh service provided in the us-west-2 Region. The Preview Channel exposes upcoming features for you to try as they are developed. As you use features in the Preview Channel, you can provide feedback via GitHub to shape how the features behave. Once a feature has complete functionality in the Preview Channel, with all of the necessary integrations and checks completed, it will graduate to the production App Mesh service.

The AWS App Mesh Preview Channel is a Beta Service and all features are previews, as those terms are defined in the AWS Service Terms. Your participation in the Preview Channel is governed by your Agreement with AWS and the AWS Service Terms, in particular, the Universal and Beta Service Participation terms, and is confidential.

The following questions are frequently asked about the Preview Channel.

The Preview Channel is a public service endpoint that allows you to try out and provide feedback on new service features before they are generally available. The service endpoint for the Preview Channel is separate from the standard production endpoint. You interact with the endpoint by using the AWS CLI, a service model file for the Preview Channel, and command input files for the AWS CLI. The Preview Channel, allows you to try new features without impacting your current production infrastructure. You're encouraged to provide feedback to the App Mesh team to help ensure that App Mesh meets customers' most important requirements. Your feedback on features while they're in the Preview Channel can help shape the features of App Mesh so that we can deliver the best possible service.

The following table lists aspects of the App Mesh service that are different from the Preview Channel.

Aspect App Mesh production service App Mesh Preview Channel service
Frontend endpoint appmesh.us-west-2.amazonaws.com appmesh-preview.us-west-2.amazonaws.com
Envoy management service endpoint appmesh-envoy-management.us-west-2.amazonaws.com appmesh-preview-envoy-management.us-west-2.amazonaws.com
CLI AWS App Mesh list-meshes AWS App Mesh-preview list-meshes (only available after adding the Preview Channel service model)
Signing name appmesh appmesh-preview
Service principal appmesh.amazonaws.com appmesh-preview.amazonaws.com
Note

Though the example in the table for the App Mesh production service lists the us-west-2 Region, the production service is available in most Regions. For a list of all Regions that the App Mesh production service is available in, see AWS App Mesh Endpoints and Quotas. However, the App Mesh Preview Channel service is available only in the us-west-2 Region.

  1. Add the Preview Channel service model that includes the Preview Channel feature to the AWS CLI with the following command.

    aws configure add-model \
    --service-name appmesh-preview \
    --service-model https://raw.githubusercontent.com/aws/aws-app-mesh-roadmap/main/appmesh-preview/service-model.json

  2. Create a JSON file that includes the feature, based on the JSON example and instructions provided in the AWS App Mesh User Guide for the feature.

  3. Implement the feature with the appropriate AWS CLI command and command input file. For example, the following command creates a route with Preview Channel features using the route.json file.

    aws appmesh-preview create-route --cli-input-json file://route.json

  4. Add APPMESH_PREVIEW = 1 as a configuration variable for the Envoy container when adding it to your Amazon ECS task definitions, Kubernetes Pod specifications, or Amazon EC2 instances. This variable enables the Envoy container to communicate with the Preview Channel endpoints. For more information about adding configuration variables, see Updating services in Amazon ECS, Updating services in Kubernetes, and Updating services on Amazon EC2.

You can provide feedback directly on the App Mesh roadmap GitHub repo issue that is linked from the documentation about the feature.

The feedback period will vary depending on the size and complexity of the feature being introduced. We intend to give a comment period of 14 days between release of a feature to the preview endpoint and release of the feature to production. The App Mesh team may extend the feedback period for specific features.

While we encourage you to provide feedback and bug reports directly on the App Mesh GitHub roadmap issue, we understand that you may have sensitive data to share, or you may find an issue that you do not feel is safe to disclose publicly. For these issues, you can contact AWS Support or give feedback by emailing the App Mesh team directly.

Yes. The Preview Channel is given the same level of security as the standard production endpoint.

You can work with a mesh in the Preview Channel for thirty days. Thirty days after a mesh is created, you can only list, read, or delete the mesh. If you attempt to create or update resources after thirty days, you'll receive a BadRequest exception explaining that the mesh is archived.

You can use the AWS CLI with a Preview Channel service model file and command input files. For more information about how to work with features, see How can I use features in the Preview Channel?. You cannot use AWS CLI command options, the AWS Management Console, SDKs, or AWS CloudFormation to work with Preview Channel features. You can use all tools however, once a feature is released to the production service.

No. APIs may change based on feedback.

No. New API objects may not be fully integrated into the AWS Management Console, AWS CloudFormation, or AWS CloudTrail. As features solidify in the Preview Channel and near general availability, the integrations will eventually become available.

Yes. Documentation for Preview Channel features is included in the production documentation. For example, if features for the route resource are released to the Preview Channel, information about how to use the features would be in the existing route resource document. Preview Channel features are labeled as only available in the Preview Channel.

When new features are introduced in the Preview Channel, an entry is added to the App Mesh Document History. You can review the page regularly or subscribe to the App Mesh Document History RSS feed. Additionally, you can review the issues for the AWS App Mesh roadmap GitHub repo. A download link for the Preview Channel service model JSON file is added to an issue when it releases to the Preview Channel. For more information about how to use the model and feature, see How can I use features in the Preview Channel?.

The text in the App Mesh documentation noting that the feature is available only in the Preview Channel is removed, and an entry is added to the App Mesh Document History. You can review the page regularly or subscribe to the App Mesh Document History RSS feed.