Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Configuring a source for a zero-ETL integration

Focus mode
Configuring a source for a zero-ETL integration - AWS Glue

Configuring an Amazon DynamoDB source

To access data from your source Amazon DynamoDB table, AWS Glue requires access to describe the table and export data from it. Amazon DynamoDB recently introduced a feature which allows configuring a Resource Based Access (RBAC) policy.

The following example Resource Based Access (RBAC) Policy uses a wild card (*) for integration:

{ "Version": "2012-10-17", "Statement": [{ "Sid": "1111", "Effect": "Allow", "Principal": { "Service": "glue.amazonaws.com" }, "Resource":"*", "Action": [ "dynamodb:ExportTableToPointInTime", "dynamodb:DescribeTable", "dynamodb:DescribeExport" ], "Condition": { "StringEquals": { "aws:SourceAccount": "<account-id>" }, "StringLike": { "aws:SourceArn": "arn:aws:glue:<region>:<account-id>:integration:*" } } }] }
  1. For the DynamoDB that you want to replicate, paste the above RBAC policy template into Resource-based policy for table and fill in the fields.

  2. If you want to make the policy restrictive, you must update the policy after creating the integration and specify the full integrationArn and use the StringEquals condition instead of StringLike.

  3. Make sure that Point-in-time recovery (PITR) is enabled for the DynamoDB table.

  4. Make sure that you add Describe Export to the Resource Based Access (RBAC) policy.

You can also add the RBAC policy to the table using the following command:

aws dynamodb put-resource-policy \ --resource-arn arn:aws:dynamodb:<region>:<account-id>:table/<ddb-table-name> \ --policy file://resource-policy-with-condition.json \ --region <region>

To verify that policy is applied correctly, use the following command to get the resource policy for a table:

aws dynamodb get-resource-policy \ --resource-arn arn:aws:dynamodb:<region>:<account-id>:table/<ddb-table-name> --region <region>

Configuring a Salesforce source

To create a connection for an SAP OData source, see Connecting to Salesforce.

Once you've created the connection, you can specify the source data to replicate.

The screenshot shows specifying source data to replicate in a zero-ETL integration.

Using your zero-ETL integration you can perform DDL operations for supported entities. For a list of entities which are not supported, see Unsupported entities and fields for Salesforce.

Configuring a Salesforce Marketing Cloud Account Engagement source

To create a connection for an Salesforce Marketing Cloud Account Engagement source, see Connecting to Salesforce Marketing Cloud Account Engagement .

Using your zero-ETL integration you can perform DDL operations for the following supported entities:

Entity label Entity name
Campaign campaign
List list
Dynamic Content dynamic-content
List Membership list-membership
Prospect prospect
User user
EmailTemplate email-template
EngagementStudioProgram engagement-studio-program
Landing Page landing-page
List Email list-email

Configuring an SAP OData source

To create a connection for an SAP OData source, see Connecting to SAP OData .

The SAP OData connector in a zero-ETL integration doesn't support entities starting with EntityOf.

Configuring a ServiceNow source

To create a connection for a ServiceNow source, see Connecting to ServiceNow .

Configuring a Zendesk source

To create a connection for a Zendesk source, see Connecting to Zendesk .

Using your zero-ETL integration you can perform the following DDL operations for supported entities:

Entity label Entity name Create supported Update supported Delete supported
Tickets tickets Y Y Y
User users Y Y Y
Satisfaction Rating satisfaction-rating Y Y N
Articles articles Y Y N
Organization organizations Y Y Y
Calls calls Y Y N
Call Legs legs Y Y N

Configuring a Zoho CRM source

To create a connection for a Zoho CRM source, see Connecting to Zoho CRM .

Using your zero-ETL integration you can perform the following DDL operations for supported entities:

Entity label Entity name DML-Insert supported DML-Modify supported DML-Delete supported DDL-Insert supported DDL-Modify supported DDL-Delete supported
Leads lead Y Y Y Y Y Y
Accounts account Y Y Y Y Y Y
Contacts contact Y Y Y Y Y Y
Campaigns campaign Y Y Y Y Y Y
Tasks task Y Y Y Y Y Y
Events event Y Y Y Y Y Y
Calls call Y Y Y Y Y Y
Solutions solution Y Y Y Y Y Y
Products product Y Y Y Y Y Y
Vendors vendor Y Y Y Y Y Y
Quotes quote Y Y Y Y Y Y
Sales Orders sales-order Y Y Y Y Y Y
Purchase Orders purchase-order Y Y Y Y Y Y
Invoices invoice Y Y Y Y Y Y
Cases case Y Y Y Y Y Y
Price Books price-book Y Y Y Y Y Y

Configuring a Facebook Ads source

To create a connection for a Facebook Ads source, see Connecting to Facebook Ads .

Using your zero-ETL integration you can perform the following DDL operations for supported entities:

Entity label Entity name Create supported Update supported Delete supported
Adset */adsets Y Y Y
Campaign */campaigns Y Y Y
Ads */ads Y Y Y

Configuring an Instagram Ads source

To create a connection for an Instagram Ads source, see Connecting to Instagram Ads .

Using your zero-ETL integration you can perform the following DDL operations for supported entities:

Entity name Create supported Update supported Delete supported
*/adsets Y Y Y
*/campaigns Y Y Y
*/ads Y Y Y
PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.