Configuring S3 Bucket integration for RDS for PostgreSQL Exports in Builder

If you navigate to Settings > Advanced Settings > Integrations, you'll find a setting related to configuring your own S3 bucket to export data from RDS for PostgreSQL data sources in Builder.

When is this needed?

Utilize this integration when you need to export geospatial data from your RDS for PostgreSQL database in Builder. CARTO incorporates an S3 bucket as a necessary intermediary step, adhering to the requirements of RDS for PostgreSQL.

Requirements for Integration:

  1. Private S3 Bucket: Before you can configure this integration, create an S3 private bucket in AWS.

    • Best Practice: We recommend setting up a new S3 bucket exclusively for this purpose, ensuring better organization and enhanced security.

  2. AWS S3 Extension Setup: The integration also depends on the AWS S3 extension being pre-installed in your PostgreSQL environment.

    • Need Help? If this step is not yet completed, or you need assistance with it, please refer to the official AWS documentation for detailed guidance.

Setting up your S3 bucket integration

Start by clicking '+ Add' to initiate the setup. For your S3 private bucket, you'll need to provide the following four parameters:

  • Bucket Name: Enter the name of your S3 bucket for data export.

  • Bucket Region: Specify your S3 bucket's region.

  • Access Key ID: Provide your AWS account's Access Key ID.

  • Access Key Secret: Enter the corresponding Access Key Secret.

Once you've added the required fields, click on "Validate and Save". This will established the S3 bucket integration to enable RDS for PostgreSQL exports.

CARTO will validate your configuration at this point. If we're able to use your S3 bucket to export files from RDS for PostgreSQL, we'll take you back to your Settings page.

From this point, CARTO will always use your S3 bucket when exporting sources from RDS for PostgreSQL, and the export viewport data feature in Builder will be enabled if it wasn't before

You can edit or remove this integration at any time.

Last updated