- Newest
- Most votes
- Most comments
Hello.
**EDIT: **When exporting correct AWS username access keys in used docker image, boto3 started working. However I could not get in working without exporting access keys
If you are running it on Fargate, I think it will work without setting an access key if you set an IAM policy on the ECS task roles.
Please refer to the following document to set it up.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html
By the way, if containers within the same task are communicating with each other, you can connect using localhost and port number as described in the document below.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/fargate-task-networking.html
By default, every Amazon ECS task on Fargate is provided an elastic network interface (ENI) with a primary private IP address. When using a public subnet, you can optionally assign a public IP address to the task's ENI. If your VPC is configured for dual-stack mode and you use a subnet with an IPv6 CIDR block, your task's ENI also receives an IPv6 address. A task can only have one ENI that's associated with it at a time. Containers that belong to the same task can also communicate over the localhost interface. For more information about VPCs and subnets, see How Amazon VPC works in the Amazon VPC User Guide.
Relevant content
asked 5 years ago
