2022年7月27日 · it's impossible to use ACM to generate certificate for aws-managed domains; when using imported certificate in ACM, FQDN is required; it seems that for a https alb listener, self-signed cert can't be used. It is totally possible to generate certificate with FQDN like *.eu-east-1.alb.aws.com, but cloudfront returns 502.

2020年10月6日 · Open the AWS console to a non-China region; Create a Route53 hosted zone with a Geolocation routing policy. Create an A record (not CNAME). Create a Geolocation record for China, pointing at the China CloudFront distro in China. Create a Geolocation record for everywhere else, pointing at your other non-China distribution.

2017年7月27日 · Thank you for telling where I can get err_log when 502 bad request happened. and I found that if I used s3 domain directly, it tell me no resolve s3 domain, and I just added resolver 8.8.8.8 with google DNS before proxy_pass. But if I used AWS CDN url, the url still cannot be resolved. –

2022年8月4日 · On the application, user is allowed to upload large videos of upto 5GB, and can also share with others using a shareable link, So can this add to more cost as in the AWS Pricing calculator, the data read/write on the CDN show 0 and no extra cost.

2016年4月20日 · This gets a bit complicated as you're basically rolling your own CDN from scratch using AWS EC2 instances and probably want to have distribution points in multiple regions. Depending on your scale, it may make sense to have intermediate nodes that serve to pull from the origin and redistribute to regional edges.

A CDN would be better suited to your needs, if your setup permits it. S3 appear to have a limit around 50MB/s for bandwidth (at least from a single instance) as per this article , but that is higher than what you should require (S3 does not support streaming).

2020年7月17日 · I just need https://my-bucket.s3.us-east-1.amazonaws.com to be cached/CDN'd by CloudFlare. And obviously I can't change Amazon's DNS ;-) I don't think this would be difficult but I can't seem to find a relatively simple explanation of the right way to set this up.

2017年8月17日 · The users will connect to a nearby CDN node and its then the CDN that communicates with your server. For some CDN's you can also just upload your static files directly to them (or a companion services, e.g Amazon CloudFront+S3), and you may have the ability to purge cache entires manually when updating if you don't use versioned URLs.

However, the CDN will provide a lighter load on your web server if you get a lot of traffic because you're passing off the serving of your media to another server. One last point, a good CDN (and Amazon's is) will user their extensive network to serve …

Although you cannot see it when you browse the CloudFront response policy settings in AWS console (it would be nice if AWS added this), it appears that the default CORS policies in CloudFront do NOT override the origin settings. So the S3 CORS responses were being cached by CloudFront leading to the issue.