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
For our local development we define AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
On AWS we use the ContainerCredentials to define permissions.
To not forget it in local development we preset the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as empty variables in our default .env.
After deploying our application to AWS we found out that for accessing SQS via Symfony Messenger the ContainerCredentials are not taken into account.
I think the issue is this type safe null check in the CredentialProvider Class, because $accessKeyId and $secretAccessKeyId are of type "string(0)" when set to empty in the environment.
Hi.
For our local development we define AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
On AWS we use the ContainerCredentials to define permissions.
To not forget it in local development we preset the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as empty variables in our default .env.
After deploying our application to AWS we found out that for accessing SQS via Symfony Messenger the ContainerCredentials are not taken into account.
I think the issue is this type safe null check in the CredentialProvider Class, because $accessKeyId and $secretAccessKeyId are of type "string(0)" when set to empty in the environment.
aws/src/Core/src/Credentials/ConfigurationProvider.php
Lines 38 to 40 in 6b7f1de
The text was updated successfully, but these errors were encountered: