Amazon DynamoDb-local java 1.23.0 has a breaking change

0

In the previous versions you can set the access-key and secret-key to "" (empty string), like:

...
.withCredentials(new AWSStaticCredentialsProvider(new BasicAWSCredentials("", "")))
...

it doesn't work any more. You will get an exception during startup.

demandé il y a un an313 vues
3 réponses
0

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

profile pictureAWS
EXPERT
répondu il y a un an
  • My remark is about 1.23.0, not 2.0. 1.22 -> 1.23 is a minor upgrade and it contains a breaking change.

-1
  • 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.

-1

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)

répondu il y a un an

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions