Open TryTryAgain opened 3 years ago
It's more than PROFILE
It should also support EC2 instance profile / ECS task roles.
Good use case is running azcopy
in a Fargate task.
@TryTryAgain - Did you found any workaround to ignore using --profile option and copy the data ?
@swami86 we ended up creating temporary STS creds using credential_process and supplying those generated creds. It would still be preferred to be able to use aws cli profiles in any way they would regularly allow.
Which version of the AzCopy was used?
10.8.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows and Linux
What command did you run?
Simple azcopy from s3 source to azure blob destination
What problem was encountered?
azcopy
requiresAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
environment variables. This is cumbersome when dealing with many source buckets and it would be preferred if you supported AWS CLI profiles either via a--profile
flag and/or by honoring theAWS_PROFILE
environment variable.How can we reproduce the problem in the simplest way?
AWS CLI profiles doesn't work,
azcopy
relied on there being AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables set.Have you found a mitigation/solution?
No