Commit fe5318e
DynamoDBConnection always built the client via
new AmazonDynamoDBClient(mCredentials, mConfig). When the datastore's
User_id / User_password properties are left empty (to authenticate via the
EC2 instance's IAM role), mCredentials is null and passing it explicitly
prevents the AWS SDK from using its default credential resolution chain, so
requests go out unsigned and fail with "Request is missing Authentication
Token".
Mirror what ExternalProviderS3 already does:
- Only build BasicAWSCredentials when both User_id and User_password are
present AND non-empty (previously a present-but-empty value produced empty
credentials).
- When there are no explicit credentials, use the config-only constructor
new AmazonDynamoDBClient(mConfig), which engages the default credential
chain (incl. the EC2 instance profile / IAM role).
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 43300d3 commit fe5318e
1 file changed
Lines changed: 8 additions & 2 deletions
Lines changed: 8 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
52 | 52 | | |
53 | 53 | | |
54 | 54 | | |
55 | | - | |
| 55 | + | |
| 56 | + | |
56 | 57 | | |
57 | 58 | | |
58 | 59 | | |
| |||
75 | 76 | | |
76 | 77 | | |
77 | 78 | | |
78 | | - | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
79 | 85 | | |
80 | 86 | | |
81 | 87 | | |
| |||
0 commit comments