By using AWS re:Post, you agree to the Terms of Use

Questions tagged with AWS Cloud Map

Sort by most recent
  • 1
  • 12 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

HTTP API GW + API VPC Link + Cloudmap + Fargate - How does it load balance

I am using an infrastructure setup as described in the title. This setup is also somewhat shown in this picture: https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2021/02/04/5-CloudMap-example.png In the official AWS blog here: https://aws.amazon.com/blogs/compute/configuring-private-integrations-with-amazon-api-gateway-http-apis/ the following is stated about using such setup: > As AWS Cloud Map provides client-side service discovery, you can replace the load balancer with a service registry. Now, connections are routed directly to backend resources, instead of being proxied. This involves fewer components, making deployments safer and with less management, and reducing complexity. My question is simple: What load balancing algorithm does HTTP API GW use when distributing traffic to resources (the Fargate tasks) registered in a service registry? Is it round-robin just as it is with ALB? Only thing I was able to find is this: > For integrations with AWS Cloud Map, API Gateway uses DiscoverInstances to identify resources. You can use query parameters to target specific resources. The registered resources' attributes must include IP addresses and ports. API Gateway distributes requests across healthy resources that are returned from DiscoverInstances. https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-private.html#http-api-develop-integrations-private-Cloud-Map
2
answers
0
votes
297
views
asked 7 months ago

failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve "fs-03ec98cf2f1d81580.efs.us-east-1.amazonaws.com"

Hi, I'm following the APPLICATION MODERNIZATION WITH AWS AND DOCKER workshop steps as mentioned and in module 2, Step 1 - Section: ***Deploy to Amazon ECS***, really got stuck when deploying application to AWS ECS. When I execute the "*docker compose up*" command as mentioned, it starts deploying resources and The Docker Compose CLI first concatenates the compose files passed through and generates an opinionated AWS CloudFormation template and deploys it to create the AWS resources defined in our compose file. After few mins , its shows in cloudformation "DELETE_IN_PROGRESS" and when all the resources get decommissioned it throws an error message saying "*DbService TaskFailedToStart: ResourceInitializationError: failed to invoke EFS utils commands to set up EFS volumes: stderr: Failed to resolve '*fs-03ec98cf2f1d81580.efs.us-east-1.amazonaws.com*' - check that your file system ID is correct.*" When I checked in the EFS console, the EFS was created successfully. Not sure why is this causing an issue? **GitHub Repo:** https://github.com/spawar1991/docker-compose-ecs-sample ------------------------------------------------------------------------- Workshop URL: https://docker.awsworkshop.io/31_docker_ecs_integration/10_migrate_to_ecs.html Can someone know how to mitigate this error and why is it causing an issue? Thanks in advance.
2
answers
0
votes
135
views
asked 9 months ago
  • 1
  • 12 / page