Why doesn't aws-ecs-deploy support PortMapping name in the ContainerDefinitions?

Brandon Robinson_tv7yni

Using the aws-ecs-deploy-1.6.2, I keep getting an error stating:

 

<span>&#10006; Failed to update the stack.</span>

<span>An error occurred (InvalidParameterException) when calling the UpdateService operation: portName(whatsours-stripe-service-8095-tcp) does not refer to any named PortMapping in the container definitions.</span>

This is due to the fact that we had to add PortMapping name to our task definitions in AWS ECS because we want to enable client/server Service Discovery; however, our task-definition-development.json file doesn't allow us to add name in the portMappings. If we add it, then we receive the following error:

 

<span>&#10006; ECS task definition parameter validation error: </span>

<span>Parameter validation failed:</span>

<span>Unknown parameter in containerDefinitions[0].portMappings[0]: "name", must be one of: containerPort, hostPort, protocol</span>

Any solutions?

 

Igor Stoyanov

@Brandon Robinson hi. Thanks for your question.

Looks like boto3 library should be updated in this pipe to fix this error (add support for it): 

<span>&#10006; ECS task definition parameter validation error: </span>

<span>Parameter validation failed:</span>

<span>Unknown parameter in containerDefinitions[0].portMappings[0]: "name", must be one of: containerPort, hostPort, protocol</span>

We will notify you when new release will become available.

Regards, Igor