1 Answer
- Newest
- Most votes
- Most comments
0
Hello, Here's a direct link to the same error and the possible causes as per your use-case.
Link -- https://aws.amazon.com/premiumsupport/knowledge-center/unable-validate-destination-s3/ -- [1]
I had a look in this link, I'm trying to use lambda instead SNS notification. As additional information, the invoke permission is already set in another cloud formation stack, the error occurs when I try to include the bucket notification statement.
Relevant content
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 5 months ago
I find out that this error happened because of yml file indentation, I tried removing spaces in the event tag and it worked.