- Newest
- Most votes
- Most comments
Hi,
The issue comes from your ".fifo": dot is not allowed in ARN syntax
See https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html for all details about allowed characters.
Best,
Didier
Hi, Here are a few things you can check and try to resolve the issue:
Topic ARN:
Make sure that the ARN you're using for the SNS topic is correct. The error message indicates that the ARN arn:aws-us-gov:sns:us-gov-west-1:702344441970:RDS-DBNotifications.fifo is invalid. Double-check the ARN from the AWS Management Console or programmatically retrieve it to ensure accuracy.
Topic Name:
Verify that the SNS topic name you're using exactly matches the one you've created. Case sensitivity matters in AWS resource names.
Permissions:
Ensure that the IAM role or user you're using to create the event subscription has the necessary permissions to access the SNS topic. You can attach the AmazonSNSFullAccess policy to your IAM user or role temporarily for testing purposes.
Region:
Confirm that you're creating the event subscription in the correct AWS region where the SNS topic exists (us-gov-west-1 in your case).
Topic Type:
Check if the SNS topic is a FIFO (First-In-First-Out) topic. FIFO topics have specific requirements and limitations compared to standard topics. If you don't specifically need FIFO behavior, consider creating a standard SNS topic.
Retry:
If all settings seem correct, try creating the event subscription again. Sometimes transient errors can occur.
If the issue persists after checking these points, you might want to provide more details about how you're creating the event subscription (e.g., through the AWS Management Console, CLI, or SDK) for further assistance. Additionally, reviewing CloudWatch logs or AWS CloudTrail logs can provide more insights into the specific error encountered during the creation process.
The subscription event name is correct because it is listed in the dropdown list on screen. I am also using AWS management console to create all objects.
Relevant content
- Accepted Answerasked a month ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
I did change the subscription type to standard and it did create it successfully. The user guide does not mention that you cant have a "." in resource id. Could this be a Bug in AWS?
resource-id The resource identifier. This is the name of the resource, the ID of the resource, or a resource path. Some resource identifiers include a parent resource (sub-resource-type/parent-resource/sub-resource) or a qualifier such as a version (resource-type:resource-name:qualifier).
Hi sam15, it may possibly be an issue in RDS if they create a SNS resource name with a forbidden '.' in it. I would suggest to open a ticket to AWS Support via AWS console to see if it needs a fix. Thanks for accepting my answer!