Amazon DynamoDB (Early Access) connector
Updated
The Amazon DynamoDB (Early Access) connector lets you read, write, query, and delete data in Amazon DynamoDB, a fully managed, serverless NoSQL database service. The connector authenticates with AWS and supports DynamoDB single-item, batch, transaction, PartiQL, and table-management APIs.
Connector configuration
To configure the connector to communicate with DynamoDB, set up the following components:
- Amazon DynamoDB connection
- Amazon DynamoDB operation The connection stores the AWS credentials and regional endpoint. Operations define the request and response for each action. After you build the connection and operation, set up the connector within a process.
Supported actions
The connector supports the following actions:
- Inbound: Get, Query
- Outbound: Upsert, Update, Delete, Create
- In/Outbound: Execute The Execute action runs PartiQL statements, transactions, and table listing or description. Refer to the Amazon DynamoDB operation topic for each object.
Prerequisites
The following prerequisites are necessary to connect to Amazon DynamoDB:
- An active AWS account with at least one DynamoDB table.
- An IAM user or role with the DynamoDB permissions your process needs.
- The AWS Access Key ID and Secret Access Key for that IAM identity. For IAM Roles Anywhere, use the certificate and trust anchor material instead.
- A Boomi AtomSphere account with permission to add connections and deploy processes.
Tracked properties
The connector has one tracked property, Result Type.
| Value | Meaning |
|---|---|
| success | Indicates a successful operation. Read requests return each matching DynamoDB item as an individual document (or a single empty {} document if no matches are found). Write requests return a single empty {} document since DynamoDB returns no payload for writes. Table listing operations (List Tables and List Global Tables) yield a single document containing all listed items. |
| unprocessed | DynamoDB accepted the request but could not complete a portion of it, and connector retries also failed. For Get (Items), the document contains unretrieved primary keys. For Upsert (Items) and Delete (Items), it contains items that were not written or deleted. The document retains the original request format for easy remapping into a retry step. Only Get (Items), Upsert (Items), Delete (Items) return this status. |
| error | • If a request fails, the output document includes Error.Type and Error.Message details explaining the failure. Error handling behavior varies by operation type. Most operations return a single error document and halt execution. • Execute Statements: If a statement is blank or rejected by DynamoDB, an error document echoing its Statement and Parameters is generated, allowing the remaining batch statements to proceed. However, if DynamoDB rejects an entire batch of up to 25 statements at once, a single consolidated error document is returned for the group. • Execute (Transact Get Items) & Execute (Transact Write Items): The entire transaction fails atomically, producing a single error document that contains the submitted TransactItems. For Execute (Transact Write Items), the document additionally provides CancellationReasons listed in submission order, identifying the specific action that triggered the failure alongside those that were rolled back. |
Use Result Type in a Decision shape after the connector step to branch on the outcome.
