- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
DynamoDB Local V2.0 and greater convention specifies that the AWS_ACCESS_KEY_ID can only contain letters (A–Z, a–z) and numbers (0–9).
More info here Troubleshooting "The Access Key ID or Security Token is Invalid" Error after Upgrading DynamoDB Local to Version 2.0 or Greater
I d suggest to look into this article https://repost.aws/articles/ARc4hEkF9CRgOrw8kSMe6CwQ/troubleshooting-the-access-key-id-or-security-token-is-invalid-error-after-upgrading-dynamodb-local-to-version-2-0-or-greater as maybe could be slightly related?
It is probably related in a way that after they released 2.0 they also added some of the upgraded logic to 1.23.0. BUT 1.23 is a minor upgrade from 1.22, and this upgraded logic broke a functionality which worked before. All of our CI tests suddenly started failing, because we used empty strings as credentials in the tests.
DinamoDb-local doesn't check the credentials, so you can still set it any non-empty string.
Although it IS still an annoying issue, because our historical versions don't build anymore (All of the tests fails)
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 2 anni fa
My remark is about 1.23.0, not 2.0. 1.22 -> 1.23 is a minor upgrade and it contains a breaking change.