Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Replicate Amazon Athena Data in Heroku for Use in Salesforce Connect
Replicate Amazon Athena data to a PostgreSQL database on Heroku and connect it to Salesforce using Salesforce Connect.
CData Sync is a standalone application that supports a wide range of replication scenarios, including replicating both sandbox and production instances into your database. By replicating Amazon Athena data to a PostgreSQL database in Heroku, you can access Amazon Athena external objects (via Salesforce Connect) alongside standard Salesforce objects.
About Amazon Athena Data Integration
CData provides the easiest way to access and integrate live data from Amazon Athena. Customers use CData connectivity to:
- Authenticate securely using a variety of methods, including IAM credentials, access keys, and Instance Profiles, catering to diverse security needs and simplifying the authentication process.
- Streamline their setup and quickly resolve issue with detailed error messaging.
- Enhance performance and minimize strain on client resources with server-side query execution.
Users frequently integrate Athena with analytics tools like Tableau, Power BI, and Excel for in-depth analytics from their preferred tools.
To learn more about unique Amazon Athena use cases with CData, check out our blog post: https://www.cdata.com/blog/amazon-athena-use-cases.
Getting Started
Requirements
For this replication example, you need the following:
- CData Sync (trial or licensed), along with a license (full or trial) for Amazon Athena replication.
- A Heroku app with the Heroku Postgres and Heroku Connect add-ons provisioned.
- A Salesforce account.
Configure the Replication Destination
Using CData Sync, you can easily replicate data from Amazon Athena data to a PostgreSQL database on Heroku. For this article, you will need an existing PostgreSQL database on Heroku. To add your PostgreSQL database as a replication destination, navigate to the Connections tab.
- Click Add Connection.
- Select the Destinations tab and locate the PostgreSQL connector.
- Click the Configure Connection icon at the end of that row to open the New Connection page. If the Configure Connection icon is not available, click the Download Connector icon to install the PostgreSQL connector. For more information about installing new connectors, see Connections in the Help documentation.
- To connect to PostgreSQL, set the following connection properties:
- Connection Name: Enter a connection name of your choice for the PostgreSQL connection.
- Server: Enter the host name or IP of the server that hosts the PostgreSQL database. The default server value is localhost.
- Auth Scheme: Select the authentication scheme. The default auth scheme is Password.
- Port: Enter the port number of the server that hosts the PostgreSQL database. The default port value is 5432.
- User: Enter the user ID provided for authentication with the PostgreSQL database.
- Password: Enter the password provided for authentication with the PostgreSQL database.
- Database: Enter the name of the database. If not specified, use the default database.
- Once connected, click Create & Test to create, test and save the connection.
You are now connected to PostgreSQL and can use it as both a source and a destination.
NOTE: You can use the Label feature to add a label for a source or a destination.
Configure the Amazon Athena Connection
You can configure a connection to Amazon Athena from the Connections tab. To add a connection to your Amazon Athena account, navigate to the Connections tab.
- Click Add Connection.
- Select a source (Amazon Athena).
- Configure the connection properties.
Authenticating to Amazon Athena
To authorize Amazon Athena requests, provide the credentials for an administrator account or for an IAM user with custom permissions: Set AccessKey to the access key Id. Set SecretKey to the secret access key.
Note: Though you can connect as the AWS account administrator, it is recommended to use IAM user credentials to access AWS services.
Obtaining the Access Key
To obtain the credentials for an IAM user, follow the steps below:
- Sign into the IAM console.
- In the navigation pane, select Users.
- To create or manage the access keys for a user, select the user and then select the Security Credentials tab.
To obtain the credentials for your AWS root account, follow the steps below:
- Sign into the AWS Management console with the credentials for your root account.
- Select your account name or number and select My Security Credentials in the menu that is displayed.
- Click Continue to Security Credentials and expand the Access Keys section to manage or create root account access keys.
Authenticating from an EC2 Instance
If you are using the CData Data Provider for Amazon Athena 2018 from an EC2 Instance and have an IAM Role assigned to the instance, you can use the IAM Role to authenticate. To do so, set UseEC2Roles to true and leave AccessKey and SecretKey empty. The CData Data Provider for Amazon Athena 2018 will automatically obtain your IAM Role credentials and authenticate with them.
Authenticating as an AWS Role
In many situations it may be preferable to use an IAM role for authentication instead of the direct security credentials of an AWS root user. An AWS role may be used instead by specifying the RoleARN. This will cause the CData Data Provider for Amazon Athena 2018 to attempt to retrieve credentials for the specified role. If you are connecting to AWS (instead of already being connected such as on an EC2 instance), you must additionally specify the AccessKey and SecretKey of an IAM user to assume the role for. Roles may not be used when specifying the AccessKey and SecretKey of an AWS root user.
Authenticating with MFA
For users and roles that require Multi-factor Authentication, specify the MFASerialNumber and MFAToken connection properties. This will cause the CData Data Provider for Amazon Athena 2018 to submit the MFA credentials in a request to retrieve temporary authentication credentials. Note that the duration of the temporary credentials may be controlled via the TemporaryTokenDuration (default 3600 seconds).
Connecting to Amazon Athena
In addition to the AccessKey and SecretKey properties, specify Database, S3StagingDirectory and Region. Set Region to the region where your Amazon Athena data is hosted. Set S3StagingDirectory to a folder in S3 where you would like to store the results of queries.
If Database is not set in the connection, the data provider connects to the default database set in Amazon Athena.
- Click Connect to Amazon Athena to ensure that the connection is configured properly.
- Click Save & Test to save the changes.
Configure Queries for Each Amazon Athena Instance
CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.
Replicate Entire Tables
To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Amazon Athena tables you wish to replicate into PostgreSQL, and click Add Tasks again.
Customize Your Replication
You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication with the help of SQL queries.
As you make changes using the interface, the SQL query used for the replication changes, going from something simple, like this:
REPLICATE [Customers]
to something customized and more complex, like this:
REPLICATE [Customers] SELECT [Name], [TotalDue] FROM [Customers] WHERE [CustomerId] = 12345
Schedule Your Replication
Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at specified intervals, ranging from once every 10 minutes to once every month.
Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Amazon Athena data to PostgreSQL.
Run the Replication Job
Once all the required configurations are made for the job, select the Amazon Athena table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.
The Amazon Athena data tables are now replicated in Heroku PostgreSQL database.
Connect to Your Replicated Amazon Athena Data as an External Data Source
Once your Amazon Athena data is replicated to the PostgreSQL database on Heroku, configure the OData interface for Heroku and connect to the database as an external data source via Salesforce Connect.
Configure the OData Service for Heroku
The first part of connecting to Amazon Athena data replicated to a PostgreSQL database on Heroku is configuring the Heroku External Objects for the database.
- In your Heroku dashboard, click the Heroku Connect Add-On.
- Select External Objects. (If this is the first time using Heroku External Object, you will be prompted to create the OData service's login credentials)
- View the OData service URL and credentials (noting the URL and credentials to be used later from Salesforce Connect).
- In Data Sources, select which replicated tables to share.
Refer to the Heroku documentation for more detailed instructions.
Configure an External Data Source in Salesforce
After the OData service for Heroku is configured, we can connect to the replicated Amazon Athena data as an external data source from Salesforce Connect.
- In Salesforce, click Setup
- In the Administration section, click Data -> External Data Sources
- Set the data source parameter properties:
- External Data Source: the name you wish to display in the Salesforce user interface
- Name: a unique identifier for the API
- Type: Salesforce Connect: OData 4.0
- URL: Enter the OData endpoint from Heroku Connect (above)
- Format: JSON
- Set Authentication:
- Identity Type: Named Principal
- Authentication Protocol: Password Authentication
- Username: the Heroku Connect username
- Password: the Heroku Connect password
- Click Save.
Synchronize Amazon Athena Objects
After you have created the external data source in Salesforce, follow the steps below to create Amazon Athena external objects that reflect any changes in the data source. You will synchronize the definitions for the Amazon Athena external objects with the definitions for Amazon Athena tables.
- Click the link for the external data source you created.
- Click Validate and Sync.
- Select the Amazon Athena tables you want to work with as external objects and click Sync.
Access Amazon Athena Data as Salesforce Objects
At this point, you will be able to connect to and work with your replicated Amazon Athena entities as external objects just as you would with standard Salesforce objects, whether you are simply viewing the data or building related lists of external Amazon Athena data alongside standard Salesforce objects.
Download a 30-day free trial of CData Sync and replicate your Amazon Athena data for use with Salesforce Connect today!