referred to mesh gateway functionality in ECS overview
This commit is contained in:
parent
fa9c1bfcf4
commit
dfcd28048a
|
@ -8,15 +8,13 @@ description: >-
|
|||
|
||||
# AWS ECS
|
||||
|
||||
Consul service mesh applications can be deployed on [AWS Elastic Container Service](https://aws.amazon.com/ecs/) (ECS)
|
||||
using either our official [Terraform modules](/docs/ecs/terraform/install) or without Terraform by [manually configuring
|
||||
the task definition](/docs/ecs/manual/install).
|
||||
You can deploy Consul service mesh applications to [AWS Elastic Container Service](https://aws.amazon.com/ecs/) (ECS) using either our official [Terraform modules](/docs/ecs/terraform/install) or by [manually configuring the task definition](/docs/ecs/manual/install).
|
||||
|
||||
## Service Mesh
|
||||
|
||||
Using Consul on AWS ECS enables you to add your ECS tasks to the service mesh and
|
||||
take advantage of features such as zero-trust-security, intentions, observability,
|
||||
traffic policy, and more.
|
||||
traffic policy, and more. You can also connect service meshes so that services deployed across your infrastructure environments can communicate.
|
||||
|
||||
## Architecture
|
||||
|
||||
|
|
Loading…
Reference in a new issue