AWS DynamoDB Connection
Region, Endpoint
Specifies the region to use when connecting to Amazon Web Services, and dictates where tables are read from and written to. If Other Region is selected, specify a region manually under Endpoint, using the full endpoint (for example, dynamodb.eu-west-1.amazonaws.com.)
Note: Note: DynamoDB tables are region-dependent, so selecting an incorrect region will prevent your table from appearing in the table list.
Access Key ID
The AWS Access Key ID of the user who will access the database.
The user must exist with appropriate DynamoDB permissions. If this entry is not found, the access key ID will be searched for in various places. These are, in order:
- a file called AwsCredentials.properties on the Java classpath
- aws.accessKeyId in the Java system properties
- the environment variable AWS_ACCESS_KEY_ID
Once a pair of credentials is found, the search will stop.
Secret Access Key
The secret access key associated with the user accessing the database.
If this parameter is not found, the secret key will be searched for in various places. These are, in order:
- a file called AwsCredentials.properties on the Java classpath
- aws.secretKey in the Java system properties
- the environment variable AWS_SECRET_KEY
Once a pair of credentials is found, the search will stop.
Constraints
Table List
After you have specified the database connection, click the Browse button to select tables for import. A connection window appears while the system compiles a table from the database.
Once the table list appears, you can select one or more tables, and then click OK to dismiss the window. The table name(s) will appear in the Table List field in the parameter box.
Note: If the table list does not display your table, ensure you have selected the appropriate region in the writer parameters. DynamoDB tables are region-dependent, so selecting an incorrect region will prevent your table from appearing in the table list.
Schema Attributes
Additional Attributes to Expose
Use this parameter to expose Format Attributes in Workbench when you create a workspace:
- In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
- In a non-dynamic scenario where you have multiple feature types, it is convenient to expose additional attributes from one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.