amazon-cloudfront

问题 I have created a S3 bucket, uploaded a video, created a streaming distribution in CloudFront. Tested it with a static HTML player and it works. I have created a keypair through the account settings. I have the private key file sitting on my desktop at the moment. That's where I am. My aim is to get to a point where my Django/Python site creates secure URLs and people can't access the videos unless they've come from one of my pages. The problem is I'm allergic to the way Amazon have laid

问题 Question: When configuring Route 53 with AWS services such as CloudFront or ELB, which is better to use: an ALIAS A record or an ALIAS CNAME record? Background: An interesting thread developed on this question regarding the benefits of ALIAS records. Thread Link My intention is to create this question so that informed answers and knowledge can be collected in one place. 回答1: There is no "better," there's only one correct answer: the Alias RR type must be the same as the target RR. For

问题 We use AWS CloudFront as our CDN in front of an Apache website running on an EC2 server. The website uses SSL (https) and CloudFront is configured to use the default CloudFront certificate, so our application loads static assets using https://xxxxxxcloudfront.net/path/to/asset , rather than https://ourdomain.com/path/to/asset . Our SSL certificate, issues by Go Daddy, expired yesterday. After installing a new certificate on the web server, CloudFront no longer seems able to deliver any assets

问题 UPDATE : The problem is with playing HTML5 videos in Safari not with playing videos in a native application. Since v10.0 upgrade iOS devices cannot play videos from a CloudFront distribution with signed cookies restriction enabled. If I disable signed cookies restriction it works as it does with previous iOS versions. I've checked the release notes and checked each related forum seeking for an explanation and ideally a solution for this issue. I found nothing reported in either Apple nor AWS

问题 Follow up to AWS API Gateway should prevent use of TLS v1, I created a Cloudfront distribution with below config Origin Domain Name as my Gate API endpoint https://abcdfefg.execute-api.us-east-1.amazonaws.com Viewer Protocol Policy as HTTPS Only Origin SSL Protocols as TLSv1.2, TLSv1.1 (Unchecked TLSv1) other defaults After the distribution was deployed, when I access my Gateway API with custom domain, I still was able to make calls on TLSv1. How do I map my custom domain to this new

问题 I have SSL Certified and setup a homepage for my site: example.com and www.example.com using Cloudfront, Route 53, and an s3 bucket. The site is just a basic static site. I am trying to setup my Cloudfront/Route 53 to allow for WildCard subomdains so I can create some landing pages eg, industry-a.example.com, industry-z.example.com and have them point to separate static s3 buckets. I have tried adding in *.example.com to my Cloudfront and Route 53 I have a hosted zone created for a domain

问题 I have deployed a lambda, which in itself returns an 'Access-Control-Allow-Origin': '*' header in it's response. I call it from an API Gateway. When calling the API gateway URL, the CORS configuration is fine. I placed CloudFront in front of the API, however now I am unable to access the API as the CORS configuration seems to be overridden by CloudFront, and I am not sure where to add custom headers in CloudFront. How do you enable CORS inside CloudFront? 回答1: Go into your CloudFront

问题 Following this article, I'm trying to serve my static content from multiple regions (under the same domain) within AWS. So far, I have: uploaded my content into an S3 bucket enabled the "static web hosting" for that bucket and made it public created a distribution in CloudFront with the S3 bucket as the origin created a record set in Route 53 pointing to the distribution At this point, everything works fine. If I enter the domain name in a browser, I can see the static content. Now it's time

问题 Logstash version 1.5.0.1 I am trying to use the logstash s3 input plugin to download cloudfront logs and the cloudfront codec plugin to filter the stream. I installed the cloudfront codec with bin/plugin install logstash-codec-cloudfront . I am getting the following: Error: Object: #Version: 1.0 is not a legal argument to this wrapper, cause it doesn't respond to "read". Here is the full error message from /var/logs/logstash/logstash.log {:timestamp=>"2015-08-05T13:35:20.809000-0400",

问题 The following code executes no problem on 2 other servers I have access to and use to run on Hostgator. Hostgator tech support refuse to help as they feel it's an issue with the code. I get no response from the API unless I change the HTTPS to HTTP in which case I get a 307 redirect message from cloudfront.net. Any ideas on what a solution might be? $data = array( "status" => "Quote", "job_address" => "1 Infinite Loop, Cupertino, California 95014, United States", "job_description" => "Client