In this article
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Use this account type to connect DynamoDB Snaps with data sources that use DynamoDB accounts. The account now supports the IAM role, which can be selected by using the Authentication Types while setting up the account.
Prerequisites
None
Limitations and Known Issues
None
Account Settings
To create your DynamoDB Account, you must select the preferred Authentication Type options: User Credentials or IAM Role. The details are specified in the section DynamoDB Account Configuration Scenarios.
Asterisk ( * ): Indicates a mandatory field.
| Info |
|---|
|
): Indicates a list that is dynamically populated based on the configuration.Field Name | Field Type | Field Dependency | Description | ||
|---|---|---|---|---|---|
Label* Default Value: None | String | N/A | Specify a unique label for the account. | ||
AWS Endpoint* Default Value: None | String/Expression
| N/A | Specify the AWS end point URL. Refer to AWS Service end points for more information. | ||
AWS Region* Default Value: [None] | String/Expression
| N/A | Specify the AWS region where the application is running from the allowed values. | ||
Authenthication Type | Dropdown List | N/A | Select the Authentication Type from the following options:
| ||
AWS Access Key ID Default Value: [None] | String /Expression | Appears when you select User Credentials as Authentication Type. | Specify the access key ID associated with your AWS authentication. | ||
AWS Secret Key | String/Expression | N/A | Specify the secret key associated with your AWS authentication. | ||
AWS Security Token | String/Expression | N/A | Specify the security token to get access to AWS resources using credentials. | ||
Cross Account IAM Role | Use this field set to configure the cross account access. Learn more about setting up Cross Account IAM Role. | ||||
Role ARN Default Value: None | N/A | Specify the Amazon Resource Name (ARN) of the role to assume. | |||
External ID Default Value: None | N/A | Specify an external ID that might be required by the role to assume. | |||
DynamoDB Account Configuration Scenarios
Scenario description | Groundplex Type | Role attached to EC2 instance | Authentication Type and other details |
|---|---|---|---|
When the Groundplex type is AWS EC2 and the role attached to the EC2 instance is DynamoDB access role. | AWS EC2-type | DynamoDB access role. | Select Authentication Type as IAM Role. |
When the Groundplex type is AWS EC2 and the role attached to the EC2 instance is DynamoDB Cross Account access role. | AWS EC2-type | DynamoDB Cross Account access role. | Select Authentication Type as IAM Role and provide details for Cross account IAM Role. |
When you do not have AWS-EC2 groundplex and the role attached to the EC2 instance is DynamoDB access role. | User does not have AWS-EC2 groundplex. Value is from local machine. | DynamoDB access role | Select Authentication Type as User Credentials and provide details for the following fields:
|
When you do not have AWS-EC2 groundplex and the role attached to the EC2 instance is DynamoDB Cross Account access role. | User does not have AWS-EC2 groundplex. Value is from local machine. | DynamoDB Cross Account access role. | Select Authentication Type as User Credentials and provide details for the following fields:
|
Dynamo DB Permissions
The ListTables permission requires all resources (*) to be selected (as it needs to be able to list all the DynamoDB tables), but the others can have policies that are more limited (for example, to a particular table) as per the DynamoDB API Permissions reference. The most basic and permissive Policy document that could be assigned to the user that would guarantee all the required permissions are granted would be:
| Code Block |
|---|
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1482439123852",
"Action": [
"dynamodb:BatchGetItem",
"dynamodb:BatchWriteItem",
"dynamodb:DescribeTable",
"dynamodb:ListTables",
"dynamodb:Scan",
"dynamodb:UpdateItem"
],
"Effect": "Allow",
"Resource": "*"
}
]
} |
Troubleshooting
Error | Reason | Resolution |
|---|---|---|
Failed to validate account: Failed to connect to service endpoint. | The connection to the host failed. | Verify that the cross IAM role is not attached to EC2 instance. |
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|