Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
  • Asterisk ( * ): Indicates a mandatory field.

  • Suggestion icon ( (blue star) ): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ( (blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the fieldsetfield-set.

  • Remove icon ( (blue star) ): Indicates that you can remove fields from the fieldsetfield-set.

Field Name

Field Type

Field Dependency

Description

Label*

Default Value: None
Example: DynamoDB IAM Role

String

N/A

Specify a unique label for the account.

AWS Endpoint*

Default Value: None
Example: xyz876jhnJKBuya9730

String/Expression

 

N/A

Specify the AWS Endpoint URL. Refer to AWS Service Endpoints for more information.

AWS Region*

Default Value: None
Example: us-east-1

String/Expression

 

N/A

Specify the AWS region where the application is running from the allowed values.

Authenthication Type

Dropdown List

N/A

Select either of the following Authentication Types to create your DynamoDB Account:

  • User Credentials

  • IAM Role

Learn more about DynamoDB Account Configuration Scenarios.

Info

Cross Account IAM Role settings are available in the Account settings dialog box irrespective regardless of the Authentiction Authentication Type you choose.

AWS Access Key ID

Default Value: None
Example: us-east-1

String /Expression

Appears when you select User Credentials as Authentication Type.

Specify the Access Key ID associated with your AWS authentication.

AWS Secret Key

Default Value: N/A
Example: <Encrypted>

String/Expression

N/A

Specify the Secret Key associated with your AWS authentication.

AWS Security Token

Default Value: N/A
Example: <Encrypted>

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 - Setting up Cross Account IAM Role.

Role ARN

Default Value: N/A
Example: arn:aws:iam::612864912850:role/EC2_to_assume_role

N/A

Specify the Amazon Resource Name (ARN) of the role to assume.

External ID

Default Value: N/A
Example: <Encrypted>

N/A

Specify an External ID that might be required by the role to assume.

...

Scenario

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 the DynamoDB access role.

AWS EC2-type

DynamoDB access role.

Select Authentication Type as the IAM Role.

When the Groundplex type is AWS EC2 and the role attached to the EC2 instance is the DynamoDB Cross Account -account access role.

AWS EC2-type

DynamoDB Cross Account -account access role.

Select Authentication Type as IAM Role and provide details for the Cross account IAM Role.

When you do not have AWS-EC2 groundplex Groundplex and the role attached to the EC2 instance is the DynamoDB access role.

User does not have AWS-EC2 groundplexGroundplex. Value is from local machine.

DynamoDB access role

Select the Authentication Type as User Credentials and provide details for the following fields:

  • AWS Access Key ID

  • AWS Secret Key, and

  • AWS Security Token (optional).

When you do not have AWS-EC2 groundplex Groundplex and the role attached to the EC2 instance is the DynamoDB Cross Account -account access role.

User does not have an AWS-EC2 groundplex. Value is from local machine.

DynamoDB Cross Account -account access role.

Select Authentication Type as User Credentials and provide details for the following fields:

  • AWS Access Key ID

  • AWS Secret Key, and

  • AWS Security Token (optional).

  • Cross-account IAM Role.

Dynamo DB DynamoDB Permissions

The ListTables permission requires all resources (*) to be selected (as because 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 specific table) as per the DynamoDB API Permissions reference. The  Following is 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": "*"
    }
  ]
}

...