Skip to main content

Conduit DynamoDB Connector v0.3.0

· 2 min read

Today, we released Conduit DynamoDB Connector v0.3.0, adding the ability to connnect to the source connector with a session token via aws.sessionToken to help those users who can't use IAM roles.

More information

New source field aws.sessionToken to connect to the source connector with a session token.

version: 2.2
pipelines:
- id: example
status: running
connectors:
- id: example
plugin: "dynamodb"
settings:
# AWS temporary session token. Note that to keep the connector running
# long-term, you should use an IAM user with no temporary session
# token. If the session token is used, then the connector will fail
# once it expires.
# Type: string
# Required: no
aws.sessionToken: ""
warning

We still recommend our users to use IAM roles instead of session tokens, as the session token will expire and the connector will stop working. If you need to use a session token, make sure to refresh it periodically.

Here's what we recommend using instead:

version: 2.2
pipelines:
- id: example
status: running
connectors:
- id: example
plugin: "dynamodb"
settings:
# AWS access key id.
# Type: string
# Required: yes
aws.accessKeyId: ""
# AWS secret access key.
# Type: string
# Required: yes
aws.secretAccessKey: ""

This is a temporary solution until we implement a more robust way to handle session tokens.

If you have any questions, or more feedback feel free to join our Discord Community

tip

For more information, check out the DynamoDB Connector documentation.

scarf pixel conduit-site-changelog