Thank you for this. This was really helpful.
This can also be related to existing notification configuration destinations being invalid, rather than overlapping prefixes or suffixes. I found that existing event destinations had been removed, though the notification configuration pointing to them was still present, and this prevented any new configurations being added, even with a random prefix, suffix and previously unused event type.
The solution obviously was to validate any existing notification configuration destinations and remove the ones that were no longer valid.
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 8 個月前
- AWS 官方已更新 2 年前