Motivation

As reported by a user, we had a red herring regarding some raised DynamoDB Streams error when used with ESM (with non default account and region):

2024-11-19T14:51:15.731 ERROR --- [functhread29] l.s.l.e.esm_worker     : Error while polling messages for event source arn:aws:dynamodb:us-west-2: 000000000001:table/<table-name>/stream/2024-11-18T14:36:43.932: An error occurred (ResourceNotFoundException) when calling the DescribeStream operation: Requested resource not found: Stream: arn:aws:dynamodb:ddblocal:000000000000:table/<table-name>/stream/2024-11-18T14:36:43.932 not found

Which made it look like we were not properly formatting the ARN or something related to DDB Local.

The issue was that we were not replacing the ARN value in the exception as it was directly raised by DDB-local, but our headers were correct for the namespacing.

Also, made a quick fix to start DDB-local in DynamoDB Streams v2 because if you targeted the dynamodbstreams service before doing a request to dynamodb, you would get a connection refused error as we'd try to send a request to it. I'm not adding all the hooks related to persistence because those services are very intertwined and this would only happen at startup with a fresh instance.

Changes

• add more regex replacement on raised exception on DDB
• add a test for this specific issue, and do a quick format fix for v1