Containers-roadmap: [ECS] [request]: Updating a service to no longer require replacement

[piradeepk]

Tell us about your request

Updating most properties on a service using CloudFormation can currently only be done through replacement. I'd like a way for a service to be updated without requiring replacement.

Which service(s) is this request for?

Fargate/ECS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

Creating a service with a custom service name allows me to specify a human readable service name. However, when I update a property within that service for instance the launchType from EC2 to Fargate, it requires my service to be replaced.

The problem is since I created a service with a custom service name, the cloud formation update service call fails as it’s unable to create the new service with the same service name. In order to get around this issue, I either have to a) update my service name to be something different, which I don’t want to do as a user, or b) delete the service before I can recreate it. This is a problem if it’s a production service as it makes my service unavailable for my users.

I would like a way to be able to update my existing service without requiring my service to be replaced.

[graylancome]

Any solution to this issue. I am currently experiencing this as well. There has to be a cleaner way to perform updates from a pipeline without running into this issue.