ECS scheduled tasks to give a warning or should not allow to create rule with the same name as another rule in the same region and on the same event bus.

[ghost]

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 What do you want us to build? ECS scheduled tasks to give a warning or should not allow to create rule with the same name as another rule in the same region and on the same event bus.

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? What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

Creating an ECS scheduled task of the same name in the same region but different clusters will delete the scheduled task initially created in another cluster without a warning and user's knowledge, resulting to tasks not provisioning.

Are you currently working around this issue? How are you currently solving this problem? No

Additional context Anything else we should know?

Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

[nacitar]

It's worth mentioning explicitly that this "feature request" that most sane people would call a "bug" results in users adding NEW scheduled tasks to clusters and having other scheduled tasks (with the same name) deleted from another cluster SILENTLY. There should be no conflict here whatsoever, and the web UI is structured in a way that makes it look like scheduled tasks are PER-CLUSTER, because they are listed within the cluster's page and do not show the scheduled tasks of other clusters, but yet they are much more global than this... if you choose a name that's in use by another cluster, that cluster just loses the scheduled task without warning. You'd have to manually look and notice it is missing to have any clue. Anything that results in silent deletions of unrelated things is a terrible bug, not a "feature request"... people shouldn't have scheduled tasks just vanishing and if indeed this is the silly way that it's "meant to work", the web UI should be greatly adjusted to indicate the fact that all scheduled tasks from all clusters (in the same region) share the same namespace, and they shouldn't be visually separated on a per-cluster basis because it isn't per-cluster AT ALL. The UI shouldn't lie to the user. Fix this bug.