To forward the headers using a cache policy: Or, choose Save changes if you're editing an existing behavior. Note: To create your own cache policy instead, see Creating cache policies. For more information, see Using the managed origin request policies. Then, for Origin request policy, choose CORS-S3Origin or CORS-CustomOrigin from the dropdown list. Under Cache key and origin requests, choose Cache policy and origin request policy.Or, select an existing behavior, and then choose Edit. Open your distribution from the CloudFront console.To add a pre-defined policy to your distribution: To forward the headers to the origin server, CloudFront has two pre-defined policies depending on your origin type: CORS-S3Origin and CORS-CustomOrigin. If your origin server is an Amazon S3 bucket, then configure your distribution to forward the following headers to Amazon S3:

Configure the CloudFront distribution to forward the appropriate headers to the origin serverĪfter you set up a CORS policy on your origin server, configure your CloudFront distribution to forward the origin headers to the origin server. Set up a CORS policy on your custom origin or Amazon Simple Storage Service (Amazon S3) origin.

If CORS headers are not returned in the response, then the origin server is not correctly setup for CORS. If the CORS policy allows the origin server to return the Access-Control-Allow-Origin header, you see a response similar to the following: HTTP/1.1 200 OK Replace with the URL of the resource that's returning the header error. Replace with the required origin header. Run the following command to confirm the origin server returns the Access-Control-Allow-Origin header. Note: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version. Resolution Confirm the origin's cross-origin resource sharing (CORS) policy allows the origin to return the Access-Control-Allow-Origin header

Angular 4 access control allow origin