aws / aws/containers-roadmap

[ECS] [ARN]: Let change the user/role

Open
#1,067 0 comments 0 reactions 0 assignees View on GitHub
ECS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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**
A command to change the owner (created by) of a service, that's means user or role

**Which service(s) is this request for?**
Fargate

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
A user activates his account to support the new ARN format and create cluster/services, after that leaves the company and the account is deleted.

Is not possible increase/decrease the task running in that service using another account (also with support to new ARN) , because you get the error message:

_error Task long arn format must be enabled for launching service tasks with ECS managed tags._

**Are you currently working around this issue?**
The only way to do it is:

1. not erase that account who create the service, or
2. activate the support for longARN to root account, or
3. re-build the cluster and service with another user/role

**Additional context**
N/A

**Attachments**
N/A

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or entry points are named. Start by reviewing the ECS/Fargate service ownership behavior and the reported long-ARN error; the requested outcome is a supported way to change the user or role that created a service so another account can scale its tasks.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.