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
I have deploy a custom build (I have not changed anything in the build apart from specifying the region) to a ap-east-1 bucket and when trying to deploy using cloud formation I get the following error,
The S3 bucket that you specified for CloudFront logs doesn't exist: imagehandler-logs-17wtb102tkcts.s3.amazonaws.com (Service: AmazonCloudFront; Status Code: 400; Error Code: InvalidArgument; Request ID: 3617cbf7-5ae8-445f-991e-a56e95441a51)
However when I checked S3 bucket list, I can see the specified log bucket (imagehandler-logs-17wtb102tkcts) has been created in ap-east-1.
Not sure if it's because the script is checking the wrong region?
The text was updated successfully, but these errors were encountered:
@jhau I'm sorry for your inconvenience. Unfortunately, our solution does not support some of recently launched regions such as Bahrain (me-south-1) and Hong Kong (ap-east-1).
@jhau we have updated our solution, and I believe your issue has been fixed. If you still see the issue with the latest version (v6.0.0), please feel free to reopen the issue.
I have deploy a custom build (I have not changed anything in the build apart from specifying the region) to a ap-east-1 bucket and when trying to deploy using cloud formation I get the following error,
The S3 bucket that you specified for CloudFront logs doesn't exist: imagehandler-logs-17wtb102tkcts.s3.amazonaws.com (Service: AmazonCloudFront; Status Code: 400; Error Code: InvalidArgument; Request ID: 3617cbf7-5ae8-445f-991e-a56e95441a51)
However when I checked S3 bucket list, I can see the specified log bucket (imagehandler-logs-17wtb102tkcts) has been created in ap-east-1.
Not sure if it's because the script is checking the wrong region?
The text was updated successfully, but these errors were encountered: