amazon-cloudfront

问题 Hi is there any version of amazon web services provides unlimited buckets? 回答1: No. From the S3 documentation: Each AWS account can own up to 100 buckets at a time. S3 buckets are expensive (in terms of resources) to create and destroy: The high availability engineering of Amazon S3 is focused on get, put, list, and delete operations. Because bucket operations work against a centralized, global resource space, it is not appropriate to make bucket create or delete calls on the high

问题 My idea is to use cloudfront to cache one entire site that is in EC2. But I am having a lot of trouble to do that. If I set the cloudfront option Forward Headers to none , the default index.html from apache is cached (probably because the CF is caching the LB URL). If I set Forward Headers to whitelist and add host in Whitelist Headers the site displays normally but I can see in the Response Header: X-Amz-Cf-Id:Ij8TsEU2hPehG53Op6LX1zFDmZfYWBOVFn8el8ApicCQYdYEi69HsQ== X-Cache:Miss from

问题 I have a CloudFront distribution which is pointing to an S3 bucket holding my website's static content. This is done using S3 REST API endpoints, so the origin's domain name and path looks like this: bucket-name.s3.amazonaws.com So far, this is working and I know this because when I open the browser and enter https://xxxxxxxxxxxxx.cloudfront.net/index.html , it downloads the html file. But this is not all that I'm after. My website is an SPA (single page application) written in React. This

问题 I'm using OAuth2 with my PHP EC2 server. From my frontend client hosted in S3, I'm making requests to my ElasticBeanstalk EC2 server (both frontend and backend are served through Cloudfront with SSL cert). These requests are sent with required access token header as Authorization: header ... It seems Cloudfront strips these headers as I'm getting error: error_description: "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or

问题 Using Grunt, NodeJs and Express, what module(s) should I use to: Discover all static assets (frontend JS, CSS, images) in the app, either by looking at an asset directory or parsing through the codebase Upload assets to Amazon S3 / CloudFront, renaming each file with a unique "fingerprinted" name Replace each asset's path in the codebase with the CloudFront URL Invalidate old CDN assets This is my first time using CloudFront. I am not sure if all of the above can be accomplished with Grunt,

问题 For example, a cloudfront distribution has the following CNAMEs associated with it photo-cdn.example.com video-cdn.example.com music-cdn.example.com And it has the following origins associated with it originA: photo.example.com/photocontents originB: video.example.com/videocontents originC: music.example.com/musiccontents I would like to be able to GET the following content files via the Cloudfront distribution as mapped below: photo-cdn.example.com/photo.jpg => originA/photo.jpg photo-cdn

问题 I am creating a signed url using the following: AWS_ACCESS_KEY_ID = my_access_key AWS_SECRET_ACCESS_KEY = my_secret_access_key KEYPAIR_ID = my_keypair_id KEYPAIR_FILE = path_to_keypair_file CF_DISTRIBUTION_ID = cf_dist_id my_connection = cloudfront.CloudFrontConnection( AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY ) distro_summary = my_connection.get_all_distributions()[0] distro_info = my_connection.get_distribution_info(distro_summary.id) distro = distro_summary.get_distribution() SECS = 8000

问题 I'm fairly new to AWS and I'm going through some different training courses right now and one of the interesting things I've stumbled upon is the ability to add Custom Headers in Cloudfront. That said, I can't seem to figure out (or locate simple to understand documentation) as to how to use/leverage the power that this feature offers. Can someone please let me know how: How to access the headers that I set? For example I used terminal to run some basic cURL commands to view the headers to my

问题 I'm using Cloudfront with load balancing and ec2 instances. In AWS, my load balancer accepts traffic from all http connections. It is possible to restrict that to accept only http connections from my Cloudfront distributions ? And how can I do that ? Thanks. 回答1: AFAIK, you can't do this at layer 3 as an ELB will allow access from anywhere (0.0.0.0/0). If you're running Apache and can find a specific header that cloudfront uses/sets then you could do this at layer 7 using mod_headers.

问题 I have a API hosted using AWS Gateway API in combination with a custom domain. Its been in production for at least a year. However, when I go to Cloudfront resource page from AWS web console , I don't see any distribution entries under my same account which is used for Gateway API. AWS Documentation states below: The CloudFront distribution created by API Gateway is owned by a region-specific account affiliated with API Gateway. When tracing operations to create and update such a CloudFront