Configuring Amazon AppFlow

The Lazsa Platform leverages Amazon AppFlow connector for ingesting data from SaaS services like Salesforce or ServiceNow to a data lake like Amazon S3 or Snowflake. For this type of data ingestion, you must first configure an Amazon AppFlow service, then create an AppFlow connector for Salesforce, ServiceNow, or Snowflake. Once these steps are complete, then you can configure the SaaS applications as data sources or use Snowflake as a data lake in the data pipelines.

To configure Amazon AppFlow

1. Sign in to the Lazsa Platform and click Configuration in the left navigation pane.
2. On the Platform Setup screen, on the Cloud Platform, Tools & Technologies tile, click Configure.
3. On the Cloud Platform, Tools & Technologies screen, in the Data Integration section, click Configure.
   (After you save your first connection details in this section, you see the Modify button here.)
   
   

4. In the list of available data integration tools, click .

5. On the Amazon Appflow connection details screen, do the following:

   1. In the Details section, provide the following details:

      Field	Description
      Name	Give a unique name to your Amazon Appflow configuration. This name is used to save and identify your specific Amazon Appflow connection details within theLazsa Platform.
      Description	Provide a brief description that helps you identify the purpose or context of this Amazon Appflow configuration.

   2. In the Configuration section, depending on how you want to retrieve the access credentials to connect to your Amazon AppFlow, do one of the following:

      Field

      Description

      Connect using Lazsa Orchestrator Agent

      Enable this option to resolve your Amazon Appflow access credentials within your private network via Lazsa Orchestrator Agent without sharing them with the Lazsa Platform. Lazsa Orchestrator Agent - Select the Lazsa Orchestrator Agent that you want to use from the list of your configured agents. AWS Account ID - This is automatically populated, based on the AWS account in which the Lazsa Orchestrator Agent is deployed. If the Lazsa Orchestrator Agent and AWS AppFlow are in different AWS accounts, then you must do the following: Cross-Account Configured - Enable this option. Provide the following information: Region: From the dropdown list, select the AWS availability region where the Amazon Appflow instance is located. External ID Key: Provide the key in the AWS Secrets Manager secret containing the External ID value. Cross Account Role ARN Key: The key in the AWS Secrets Manager secret containing the Cross Account Role ARN value.

   3. In the Configuration section, provide the following information:

      Field	Description
      AWS Account	Enter the name of your AWS account.
      AWS Account ID	The AWS Account ID is automatically populated.
      Region	From the dropdown list, select the AWS availability region where the Amazon Appflow instance is located.
      External ID	Provide the external ID for the AWS account.

   4. Secure configuration details with a password
      To password-protect your Amazon AppFlow connection details, turn on this toggle, enter a password, and then retype it to confirm. This is optional but recommended. When you share the connection details with multiple users, password protection helps you ensure authorized access to the connection details.
      

   5. Click Save Configuration. The configured connection details, you can see the configuration listed on the Databases and Data Warehouses screen.
      
      Sample Connection Details Configured for Amazon AppFlow:
      
      

Recommended Topics

What's next? Cloud Platforms, Tools, and Technologies