The following tutorial shows how you can leverage Progress DataDirect Salesforce JDBC drivers to import the data from Salesforce into S3 storage engine.
AWS Data Pipeline is a web service that lets you process, transform and move the data securely between AWS Storage and compute services in regular intervals. In addition to this there is also one neat feature which enables you connect to any database with JDBC driver and import the data in to S3 which you can use later to move it across either compute or storage services in AWS.
This tutorial explains how to leverage the Progress DataDirect Salesforce JDBC Driver to import the data from Salesforce into S3 storage engine with minimal effort and by creating a pipeline which you can essentially re-use multiple times.
Once the pipeline is saved without any errors, you can activate the pipeline. Depending on the schedule that you have configured, the pipeline should run and create a CSV file which contains Accounts Table data read from DataDirect Salesforce JDBC drivers. It should be present in the path that you have configured in the S3DataNode.
We hope this tutorial helped you to import Salesforce data into Amazon S3 using Amazon Data Pipeline, which you can use to import it in to various Amazon Compute services. This demonstration is not limited to Salesforce. In fact, you can create Amazon Data Pipeline with any of the DataDirect JDBC drivers to connect and import data from over 50+ data sources which includes your favorite SaaS, Relational and Big data sources.
Try Free for 30 Days
Saikrishna is a DataDirect Developer Evangelist at Progress. Prior to working at Progress, he worked as Software Engineer for 3 years after getting his undergraduate degree, and recently graduated from NC State University with Masters in Computer Science. His interests are in the areas of Data Connectivity, SaaS and Mobile App Development.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.