Add this rule to your .htaccess
Header add Access-Control-Allow-Origin "*"
even better, as suggested by @david thomas, you can use a specific domain value, e.g.
Header add Access-Control-Allow-Origin "your-domain.example"
More Related Contents:
- AWS CloudFront: Font from origin has been blocked from loading by Cross-Origin Resource Sharing policy
- Amazon CloudFront Latency
- S3 – Access-Control-Allow-Origin Header
- CloudFront + S3 Website: “The specified key does not exist” when an implicit index document should be displayed
- Multiple Cloudfront Origins with Behavior Path Redirection
- Supporting HTTPS URL redirection with a single CloudFront distribution
- AWS CloudFront redirecting to S3 bucket
- S3 Static Website Hosting Route All Paths to Index.html
- Technically what is the difference between s3n, s3a and s3?
- Make a bucket public in Amazon S3
- How to rename files and folder in Amazon S3?
- how to add cache control in AWS S3?
- AWS S3 pre signed URL without Expiry date
- Amazon S3 – HTTPS/SSL – Is it possible? [closed]
- Downloading an entire S3 bucket?
- Getting started with secure AWS CloudFront streaming with Python
- Amazon s3a returns 400 Bad Request with Spark
- AWS S3 display file inline instead of force download
- AWS s3 V3 Javascript SDK stream file from bucket (GetObjectCommand)
- S3 – What Exactly Is A Prefix? And what Ratelimits apply?
- Access AWS S3 from Lambda within VPC
- S3: User cannot access object in his own s3 bucket if created by another user
- AWS S3 Bucket Access from EC2
- AWS S3 CLI – Could not connect to the endpoint URL
- Cloudfront and EC2
- Getting 403 forbidden from s3 when attempting to download a file
- AWS Glue output file name
- AWS S3 gracefully handle 403 after getSignedUrl expired
- Amazon S3 bucket returning 403 Forbidden
- AWS CLI S3 A client error (403) occurred when calling the HeadObject operation: Forbidden