amazon-web-services

Terraform: Issue with assume_role

本秂侑毒 提交于 2021-02-09 11:17:04
问题 I'm trying to solve this mystery for few days now, but no joy. Basically, Terraform cannot assume role and failing with: Initializing the backend... 2019/10/28 09:13:09 [DEBUG] New state was assigned lineage "136dca1a-b46b-1e64-0ef2-efd6799b4ebc" 2019/10/28 09:13:09 [INFO] Setting AWS metadata API timeout to 100ms 2019/10/28 09:13:09 [INFO] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id 2019/10/28 09:13:09 [INFO] AWS Auth provider used:

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

Terraform: Issue with assume_role

安稳与你 提交于 2021-02-09 11:13:03
问题 I'm trying to solve this mystery for few days now, but no joy. Basically, Terraform cannot assume role and failing with: Initializing the backend... 2019/10/28 09:13:09 [DEBUG] New state was assigned lineage "136dca1a-b46b-1e64-0ef2-efd6799b4ebc" 2019/10/28 09:13:09 [INFO] Setting AWS metadata API timeout to 100ms 2019/10/28 09:13:09 [INFO] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id 2019/10/28 09:13:09 [INFO] AWS Auth provider used:

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

Terraform: Issue with assume_role

夙愿已清 提交于 2021-02-09 11:12:39
问题 I'm trying to solve this mystery for few days now, but no joy. Basically, Terraform cannot assume role and failing with: Initializing the backend... 2019/10/28 09:13:09 [DEBUG] New state was assigned lineage "136dca1a-b46b-1e64-0ef2-efd6799b4ebc" 2019/10/28 09:13:09 [INFO] Setting AWS metadata API timeout to 100ms 2019/10/28 09:13:09 [INFO] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id 2019/10/28 09:13:09 [INFO] AWS Auth provider used:

response for preflight is invalid (redirect) for aws s3

风格不统一 提交于 2021-02-09 08:38:48
问题 I am trying to upload an image to my Amazon S3 bucket. But I keep getting this CORS error, even though I have set the CORS configuration correctly. This is my CORS configuration: <?xml version="1.0" encoding="UTF-8"?> <CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <CORSRule> <AllowedOrigin>*</AllowedOrigin> <AllowedMethod>GET</AllowedMethod> <MaxAgeSeconds>3000</MaxAgeSeconds> <AllowedHeader>Authorization</AllowedHeader> </CORSRule> <CORSRule> <AllowedOrigin>http:/

response for preflight is invalid (redirect) for aws s3

吃可爱长大的小学妹 提交于 2021-02-09 08:28:33
问题 I am trying to upload an image to my Amazon S3 bucket. But I keep getting this CORS error, even though I have set the CORS configuration correctly. This is my CORS configuration: <?xml version="1.0" encoding="UTF-8"?> <CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/"> <CORSRule> <AllowedOrigin>*</AllowedOrigin> <AllowedMethod>GET</AllowedMethod> <MaxAgeSeconds>3000</MaxAgeSeconds> <AllowedHeader>Authorization</AllowedHeader> </CORSRule> <CORSRule> <AllowedOrigin>http:/

Can I trigger an ECS/Fargate task from a specific file upload in S3?

主宰稳场 提交于 2021-02-09 02:44:10
问题 I know that I can trigger a task when a file is uploaded (per https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/CloudWatch-Events-tutorial-ECS.html) however, how can I trigger a task when a specific file is uploaded? Amazon seems not to have anticipated people having multiple jobs watching the same bucket for different files :( 回答1: You can accomplish this with CloudWatch Events from CloudTrail Data Events. Head over to CloudTrail, and create a Trail for your account. For Apply trail

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

AWS Elastic Beanstalk - how to stop previous docker before starting new one

偶尔善良 提交于 2021-02-08 23:42:19
问题 I have a set of AWS Elastic beanstalk using Docker based configuration for both web server and worker server. The way we have setup is that the java process inside docker allocates 70% of the box memory when starting. Now the first deployment works fine, but when I try to update application version with in-place Rolling update, Elastic beanstalk tries to start an additional docker container with the java process before stopping the existing one. This fails the deploy as the Java server is not