Support ECS Service connect
See original GitHub issueUpdating the task definition to use Service Connect, I get an error during the deploy process.
* UnexpectedParameter: Unexpected key 'name' found in params.containerDefinitions[0].portMappings[0]
* UnexpectedParameter: Unexpected key 'appProtocol' found in params.containerDefinitions[0].portMappings[0]
With ECS supporting Service connect, name
and appProtocol
has to be supported in portMappings
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/ECS.html#registerTaskDefinition-property
Issue Analytics
- State:
- Created 9 months ago
- Reactions:6
- Comments:6
Top Results From Across the Web
Service Connect - Amazon Elastic Container Service
Amazon ECS Service Connect provides management of service-to-service communication as Amazon ECS configuration. It does this by building both service ...
Read more >New – Amazon ECS Service Connect Enabling ... - Noise
ECS Service Connect provides an easy network setup and seamless service communication deployed across multiple ECS clusters and virtual private ...
Read more >How do I connect to an ECS service running on Fargate?
So far, I have configured my service using Fargate and it is running on ECS with 1 task. I'm not really sure how...
Read more >Interconnecting services - Amazon Elastic Container Service
Amazon ECS Service Connect provides management of service-to-service communication as Amazon ECS configuration. It does this by building both service ...
Read more >New: Amazon ECS Service Connect - Enabling Easy ... - Reddit
Service Connect does service discovery, and load balancing using a client side proxy; it also does connection draining and automatically ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thank you both @shinenelson @javalon very much! It has helped me to understand and solve the problem 💯
This is a problem only if one uses the AWS Management Console to create new task definition revision. To get around this, one could use the Create new version with JSON option while creating the new revision and edit the task definition JSON by hand. I recognize that this is not as intuitive as filling up a form, but that comes at the cost of all of the GitHub Action workflows depending on the same task definitions failing.