See: Description
| Interface | Description |
|---|---|
| AWSAppMesh |
Interface for accessing AWS App Mesh.
|
| AWSAppMeshAsync |
Interface for accessing AWS App Mesh asynchronously.
|
| Class | Description |
|---|---|
| AbstractAWSAppMesh |
Abstract implementation of
AWSAppMesh. |
| AbstractAWSAppMeshAsync |
Abstract implementation of
AWSAppMeshAsync. |
| AWSAppMeshAsyncClient |
Client for accessing AWS App Mesh asynchronously.
|
| AWSAppMeshAsyncClientBuilder |
Fluent builder for
AWSAppMeshAsync. |
| AWSAppMeshClient |
Client for accessing AWS App Mesh.
|
| AWSAppMeshClientBuilder |
Fluent builder for
AWSAppMesh. |
AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and control microservices. App Mesh standardizes how your microservices communicate, giving you end-to-end visibility and helping to ensure high availability for your applications.
App Mesh gives you consistent visibility and network traffic controls for every microservice in an application. You can use App Mesh with AWS Fargate, Amazon ECS, Amazon EKS, and Kubernetes on AWS.
App Mesh supports microservice applications that use service discovery naming for their components. To use App Mesh,
you must have an application running on Amazon EC2 instances, hosted in either Amazon ECS, Amazon EKS, or Kubernetes
on AWS. For more information about service discovery on Amazon ECS, see Service Discovery in the
Amazon Elastic Container Service Developer Guide. Kubernetes kube-dns and coredns
are supported. For more information, see DNS for Services and Pods in the
Kubernetes documentation.
Copyright © 2013 Amazon Web Services, Inc. All Rights Reserved.