Revision history [back]

There could be multiple reasons why a 502 error is returned while trying to access a newly added S3 asset. Some common reasons are:

1. Incorrect or invalid URL: Make sure that you are using the correct URL while accessing the S3 asset. The URL should be in the format: "https://s3.[region].amazonaws.com/[bucket-name]/[object-key]". Also, ensure that there are no typos or errors in the URL.

2. Permissions issue: Check if the IAM user or role that you are using to access the S3 asset has sufficient privileges to access the specific bucket and object. Also, make sure that the bucket policy or ACLs allow the user/role to access the asset.

3. Region mismatch: Ensure that the region specified in the URL matches the region where the S3 bucket is located.

4. Network connectivity issues: The 502 error can occur due to network connectivity issues between your computer and the S3 endpoint. Try accessing the asset from a different network or using a different device.

5. Backend server issue: The error could also be due to an issue with the backend server processing the request. In such cases, you may need to retry the request after some time or contact Amazon Support for assistance.