App Mesh makes it easy to run microservices by providing consistent visibility and network traffic controls for every microservice in an application. App Mesh separates the logic needed for monitoring and controlling communications into a proxy that runs next to every microservice. App Mesh removes the need to coordinate across teams or update application code to change how monitoring data is collected or traffic is routed. This allows you to quickly pinpoint the exact location of errors and automatically re-route network traffic when there are failures or when code changes need to be deployed.
You can use App Mesh with AWS Fargate, Amazon Elastic Container Service (ECS), Amazon Elastic Container Service for Kubernetes (EKS), and Kubernetes on EC2 to better run containerized microservices at scale. App Mesh uses Envoy, an open source proxy, making it compatible with a wide range of AWS partner and open source tools for monitoring microservices.
Learn more at https://aws.amazon.com/app-mesh
Today, AWS App Mesh is generally available for production use. You can use App Mesh with AWS Fargate, Amazon Elastic Container Service (ECS), Amazon Elastic Container Service for Kubernetes (EKS), applications running on Amazon EC2, and Kubernetes on EC2 to better run containerized microservices at scale. App Mesh uses Envoy, an open source proxy, making it compatible with a wide range of AWS partner and open source tools for monitoring microservices.
Learn more at https://aws.amazon.com/app-mesh
For help getting started with App Mesh, take a look at the examples in this repo.
All the walkthrough examples in this repo are compatible only with amd64 linux instances. arm64 is only supported from version v1.20.0.1 or later of aws-appmesh-envoy and v1.4.2 and later for Appmesh-controller. We are working on updating these walkthroughs to be arm64 compatible as well. See aws#473 for more up-to-date information.
All the examples and walkthrough are written for commercial regions. You need to make few changes to make them work for China regions, below are some changes that will be needed:
- Change ARN: For China regions include aws-cn in all arns. So instead of 'arn:aws:' it starts with 'arn:aws-cn:'. Replace 'arn:aws:' with 'arn:${AWS::Partition}:' to make it work for all partitions.
- Change Endpoints: The endpoint domain for China regions is amazonaws.com.cn. Replace the endpoints from amazonaws.com to amazonaws.com.cn Refer this doc for a list of endpoints for cn-north-1. Do not change the Service Principal like ecs-tasks.amazonaws.com, it is a Service Principal not an endpoint.
- Change TCP ports 80/8080/443 By default all AWS China accounts are blocked for TCP ports 80/8080/443 with EC2 and S3 services. These ports will be unlocked when an ICP license has been provided by customers. As a workaround you can use some other port for ex: 9090. The url that you curl for, needs to explicitly mention the port now. For example: http://appme-.....us-west-2.elb.amazonaws.com.cn:9090/color
The AWS App Mesh team maintains a public roadmap.
If you have a suggestion, request, submission, or bug fix for the examples in this repo, please open it as an Issue.
If you have a feature request for AWS App Mesh, please open an Issue on the public roadmap.
If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.
- Streamline operations by offloading communication management logic from application code and libraries into configurable infrastructure.
- Reduce troubleshooting time required by having end-to-end visibility into service-level logs, metrics and traces across your application.
- Easily roll out of new code by dynamically configuring routes to new application versions.
- Ensure high-availability with custom routing rules that help ensure every service is highly available during deployments, after failures, and as your application scales.
- Manage all service to service traffic using one set of APIs regardless of how the services are implemented.
AWS App Mesh is built in direct response to our customers needs implementing a 'service mesh' for their applications. Our customers asked us to:
- Make it easy to manage microservices deployed across accounts, clusters, container orchestration tools, and compute services with simple and consistent abstractions.
- Minimize the cognitive and operational overhead in running a microservices application and handling its monitoring and traffic control.
- Remove the need to build or operate a control plane for service mesh.
- Use open source software to allow extension to new tools and different use cases.
In order to best meet the needs of our customers, we have invested into building a service that includes a control plane and API that follows the AWS best practices. Specifically, App Mesh:
- Is an AWS managed service that works across container services with a design that allows us to add support for other computer services in the future.
- Works with the open source Envoy proxy
- Is designed to pluggable and will support bringing your own Envoy images and Istio Mixer in the future.
- Implemented as a multi-tenant control plane to be scalable, robust, cost-effective, and efficient.
- Built to work independently of any particular container orchestration system. Today, App Mesh works with both Kubernetes and Amazon ECS.