aws-fargate

问题 Basically, I'm follow these two guides: Deploying Hasura on AWS with Fargate, RDS and Terraform Deploying Containers on Amazon’s ECS using Fargate and Terraform: Part 2 I have: Postgres RDS Database deployed in 'Multi-AZ' My python/flask app deployed in Fargate across multiple AZ's I run a migration inside the task definition before the app ALB Load balancing between the tasks Logging for RDS, ECS and ALB into Cloudwatch Logs. A NAT gateway with an Elastic IP for each private subnet to get

问题 I'm launching a RoR application over AWS ECS in a Fargate task. This exact task has been running successfully for over a year and started failing (i.e. can't connect via browser) since about a week. After contacting tech support, I found that when I use CURL to connect to my site from the command line, it responds quickly with the full HTML document. When I try to use Firefox / Chrome instead, it just times out with either 503 or 504 error. Has there been some changes to SSL / certificates,

问题 I'm launching a RoR application over AWS ECS in a Fargate task. This exact task has been running successfully for over a year and started failing (i.e. can't connect via browser) since about a week. After contacting tech support, I found that when I use CURL to connect to my site from the command line, it responds quickly with the full HTML document. When I try to use Firefox / Chrome instead, it just times out with either 503 or 504 error. Has there been some changes to SSL / certificates,

问题 I am trying to run a pod on fargate from EKS that needs to access s3 via boto3 python client and I cant figure out why this is happening. It works just fine when scheduled on a eks ec2 node. botocore.exceptions.NoCredentialsError: Unable to locate credentials I have a properly setup fargate profile and followed this guide. Does anyone know why aws credentials are not within the context of this pod? Does this have anything to do with the pod execution role? 回答1: I have a properly setup fargate

问题 I am trying to run a pod on fargate from EKS that needs to access s3 via boto3 python client and I cant figure out why this is happening. It works just fine when scheduled on a eks ec2 node. botocore.exceptions.NoCredentialsError: Unable to locate credentials I have a properly setup fargate profile and followed this guide. Does anyone know why aws credentials are not within the context of this pod? Does this have anything to do with the pod execution role? 回答1: I have a properly setup fargate

问题 I have deployed the docker image of my spring boot application over aws ECR, following creation of AWS fargate cluster. PFA screenshots of the configurations stating task, security, service and cluster definition.I can ping my public ip successfully. But I can't access my application over neither load balancer nor public ip. The urls I tried to access application were public_ip:8081/my_rest_end_point and load_balancer_public_dns:8081/my_reset_end_point I have tested running my docker image on

问题 I am trying to create a following architecture: a vpc with two subnets (one is public containing a NatGateway and an InternetGateway, and another one is private. I start a fargate service in a private subnet and it fails with this error: CannotPullContainerError: API error (500): Get https://XYZ.dkr.ecr.us-east-1.amazonaws.com/v2/: net/http: request cancelled while waiting for connection (Client.Timeout exceeded while awaiting headers) Here's my CloudFormation template (the service is

问题 I am trying to create a following architecture: a vpc with two subnets (one is public containing a NatGateway and an InternetGateway, and another one is private. I start a fargate service in a private subnet and it fails with this error: CannotPullContainerError: API error (500): Get https://XYZ.dkr.ecr.us-east-1.amazonaws.com/v2/: net/http: request cancelled while waiting for connection (Client.Timeout exceeded while awaiting headers) Here's my CloudFormation template (the service is

问题 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

问题 In Re:Invent 2018, AWS seems to have launched new integrations with Step Functions, which includes ECS Fargate support. https://docs.aws.amazon.com/step-functions/latest/dg/connectors-ecs.html I have been digging up on this, and I am able to get the ECS task to startup, and do its thing, but I am not able to send desired output back to the step function. The response syntax too does not seem to have anything that corresponds to the output of a particular state. https://docs.aws.amazon.com