diff --git a/engine/context/ecs-integration.md b/engine/context/ecs-integration.md
index e6ae56c16272..fedbe7016014 100644
--- a/engine/context/ecs-integration.md
+++ b/engine/context/ecs-integration.md
@@ -252,7 +252,9 @@ services:
 
 The Docker ECS integration relies on [Amazon CloudFormation](https://docs.aws.amazon.com/cloudformation/){: target="_blank" class="_"} to manage the application deployment. To get more control on the created resources, you can use `docker compose convert` to generate a CloudFormation stack file from your Compose file. This allows you to inspect resources it defines, or customize the template for your needs, and then apply the template to AWS using the AWS CLI, or the AWS web console.
 
-By default, the Docker ECS integration creates an ECS cluster for your Compose application, a Security Group per network in your Compose file on your AWS account’s default VPC, and a LoadBalancer to route traffic to your services. If your AWS account does not have [permissions](https://github.com/docker/ecs-plugin/blob/master/docs/requirements.md#permissions){: target="_blank" class="_"} to create such resources, or you want to manage these yourself, you can use the following custom Compose extensions:
+## Using existing AWS network resources
+
+By default, the Docker ECS integration creates an ECS cluster for your Compose application, a Security Group per network in your Compose file on your AWS account’s default VPC, and a LoadBalancer to route traffic to your services. If your AWS account does not have [permissions](https://github.com/docker/ecs-plugin/blob/master/docs/requirements.md#permissions){: target="_blank" class="_"} to create such resources, or if you want to manage these yourself, you can use the following custom Compose extensions:
 
 - Use `x-aws-cluster` as a top-level element in your Compose file to set the ARN
 of an ECS cluster when deploying a Compose application. Otherwise, a 
@@ -264,10 +266,17 @@ of a VPC when deploying a Compose application.
 - Use `x-aws-loadbalancer` as a top-level element in your Compose file to set
 the ARN of an existing LoadBalancer.
 
-- Use `x-aws-securitygroup` inside a network definition in your Compose file to
-set the ARN of an existing SecurityGroup used to implement network connectivity
-between services.
+- Use `external: true` inside a network definition in your Compose file for 
+Docker ECS integration to _not_ create a Security Group, and set `name` with the 
+ID of an existing SecurityGroup you want to use for network connectivity between 
+services:
 
+```yaml
+networks:
+  back_tier:
+    external: true
+    name: "sg-1234acbd"
+```  
 
 ## Local simulation