How do I configure CORS in Amazon S3 and confirm the CORS rules using cURL?
"I want to allow cross-origin access to resources in my Amazon Simple Storage Service (Amazon S3) bucket, but I'm getting an error."
"I want to allow cross-origin access to resources in my Amazon Simple Storage Service (Amazon S3) bucket, but I'm getting an error.ResolutionYou can apply Cross-Origin Resource Sharing (CORS) rules to your bucket using either the Amazon S3 console or AWS Command Line Interface (AWS CLI). To test the CORS rules on your Amazon S3 bucket, use the cURL command. CORS is a feature of HTTP that uses headers to allow browsers to display content which a web server requested from a different origin. If you make a cross-origin request to an Amazon S3 bucket that isn't defined by a CORS rule, then the CORS header isn't returned.For example:curl -i http://mycorsbucket.s3.amazonaws.com/cors-test.html -H "Origin: http://www.example.com"HTTP/1.1 200 OKx-amz-id-2: Va106gWx1uUDGbouopXfpjvjHW0VXydI8/VGlraf/62f2vvxtI+iAnmu7lF4MK2B6CxuzReyfRI=x-amz-request-id: QWNNX1Y0MWFM152HDate: Thu, 04 Nov 2021 18:52:55 GMTLast-Modified: Thu, 04 Nov 2021 16:03:50 GMTETag: "cd4276d2cd5a2dc8ebcc1e04746680f6"Accept-Ranges: bytesContent-Type: text/htmlServer: AmazonS3Content-Length: 55If a web server made a similar request to a website, the content retrieved from your bucket won't appear in your browser. To allow your content to appear, configure a CORS policy on your Amazon S3 bucket. Proper configuration of the CORS policy makes sure that the appropriate headers are returned. You can configure a CORS rule on your bucket using the Amazon S3 console or AWS CLI.Configuring a CORS rule using the Amazon S3 consoleTo configure a CORS rule on your bucket using the Amazon S3 console, perform the following steps:1.    Sign in to the AWS Management Console.2.    Open the Amazon S3 console.3.    Select your bucket.4.    Choose the Permissions tab.5.    In the Cross-origin resource sharing pane, choose Edit.6.    In the text box, enter the JSON CORS rule that you want to activate:Example:[  {    "AllowedHeaders": [      "Authorization"    ],    "AllowedMethods": [      "GET",      "HEAD"    ],    "AllowedOrigins": [      "http://www.example.com"    ],    "ExposeHeaders": [      "Access-Control-Allow-Origin"    ]  }]For more information about each of the CORS rule elements or example rules, see CORS configuration.7.    Choose Save.Configuring a CORS rule using the AWS CLITo configure a CORS rule on your bucket using the AWS CLI, run the following command:aws s3api put-bucket-cors --bucket mycorsbucket --cors-configuration '{"CORSRules" : [{"AllowedHeaders":["Authorization"],"AllowedMethods":["GET","HEAD"],"AllowedOrigins":["http://www.example.com"],"ExposeHeaders":["Access-Control-Allow-Origin"]}]}'Note: If you receive errors when running AWS CLI commands, make sure that you're using the most recent version of the AWS CLI.Testing the CORS ruleTo test the CORS rule, use the cURL command, like this:curl -i http://mycorsbucket.s3.amazonaws.com/index.html -H "Origin: http://www.example.com"HTTP/1.1 200 OKx-amz-id-2: d5Jsw1vCf8tR3cMdXrtcTKYgczU/1pjxahnrw7C6jU1fLo8py2Nv2kpeFs8pYPruVZg6Y3JuRUA=x-amz-request-id: BMCCY18E58B3GBWVDate: Thu, 04 Nov 2021 19:12:26 GMTAccess-Control-Allow-Origin: http://www.example.comAccess-Control-Allow-Methods: GET, HEADAccess-Control-Expose-Headers: Access-Control-Allow-OriginAccess-Control-Allow-Credentials: trueVary: Origin, Access-Control-Request-Headers, Access-Control-Request-MethodLast-Modified: Thu, 04 Nov 2021 16:03:50 GMTETag: "cd4276d2cd5a2dc8ebcc1e04746680f6"Accept-Ranges: bytesContent-Type: text/htmlServer: AmazonS3Content-Length: 55If the CORS rule is correctly configured, you receive a 200 OK response.Troubleshooting CORS methodsIf you encounter unexpected behavior while accessing buckets with the CORS configuration, try the following:1.    Use the cURL command to make requests using specific CORS methods by adding the -H "Access-Control-Request-Method: <Method>" flag. This flag specifies the CORS method to be tested. Use the --request OPTIONS flag to perform a preflight check of the request.Note: Amazon S3 supports the GET, HEAD, PUT, POST, and DELETE methods.curl -i http://mycorsbucket.s3.amazonaws.com/cors-test.html -H "Access-Control-Request-Method: POST" --request OPTIONS -H "Origin: http://www.example.com"HTTP/1.1 403 Forbiddenx-amz-request-id: 190J4Q6222HA2KZ5x-amz-id-2: 6oEci3qg88OeoLvBGwkN8K9AGdxyVela8ZKxftXMqyWrtZFfiKMrBwpTAeRiOth8amovJMtAAdA=Content-Type: application/xmlTransfer-Encoding: chunkedDate: Fri, 19 Nov 2021 18:43:38 GMTServer: AmazonS3<?xml version="1.0" encoding="UTF-8"?><Error><Code>AccessForbidden</Code><Message>CORSResponse: This CORS request is not allowed. This is usually because the evalution of Origin, request method / Access-Control-Request-Method or Access-Control-Request-Headers are not whitelisted by the resource's CORS spec.</Message><Method>POST</Method><ResourceType>OBJECT</ResourceType><RequestId>190J4Q6222HA2KZ5</RequestId><HostId>6oEci3qg88OeoLvBGwkN8K9AGdxyVela8ZKxftXMqyWrtZFfiKMrBwpTAeRiOth8amovJMtAAdA=</HostId></Error>2.    If the request returns an error, verify that the CORS configuration is set on the bucket. Be sure that you added the required method to the CORS rule on your bucket. If the CORS configuration is set, you see the option to edit the CORS configuration in the Permissions section for bucket in the S3 console.aws s3api put-bucket-cors --bucket mycorsbucket --cors-configuration '{"CORSRules" : [{"AllowedHeaders":["Authorization"],"AllowedMethods":["GET","HEAD","POST"],"AllowedOrigins":["http://www.example.com"],"ExposeHeaders":["Access-Control-Allow-Origin"]}]}'3.    Test the updated CORS rule. If your method works as expected, you receive the following response:curl -i http://mycorsbucket.s3.amazonaws.com/index.html -H "Access-Control-Request-Method: POST" -X OPTIONS -H "Origin: http://www.example.com"HTTP/1.1 200 OKx-amz-id-2: Cx4kuM31KPVE19woEPRRYxF+85vEWkLk8+M0p6BIb72T550njMnmLtjqRgYzuxKelR0f+cxhFqI=x-amz-request-id: QBSHV46QK43HGW15Date: Fri, 19 Nov 2021 18:48:21 GMTAccess-Control-Allow-Origin: http://www.example.comAccess-Control-Allow-Methods: GET, HEAD, POSTAccess-Control-Expose-Headers: Access-Control-Allow-OriginAccess-Control-Allow-Credentials: trueVary: Origin, Access-Control-Request-Headers, Access-Control-Request-MethodServer: AmazonS3Content-Length: 04.    Capture the complete request and response using a tool of your choice. For each request that Amazon S3 receives, you must have a CORS rule that matches the data in your request.Verify that the request has the Origin header. If the header is missing, Amazon S3 doesn't treat the request as a cross-origin request, and doesn't send CORS response headers in the response.Verify that the Origin header in your request matches at least one of the AllowedOrigins elements in the specified CORSRule. The scheme, host, and port values in the Origin request header must match the AllowedOrigins elements in the CORSRule. For example, suppose you set the CORSRule to allow the origin http://www.example.com. When you do this, https://www.example.com and http://www.example.com:80 origins in your request don't match the allowed origin in your configuration.Verify that the method in your request or preflight request (method that's specified in the Access-Control-Request-Method) is one of the AllowedMethods elements in the same CORSRule.If a preflight request includes an Access-Control-Request-Headers header, verify that the CORSRule includes the AllowedHeader entries for each value in the Access-Control-Request-Headers header.Related informationAdding HTTP headers to Amazon CloudFront responsesHow do I resolve the "No 'Access-Control-Allow-Origin' header is present on the requested resource" error from CloudFront?How does Amazon S3 evaluate the CORS configuration on a bucket?Troubleshoot CORSFollow"