The aforementioned error indicates that the bucket specified did not exist in the eu-central-1 region at the time of Canary creation. In an attempt to reproduce this issue, I deployed the solution here and the only change I made to the template was to replace the
RuntimeVersion: syn-1.0 property with
RuntimeVersion: syn-nodejs-puppeteer-3.0 per the Synthetics runtime versions here . The stack deployed successfully.
To fix this issue, confirm that the S3 bucket was indeed created successfully from the stack events before the creation of the canary. You could also consider using the below snippet to narrow down the issue;
ArtifactS3Location: Fn::Join: - '' - - s3:// - Ref: MyArtifactBucket
My suspicion is that the bucket name used in ArtifactS3Location did not resolve to an existing bucket.
For further troubleshooting, we would require details that are non-public information. Please open a support case with AWS using the following link
S3 Bucket cannot be reached in GroundTruth Labelingasked 5 months ago
How to append timestamp to s3 bucket name in suffix using cloudformation template?asked 3 months ago
S3 bucket name is not configured while creating stack through CloudFormation template.asked 3 months ago
S3 bucket permissions to run CloudFormation from different accounts and create Lambda Funtions.asked 9 months ago
Does an S3 bucket have to be provided for a Braket DWave run?asked 2 years ago
AWS::Synthetics::Canary Not Creating S3 Bucket in EUAccepted Answerasked 8 months ago
Using S3 bucket as source for table in Athenaasked 18 days ago
How to declare multi region access point in cloudformation template
Changing S3 Bucket Region of Aws Amplifyasked 2 months ago
Can AWS CloudFormation template access s3 from any region other than its current region?