there may be a bug with managing dynamodb tables in localstack using aws-sdk-go-v2. my team stumbled upon this while migrating an application from aws-sdk-go v1 to v2.
to reproduce this locally, run docker compose up
to spin up localstack, then run go run main.go
(either in a separate terminal, or in the same if docker compose is run in the background.)
main.go
- connects to localstack (success)