Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[dynamodb] global table grantReadWriteData not working for replicas of global Table

See original GitHub issue

My cdk stack is this :

1 ddb global table in us-east-1 replicating onto 3 other regions.
- global table nature for sync across regions
lambda and api gateway in all 4 regions.
lambda for each region interacting with the replica ddbs in that region.

I am using “@aws-cdk/aws-dynamodb”: “1.32.2”, in my package.json

when I use below command I see that the inline policy on my Lambda executionRole has all the desired Actions on only the us-east-1 table and not on the replicating regions

dynamoDBTable.grantReadWriteData(lambdaFunction as IGrantable);

Reproduction Steps

create cdk application
create ddb table in us-east-1
for other regions [eu-west-1, ap-northeast1, us-west-2] iterate over each and create lambdaFunction in each
dynamoDBTable.grantReadWriteData(lambdaFunction as IGrantable);
after cdk deploy open the lambdaFunction for eu-west-1 region on aws console and see executionRole in permissions
you will notice inline policy of that role to contain only permission on us-east-1 instead of eu-west-1

What did you expect to happen?

inline policy of lambdaExecution role to contain permission on eu-west-1 table

ensure execution role for each lambda in each region exists on corresponding ddb table (created via replication)

What actually happened?

execution role created only for original region (us-east-1) where the dynamodb Table got created using

new dynamoDB.Table(scope, id, tableProps);

Environment

CLI Version : NA
Framework Version: CDK 1.32.2
Node.js Version: v12.18.3
OS : mac
Language (Version): TypeScript

Other

This is 🐛 Bug Report

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

jogoldcommented, Sep 1, 2020

You need to upgrade all your @aws-cdk dependencies to at least 1.36.0

1reaction

jogoldcommented, Sep 1, 2020

@cdebojit the fix in https://github.com/aws/aws-cdk/pull/7453 has been released in v1.36.0 and you are apparently using v1.32.2? Can you try with a version >= 1.36.0?

Top Results From Across the Web

Troubleshoot DynamoDB error "cannot create a replica of table"

I'm trying to add a replica to an Amazon DynamoDB global table. but the operation fails with the exception “LimitExceededException” and throws ...

@aws-cdk/aws-dynamodb - npm

You only pay for what you use and there is no read and write capacity for the table or its global secondary indexes....

AWS CDK and Amazon DynamoDB global tables

The problem is that replicas created via the custom resource will not inherit that removalPolicy . This setting will only apply to the...

AWS CDK Lambda and DynamoDB dependency management

A discussion about issues we've stumbled upon and a solution that simplified our ... Managing dependencies between Lambdas and DynamoDB tables can get...

Global tables: How it works - Amazon DynamoDB - 亚马逊云科技

Do not modify these attributes or create attributes with the same name. You can add replica tables to the global table so that...