Amazon DynamoDB: Role-based IAM Auth with External ID
Amazon DynamoDB destinations now support role-based IAM authentication with an External ID, preventing the confused deputy problem. Users can enable role-based auth via a toggle that generates a Fivetran-managed External ID to add to their AWS IAM trust policy, ensuring only their Fivetran account can assume the role.
Amazon DynamoDB now supports role-based IAM authentication with an External ID to prevent the confused deputy problem.
When setting up a DynamoDB destination, you can now enable the Use Role-based Auth toggle. This generates a Fivetran-managed External ID (a 24-character base58 string) that you add to your AWS IAM trust policy alongside your Role ARN. Fivetran uses this External ID when assuming the role, ensuring only your Fivetran account can do so.
Legacy access-key connections are unaffected.
Source: original entry ↗
More from Census
Follow Census to get its new changes in your feed and email digest.
Braze: Email and User Alias as Identifiers
The Braze connector now supports email and user_alias as user identifiers for Event and PurchaseEvent syncs, alongside the existing external_id option, providing more flexibility in data synchronization.
LinkedIn Conversions: lead as an Optional Field
LinkedIn Conversions now supports an optional lead field to map Lead Gen Form Response IDs and attribute conversion events to specific lead forms.
API V2 Beta Endpoints Now Available
Census introduces the first V2 API endpoints with a new Sources API that supports region and storage backend selection, Group ID management for access controls, and Personal Access Token authentication. Workspaces have been removed from the API and Workspace API Keys are no longer supported.