-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Open
Labels
aws:dynamodbAmazon DynamoDBAmazon DynamoDBstatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When using ARNs with transactions we are seeing failures in localstack.
This issue was initially surfaced during testing with the aws-sdk-go-v2 client, also reproduced with boto3, and here with the CLI.
Expected Behavior
Using ARNs with Transactions works with DynamoDB in production, and the ARNs are needed there to properly construct the endpoints to access those tables.
How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
aws dynamodb transact-write-items --endpoint-url http://localhost:4566 \
--transact-items '[{
"Put": {
"TableName": "arn:aws:dynamodb:us-east-1:000000000000:table/example-table",
"Item": { ... }
}
}]'
An error occurred (ResourceNotFoundException) when calling the TransactWriteItems operation: Cannot do operations on a non-existent table
or
aws dynamodb transact-get-items --endpoint-url http://localhost:4566 \
--transact-items '[{
"Get": {
"TableName": "arn:aws:dynamodb:us-east-1:000000000000:table/example-table",
"Key": { ... }
}
}]'
An error occurred (ResourceNotFoundException) when calling the TransactGetItems operation: Cannot do operations on a non-existent table
Environment
- LocalStack:
LocalStack version: 4.9.2Anything else?
No response
Metadata
Metadata
Assignees
Labels
aws:dynamodbAmazon DynamoDBAmazon DynamoDBstatus: backlogTriaged but not yet being worked onTriaged but not yet being worked ontype: bugBug reportBug report