Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: AWS Lambda : Custom path needed in Sync through s3 option

Answered
LAKSHMANANATHAN M S User

Hi Team,

We have use case to load API data into Destination from different sources. Currently we are using Fivetran AWS Lambda custom connector with s3 sync option to do the same.

But Fivetran saving the file in default path in s3 bucket.

Default path: fivetran_aws_lambda_connector/fivetran/aws_lambda/

We want to store save the file with custom path like below. Assume below 3 connectors created to load API data from 3 different source 

<Connector1>/fivetran_aws_lambda_connector/fivetran/aws_lambda/

<Connector2>/fivetran_aws_lambda_connector/fivetran/aws_lambda/

<Connector3>/fivetran_aws_lambda_connector/fivetran/aws_lambda/

Could you please check the possibility of adding this feature to AWS LAMBDA connector with S3 sync option?

Note: Ticket 121568 raised to get details for the custom path.

Please let me know for more details.

Regards,

Lakshman

 

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Alison Fivetranner

    Hi Lakshman,

    Thank you for sharing your use case and associated details. Can you share more about why you are looking to change storage location?

    I'm not following why its going to help you to store the data in these locations?
    What value would you be using for <Connector1> etc.

    Alison