Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[service] [request]: Fine-grained IAM permission control for ECS UpdateService API #2527

Open
yb-thai opened this issue Jan 23, 2025 · 0 comments
Labels
Proposed Community submitted issue

Comments

@yb-thai
Copy link

yb-thai commented Jan 23, 2025

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request

Request the ability to create more granular IAM permissions for the Amazon ECS UpdateService API. Specifically, need the option to grant a user or role permission to modify only the DesiredCount parameter of an ECS service, while preventing changes to any other service attributes.

Which service(s) is this request for?
ECS

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

The existing IAM permissions for ecs:UpdateService are too broad, allowing users with this permission to modify multiple service parameters beyond just the DesiredCount.

Suggestion: Introduce a new condition key, i.e as "ecs:UpdateServiceParams", that would allow administrators to specify which parameters of the UpdateService API can be modified. This would enable the creation of IAM policies that restrict users to only updating the DesiredCount, while preventing modifications to other service attributes like task definition, deployment configuration, or network configuration.

Are you currently working around this issue?
Allow user/role to able to update all the parameters in ECS service.

@yb-thai yb-thai added the Proposed Community submitted issue label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

1 participant