Facing NoSuchKey exception when deploying a stack

Hello.

What specific CloudFormation template are you using?

Generally, the cause of this error is that the S3 path specification is incorrect or the specified object does not exist in the S3 bucket.
So please make sure that the path is correct and that the object is successfully placed in the S3 bucket.

Hi,

A standard bucket is accessible in only the region in which it was created. So, you'll have an error like NoSuchKey when you access it from your new region.

2 solutions:

1. for data locality, you replicate your bucket under a different name in the new region (region name as suffix) and you install automatic replication across the buckets
2. you make the single bucket accessible over a global bucket access point: see https://medium.com/cloudzone/aws-s3-multi-region-access-point-simplify-your-data-access-across-regions-60a232957084 for a good intro. Then go to AWS doc: https://aws.amazon.com/s3/features/multi-region-access-points/

Both solutions above will require changes to your CFN template: you'll have to make the name of the bucket region-dependent (using a CFN Map) or replace current bucket name by global access endpoint

Best,

Didier