You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My specific example is running within a Fargate container. Setting the env variables would be against a best practice and it would be better to use the defined task role to fetch credentials.
2022/10/26 20:43:41 AWS_ACCESS_KEY_ID environment variable is required and not found
I am not super familiar with golang but I believe based on the session created here
it should handle situations where env vars are not set and credentials are loaded in a different way. So the environment variables are not explicitly needed to work.
The text was updated successfully, but these errors were encountered:
1davidmichael
changed the title
Required AWS variables
Required AWS variables not actually required
Oct 27, 2022
Currently environment variables for AWS are required to be set. However, they are particular instances where the variables are not defined and the AWS SDK handles fetching them via other means.
My specific example is running within a Fargate container. Setting the env variables would be against a best practice and it would be better to use the defined task role to fetch credentials.
I am not super familiar with golang but I believe based on the session created here
it should handle situations where env vars are not set and credentials are loaded in a different way. So the environment variables are not explicitly needed to work.
The text was updated successfully, but these errors were encountered: