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.

### 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**
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.)

The request concerns ECS and Fargate scheduled tasks and duplicate rule names within the same region and event bus. No repository files, tests, or implementation entry points are named; first clarify the service scope and expected warning or rejection behavior, with completion defined as preventing an unintended deletion or clearly warning about the duplicate.

Written by the indexing model from the issue text.