1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hello.
By configuring Service Discovery, you can set a domain for the container.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html
I hope the following documentation tutorials will be helpful.
https://docs.aws.amazon.com/AmazonECS/latest/userguide/create-service-discovery.html
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
I tried to use this solution, but I faced with another issue. I'm using Account A for network and Account B for the ECS cluster. The private hosted zone can be created only into the Account A and I'm not able to associate the hostname with my container.
Do you have any recommendation how to archive this?
I have never set it up cross-account, but from reading the document below, I think it might not be possible to set it up unless the ECS task and VPC are in the same account. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html
If there is another method, I think you will need to use ALB to route to tasks by DNS name. https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-update-rules.html