Skip to main content
Automatic Exports on Qomon

Read this article to find out how to configure automatic exports on Qomon using S3

Clare Atreo avatar
Written by Clare Atreo
Updated over a week ago

What is S3 Configuration?

Simple Storage Service (S3) is a storage service that can be set up with almost any cloud service provider. It allows you to store and safeguard large amounts of data and is very secure and efficient. Users of various sizes and industries can utilize S3 for different purposes: like storing data for websites, mobile apps, backups, archives, and more. It offers management features to help you organize and control access to your data based on your business and compliance needs.

Qomon and S3 for auto exports

Qomon users configure S3 to obtain automatic exports from their contact database(s) for a certain category of people and a certain locale or period of time. An example would be if you have an organization account with 50 different spaces and want an export from each space at the end of the week with all new contacts.

S3 exports contain all fields available in exports directly initiated from the web app. You have the option to select the specific fields you wish to include in your automatic exports, giving you control and customization over your data exports.

What do we need from you?

  • Access ID

  • Secret Key

  • Endpoint

  • Region

  • Bucket

  • ACL (Access Control List)

Find descriptions of each below:

💻 Access ID

The first step is to create an Access ID. This is a unique identifier associated with your account/user. Your Access ID must be globally unique, so ensure that it is specific to the desired bucket or storage area, and not short or generic.

Example Access ID’s for different cloud providers:

  • AWS: AKIAIOSFODNN7EXAMPLE

  • Google Cloud: my-access-id-12345

  • Scaleway: SCW1T7KPT8NHZVCDJQ4X

🔑 Secret Key

You will need to create a secret key, a token associated with your Access ID. This is an extra layer of security and should be kept confidential! It should be treated as sensitive information and protected accordingly.

Example Secret Keys for different cloud providers:

  • AWS: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

  • Google Cloud: my-secret-key-ABCDE12345FGHI67890

  • Scaleway: oGtZpLOoVbUCDQXdG9NTecAtEDvzbs6uQsTLKvi3Exg=

📶 Endpoint

The Endpoint is the URL used to connect to the S3 service. It specifies the target cloud storage provider and the associated S3 service within that provider.

Example Endpoints for different cloud providers:

  • AWS: s3.amazonaws.com

  • Google Cloud: storage.googleapis.com

  • Scaleway: s3.fr-par.scw.cloud

📍 Region

The Region represents the geographical location where the S3 bucket is located. Different regions may offer varying levels of availability, latency, and compliance options.

Example Regions for different cloud providers:

  • AWS: us-east-1 (US East - North Virginia)

  • Google Cloud: us-central1 (US Central - Iowa)

  • Scaleway: fr-par (Paris, France)

☁️ Bucket

The Bucket refers to a unique container within the cloud provider's storage system, where data objects are stored. It is essential to specify the correct bucket name to interact with the desired storage area.

Example Bucket names for different cloud providers:

  • AWS: my-aws-bucket

  • Google Cloud: my-google-bucket

  • Scaleway: my-scaleway-bucket

🪪 ACL (Access Control List)

The ACL defines the access permissions for objects stored within the S3 bucket. It determines who can read, write, or modify the objects.

Example ACL options for different cloud providers:

  • AWS: private, public-read, public-read-write

  • Google Cloud: projectPrivate, authenticatedRead, bucketOwnerFullControl

  • Scaleway: private, public-read, public-read-write

Where to send this information?

Simply send that list of six off, along with the specific fields you would like included in your exports, and how frequently you would like to receive the export, to your account manager or to [email protected] 😄.

For more information or assistance on S3, contact [email protected] !

Did this answer your question?