You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DynamoDBCrudPolicy currently only allows the table name to be configured. The region is always assumed to be the same region as the resource being deployed. We should be able to override the region in order to easily allow e.g deploying a lambda that can access a dynamodb table in a different region like so:
I'm aware that I can manually copy + paste the expanded definition for DynamoDBCrudPolicy into my SAM template, but allowing the region to be specified as proposed will make things easier.
The text was updated successfully, but these errors were encountered:
The
DynamoDBCrudPolicy
currently only allows the table name to be configured. The region is always assumed to be the same region as the resource being deployed. We should be able to override the region in order to easily allow e.g deploying a lambda that can access a dynamodb table in a different region like so:I'm aware that I can manually copy + paste the expanded definition for
DynamoDBCrudPolicy
into my SAM template, but allowing the region to be specified as proposed will make things easier.The text was updated successfully, but these errors were encountered: