amazon-cloudfront

AccessDenied: User is not authorized to perform: cloudfront:CreateInvalidation

人盡茶涼 提交于 2021-02-20 17:03:44
问题 I'm trying to deploy an ember app to AWS CloudFront using ember-cli-deploy and ember-cli-deploy-cloudfront. I set up my bucket and user in AWS, gave my user AmazonS3FullAccess policy. Set up my .env.deploy.production file to look like this: AWS_KEY=<my key> AWS_SECRET=<my secret> PRODUCTION_BUCKET=<app.<my domain>.com PRODUCTION_REGION=us-east-1 PRODUCTION_DISTRIBUTION=<my cloudfront distribution id> My config/default.js looks like this: /* jshint node: true */ module.exports = function

AccessDenied: User is not authorized to perform: cloudfront:CreateInvalidation

假如想象 提交于 2021-02-20 17:02:54
问题 I'm trying to deploy an ember app to AWS CloudFront using ember-cli-deploy and ember-cli-deploy-cloudfront. I set up my bucket and user in AWS, gave my user AmazonS3FullAccess policy. Set up my .env.deploy.production file to look like this: AWS_KEY=<my key> AWS_SECRET=<my secret> PRODUCTION_BUCKET=<app.<my domain>.com PRODUCTION_REGION=us-east-1 PRODUCTION_DISTRIBUTION=<my cloudfront distribution id> My config/default.js looks like this: /* jshint node: true */ module.exports = function

AccessDenied: User is not authorized to perform: cloudfront:CreateInvalidation

ⅰ亾dé卋堺 提交于 2021-02-20 17:02:07
问题 I'm trying to deploy an ember app to AWS CloudFront using ember-cli-deploy and ember-cli-deploy-cloudfront. I set up my bucket and user in AWS, gave my user AmazonS3FullAccess policy. Set up my .env.deploy.production file to look like this: AWS_KEY=<my key> AWS_SECRET=<my secret> PRODUCTION_BUCKET=<app.<my domain>.com PRODUCTION_REGION=us-east-1 PRODUCTION_DISTRIBUTION=<my cloudfront distribution id> My config/default.js looks like this: /* jshint node: true */ module.exports = function

cloudfront is giving “your connection is not private” error

自作多情 提交于 2021-02-11 12:29:21
问题 I am trying to have to host on my s3 bucket which is attached to CloudFront distribution in the front. But I am getting this error when I access the CloudFront domain name I know the following error might be because of the SSL certificate. But I have the same SSL certificate attached to other distributions and that is working fine. I also check if the name c name matches, which I does. Could anyone help me out with this? 来源: https://stackoverflow.com/questions/65933833/cloudfront-is-giving

AWS Cloudfront distribution ID by tag

两盒软妹~` 提交于 2021-02-09 11:13:03
问题 is that possible to get aws cloudfront dist id by tag via awscli or aws sdk for powershell. I could only get only ID by ARN number of resource aws cloudfront list-tags-for-resource --resource XXX { "Tags": { "Items": [ { "Value": "TEST_APP", "Key": "CLIENT_APP" } ] } } UPDATE Solved via cloudfrontdistids=$(aws cloudfront list-distributions | jq -r ".DistributionList.Items[].ARN") for dist in $cloudfrontdistids do if [ $(aws cloudfront list-tags-for-resource --resource $dist | jq -r ".Tags

AWS Cloudfront distribution ID by tag

|▌冷眼眸甩不掉的悲伤 提交于 2021-02-09 11:12:46
问题 is that possible to get aws cloudfront dist id by tag via awscli or aws sdk for powershell. I could only get only ID by ARN number of resource aws cloudfront list-tags-for-resource --resource XXX { "Tags": { "Items": [ { "Value": "TEST_APP", "Key": "CLIENT_APP" } ] } } UPDATE Solved via cloudfrontdistids=$(aws cloudfront list-distributions | jq -r ".DistributionList.Items[].ARN") for dist in $cloudfrontdistids do if [ $(aws cloudfront list-tags-for-resource --resource $dist | jq -r ".Tags

cloudfront responds with a status of 413 (Request Entity Too Large)

牧云@^-^@ 提交于 2021-02-09 01:40:55
问题 We have a requirement to send large data as part of URL which will be read by angular to render the page. Url is of more than 10000 characters. But cloudfront is returning below error - Bad request. Generated by cloudfront (CloudFront) Request ID: I2fOApzZr4psKrWsY6abezp5R0m30zKDKE7c0MuB_JkjWbvxz5GVnQ== Browser console returns error code 413 with below message - Failed to load resource: the server responded with a status of 413 (Request Entity Too Large) Is there any settings in cloud front

Cloudfront + Woocommerce - cart not updating

大兔子大兔子 提交于 2021-02-08 11:38:45
问题 I have recently added cloudfront to my wordpress site hosted on AWS. At first my cart would not register any products being added to it - so I made a behaviour in cloudfront to not cache the cart, my account and checkout pages. Now my users can only add a single product at a time - after adding a second it overwrites what was added in intially. I believe it must be a problem with the caching behaviour of cloudfront. can anyone help me with what settings I need to get woocommerce to play nice

Multiple S3 buckets in the same CloudFront distribution

懵懂的女人 提交于 2021-02-07 12:28:28
问题 I created a Cloudfront distribution with a CNAME images.domain.com with SSL, and I have 2 S3 buckets: one for user uploads, one for product pictures The default bucket is the uploads bucket I would like to use the same CloudFront for both buckets So I added the 2 buckets as origins and created a "Behavior", with the path /products/* using my product bucket as origin My "Behaviors" are : /products/* to: products bucket (precedence = 0) Default (*) to: uploads bucket (precedence = 1) When I go

Multiple S3 buckets in the same CloudFront distribution

这一生的挚爱 提交于 2021-02-07 12:28:27
问题 I created a Cloudfront distribution with a CNAME images.domain.com with SSL, and I have 2 S3 buckets: one for user uploads, one for product pictures The default bucket is the uploads bucket I would like to use the same CloudFront for both buckets So I added the 2 buckets as origins and created a "Behavior", with the path /products/* using my product bucket as origin My "Behaviors" are : /products/* to: products bucket (precedence = 0) Default (*) to: uploads bucket (precedence = 1) When I go