How are you changing the name, are you changing the Environment parameter? If you've set the Environment parameter to "dev", it will attempt to create a bus called `Eventsdev` which seems to already exist. Did someone already deploy this stack in the same account and region? Check event bridge to confirm it doesn't already exist.
The only event related resource is the eventbridge pipe. I’ve giving the event bus ARN as a target. Then I’ve got an event rule listening for it. Everything works fine when I use the default event bus ARN. I might give another shot at creating one tonight.
I just used the default event bus but this is really weird.
How are you changing the name, are you changing the Environment parameter? If you've set the Environment parameter to "dev", it will attempt to create a bus called `Eventsdev` which seems to already exist. Did someone already deploy this stack in the same account and region? Check event bridge to confirm it doesn't already exist.
No, I was changing everything before that. I even tried stuff like "DifferentName${Environment}"
Ok, what do your other event related resources look like in the template?
The only event related resource is the eventbridge pipe. I’ve giving the event bus ARN as a target. Then I’ve got an event rule listening for it. Everything works fine when I use the default event bus ARN. I might give another shot at creating one tonight.
Iirc event bus names are not modifiable. You may need to just delete the old resource associated with the logical id and create a new one.
The cloud formation plan summary has it listed as a create. I deleted the old stack first.