The Connect to Destination without OAuth or S3 Pull block is used to fetch or pull files stored in an Amazon S3 bucket. It acts as a source block, meaning it pulls data that can then be used for further processing, transformations, or validations within a dataflow. This block connects to the S3 bucket using AWS Access Key and Secret Key credentials.

Use Case

Requirement

A company stores customer transaction data in an S3 bucket after every purchase made on its e-commerce platform. The data is stored in .csv format and must be pulled into the Capillary platform for further processing and allocation of loyalty points.

Solution

Create a template with the Connect to Destination without OAuth block to fetch the file from the specified S3 bucket. Once the files are pulled from S3, you can use the Transform Data block or Neo Transformer for parsing, validating, and mapping fields before pushing to Capillary's APIs. to process the data and allocate loyalty points.

Configuring the Connect to Destination without OAuth Block

Pre-Requisite

The following are the prerequisites for the Connect to Destination without OAuth block:

• AWS Access Key and Secret Key with read permissions for the S3 bucket.
  For Access Key and Secret, create a ticket with the Capillary Access team.
• Bucket Name and the Region where your files are stored.

For details on adding column headers, refer to Defining column header.