Open niros1 opened 3 years ago
Two things come to mind:
~/.aws/config
file and AWS_PROFILE env var, which you would use to authenticate inside your container, and the second being the fact that you're passing the access key, secret, and token via env vars that you received from authenticating on your local host.If you want to authenticate locally, then you don't need to pass your aws config and profile name to the container, as that information is contained in the key, secret, and token.
Hi, I am working with compose based on scenario 1 (https://aws.amazon.com/blogs/compute/a-guide-to-locally-testing-containers-with-amazon-ecs-local-endpoints-and-docker-compose/), everything work well till I configured my environment to MFA authentication. Before MFA i just used the profile name and mounting the .aws directory, I change the docker-compose.override to use the current session, the problem is that I get (from Boto) ResourceNotFoundException when I am trying to work with Dynamo DB. any idea what am I missing?
in order to use the authentication session I did the following changes (see env vars below):
10X in advance. Nir