This message was deleted.

Hi, the

--sync-usage-file

features currently uses your the creds from the default AWS provider chain, so it will use the same credentials that would be used by the

aws

CLI tool. To set or override these you can use the

AWS_ACCESS_KEY_ID

and

AWS_SECRET_ACCESS_KEY environment

or

AWS_PROFILE

env variables. Would that work for your use case?

I will try to build a custom docker image with an AWS config file with assume roles and set the

AWS_PROFILE

to point to the correct account. I will post here some feedback.

🙌 thanks, yeah let me know how it goes

This worked perfectly. Thanks for pointing me in the right direction. Great product you guys have here! Cheers!

Awesome @proud-tailor-45919 💪 , could I ask what’s your specific use case for using the

sync-usage-file

. It would be amazing to understand what information/data your looking to populate

Hey @mysterious-teacher-68276, we use Atlantis and every team is responsible for their own AWS infra. The

sync-usage-file

is particularly important for us to estimate costs of Lambdas, S3 and we would love to get more info on DynamoDBs.

ok perfect, thanks for the info