By using AWS re:Post, you agree to the AWS re:Post Terms of Use

Can't create S3 event notification to SNS topic from specific bucket

0

I'm trying to create S3 event notification to SNS topic from an existing S3 bucket. I'm receiving "Unable to validate the following destination configurations".

Initially I thought the issue was with the SNS topic Access Policy and tried different troubleshooting suggestions, such as this video https://www.youtube.com/watch?v=RjSW75YsBMM, but nothing worked.

I'm using the following policy:

{
    "Version": "2012-10-17",
    "Id": "example-ID",
    "Statement": [
        {
            "Sid": "Example SNS topic policy",
            "Effect": "Allow",
            "Principal": {
                "Service": "s3.amazonaws.com"
            },
            "Action": [
                "SNS:Publish"
            ],
            "Resource": "SNS-topic-ARN",
            "Condition": {
                "ArnLike": {
                    "aws:SourceArn": "arn:aws:s3:*:*:bucket-name"
                },
                "StringEquals": {
                    "aws:SourceAccount": "bucket-owner-account-id"
                }
            }
        }
    ]
}  

Then I decided to focus on the S3 bucket part of the equation and created brand new bucket with exactly the same configuration, switched the SourceArn in the policy with the new bucket's arn and the event notification was successfully created.

What could be the reason for a given SNS topic with a given policy to work with one S3 bucket, but not with another?

2 Answers
1

One of the reasons for the validation failure could be an incorrect or misspelled ARN. Or it could be the event types that trigger the SNS notifications. Verify the bucket configuration to make sure it is properly setup to receive event notifications. Specifically it can trigger the right SNS topic. In addition, double check on the regions where the S3 and SNS services are created and the validations will fail if they are in different regions.

AWS
answered 2 years ago
0

In SNS topic access policy change the "AWS:SourceOwner" to "AWS:SourceAccount" and add "ArnLike": { "aws:SourceArn": "arn:aws:s3:::your bucket name" }

Then it will work.

answered 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions