You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: engine/context/ecs-integration.md
+38-1
Original file line number
Diff line number
Diff line change
@@ -376,7 +376,44 @@ of a VPC when deploying a Compose application.
376
376
- Use `x-aws-loadbalancer` as a top-level element in your Compose file to set
377
377
the ARN of an existing LoadBalancer.
378
378
379
-
- Use `external: true` inside a network definition in your Compose file for
379
+
The latter can be used for those who want to customize application exposure, typically to
380
+
use an existing domain name for your application:
381
+
382
+
1. Use the AWS web console or CLI to get your VPC and Subnets IDs. You can retrieve the default VPC ID and attached subnets using this AWS CLI commands:
1. Use the AWS CLI to create your load balancer. The AWS Web Console can also be used but will require adding at least one listener, which we don't need here.
1. To assign your application an existing domain name, you can configure your DNS with a
410
+
CNAME entry pointing to just-created loadbalancer's `DNSName` reported as you created the loadbalancer.
411
+
412
+
1. Use Loadbalancer ARN to set `x-aws-loadbalancer` in your compose file, and deploy your application using `docker compose up` command.
413
+
414
+
Please note Docker ECS integration won't be aware of this domain name, so `docker compose ps` command will report URLs with loadbalancer DNSName, not your own domain.
415
+
416
+
You also can use `external: true` inside a network definition in your Compose file for
380
417
Docker Compose CLI to _not_ create a Security Group, and set `name` with the
381
418
ID of an existing SecurityGroup you want to use for network connectivity between
0 commit comments