Over-aggressive Credentials Checking about remotion HOT 6 CLOSED

Thanks @shellscape for filing!
We can implement a credentials bypass, but it could also be possible to just recognize $HOME/.aws/profile.

However, I cannot find any resources about the $HOME/.aws/profile feature. How did you learn about this?

from remotion.

https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html#cli-configure-files-where

The AWS CLI stores sensitive credential information that you specify with aws configure in a local file named credentials, in a folder named .aws in your home directory. The less sensitive configuration options that you specify with aws configure are stored in a local file named config, also stored in the .aws folder in your home directory.

And re: aws-sdk automatically loading the profile: https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-shared.html

from remotion.

I see $HOME/.aws/credentials, but not $HOME/.aws/profile.
I assume it was meant in a paraphrased way.

Do you want to review #3363?

from remotion.

Thanks, I was context switching too much. credentials is correct.

from remotion.

@JonnyBurger 4.0.86 solves the use case for ~/.aws/credentials. Thanks for getting that in. I still believe that a switch for turning off checking would be useful, but that's up to you all. I'm unblocked as of 4.0.86 though.

from remotion.

@shellscape Great to hear! We'll be quick to react if a case surfaces where we need further loosening.

from remotion.