Closed sbstjn closed 7 years ago
A first step to a more secure solution would be at least a policy bound to the account and table name:
{
"Action": [
"dynamodb:DescribeTable",
"dynamodb:UpdateTable"
],
"Resource": "arn:aws:dynamodb:*:AccountID:table/TableName",
"Effect": "Allow"
}
Included in the 0.1.1
release.
The permissions for the created role must have a restricted access policy. The current implementation should not be used in production environments.