Home > Blockchain >  Using Step Function Optimised Integration to access a DynamoDB table in another region
Using Step Function Optimised Integration to access a DynamoDB table in another region

Time:11-19

We have an AWS Step Function which uses the DynamoDB Optimised Integration to update items within a DynamoDB table. Both of these are deployed to the same region, Region A, and work perfectively well.

We would like to deploy the Step Function to another region B. This is effectively the same Step Function, and the intention is that it will access the original DynamoDB table that is still in Region A.

However, looking at the documentation on the DynamoDB Optimised Integration, I don't see a way in which I can specify the region of the table I want the Step Function to access. It seems to assume that the table is in the same region as the Step Function.

Is there a way for the Step Function to use the DynamoDB Optimised Integration to access a DynamoDB table in a different region?

Note: I'm aware that Global Tables and Lambdas would work here. But I'd like to know if this is possible before considering these options.

CodePudding user response:

You can't access a Dynamo table in another region using the integration, it assumes the region endpoint and doesn't have any option to set the endpoint like the SDK does.

  • Related