You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchBucket. S3 Error Message: The specified bucket does not exist (Service: Lambda, Status Code: 400, Request ID: d5091597-a0ff-4160-8c4a-551414fb91cc)" (RequestToken: 833066cd-d1f7-a380-c414-6578f32d62c5, HandlerErrorCode: InvalidRequest)
To Reproduce
It appears that when the "custom-control-tower-initiation.template" is creating a bucket with random letters in the back, but the lambda function is looking for ${AWS::Region}.
I originally assumed that the script did not give enough time for the S3 bucket to build. but every time you run the script it names it cfctest(Stack Name)-customcontroltowercloudtraildataeventbucke(Bucket Name from Template)-ebvht6sthyzz(Random Characters) so ever if I delete the stack and run it again, the characters at the end change so it get the same error. Please advise on how to move forward.
The text was updated successfully, but these errors were encountered:
Describe the bug
Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchBucket. S3 Error Message: The specified bucket does not exist (Service: Lambda, Status Code: 400, Request ID: d5091597-a0ff-4160-8c4a-551414fb91cc)" (RequestToken: 833066cd-d1f7-a380-c414-6578f32d62c5, HandlerErrorCode: InvalidRequest)
To Reproduce
It appears that when the "custom-control-tower-initiation.template" is creating a bucket with random letters in the back, but the lambda function is looking for ${AWS::Region}.
I originally assumed that the script did not give enough time for the S3 bucket to build. but every time you run the script it names it cfctest(Stack Name)-customcontroltowercloudtraildataeventbucke(Bucket Name from Template)-ebvht6sthyzz(Random Characters) so ever if I delete the stack and run it again, the characters at the end change so it get the same error. Please advise on how to move forward.
The text was updated successfully, but these errors were encountered: