# S3 / Azure / GCS ### Overview This article describes how to configure your S3-compatible storage (AWS S3, GCS, Azure Blob) to allow Birdie to export data to a dedicated bucket. Birdie can export processed data (e.g., enriched feedback, areas, opportunities) to your S3-compatible storage. We recommend creating: * A dedicated **bucket or prefix** for Birdie exports * Credentials with **write access** to the export location This isolates write access from your existing data. ### Step 1: Create a dedicated bucket or prefix for exports Create a dedicated bucket or prefix where Birdie will write export files: ``` s3://your-bucket/birdie-exports/ ``` ### Step 2: Configure write permissions Birdie uses the same authentication mechanisms for export as for data ingestion. The credentials must have **write access** to the export bucket/prefix. For detailed instructions on generating credentials for each provider, refer to the corresponding section in the [Data Ingestion with S3 documentation](https://ask.birdie.ai/~/revisions/5vNgx1SBLaM9wSz456q7/integrations-and-data-ingestion/how-to-integrate-with/s3-azure-gcs): * AWS: [User with Access Key or Role with External ID](/integrations-and-data-ingestion/how-to-integrate-with/s3-azure-gcs.md#aws) * GCS: [HMAC Keys](/integrations-and-data-ingestion/how-to-integrate-with/s3-azure-gcs.md#gcp) * Azure Blob Storage: [SAS Token (recommended) or Shared Key](/integrations-and-data-ingestion/how-to-integrate-with/s3-azure-gcs.md#azure) Once you have generated the credentials, you will have to grant write access to your bucket for the user / role: * AWS: Grant [read and write access](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_s3_rw-bucket.html) for the specific Bucket and Objects. * GCS: Grant the [Storage Object User](https://docs.cloud.google.com/storage/docs/access-control/iam-roles#storage.objectUser) and [Storage Bucket Viewer](https://docs.cloud.google.com/storage/docs/access-control/iam-roles#storage.bucketViewer) roles for the specific bucket. * Azure Blob Storage: Grant the [Storage Blob Data Contributor](https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/storage#storage-blob-data-contributor) role. ### Step 3: Share export configuration with Birdie Share the following details securely with Birdie: * Export bucket name * Region * Credentials with write access (Access Key ID / Secret Key) * Other optional parameters (External ID, Role ARN, S3 endpoint url, etc.) Birdie will configure the export connector and confirm once the integration is active. If you don't know how to generate/obtain any of these items, please refer to the [S3 data ingestion setup](https://ask.birdie.ai/~/revisions/61LOEXSieVY1svUYtjzo/integrations-and-data-ingestion/how-to-integrate-with/s3-azure-gcs). ### How the Export Works Birdie delivers daily exports via folders in your bucket: ``` s3://your-bucket/export/2025-01-01/feedbacks.csv s3://your-bucket/export/2025-01-02/feedbacks.csv ... ``` Each folder contains the standard set of export files: * `feedbacks.csv` * `areas.csv` * `opportunities.csv` * etc. The complete set of files is documented in the [data forwarding documentation](https://ask.birdie.ai/~/revisions/imP4CTJ80lIhIX6zY2BL/integrations-and-data-ingestion/how-to-export-with...). Birdie's exported content will be incremental for some of the files. This means you can't rely solely on the latest file to have the full picture of the data you have inside Birdie. We recommend you use a Data Warehouse or SQL Engine of choice to consolidate and deduplicate these entries so you can use them analytically. You'll be responsible for keeping an up-to-date, deduplicated copy of each of these tables. ### Exported Data Format The exported data content will match the schemas described in our [data forwarding documentation](https://ask.birdie.ai/~/revisions/imP4CTJ80lIhIX6zY2BL/integrations-and-data-ingestion/how-to-export-with...). You can also check this documentation to better understand how to query the consolidated copies of the exported data. If the schema evolves over time, you'll need to update your table definitions to make sure to include the new columns within your table. You also need to create a Warehouse / Database system and ETL Pipeline where you consolidate and deduplicate the data. More details on how to do this are given in the [data forwarding documentation](https://ask.birdie.ai/~/revisions/imP4CTJ80lIhIX6zY2BL/integrations-and-data-ingestion/how-to-export-with...). ### References * [AWS S3 Documentation](https://docs.aws.amazon.com/s3/) * [GCS Interoperability](https://cloud.google.com/storage/docs/interoperability) * [Azure Blob Storage](https://learn.microsoft.com/en-us/azure/storage/blobs/) * [Data Ingestion with S3](https://ask.birdie.ai/~/revisions/5vNgx1SBLaM9wSz456q7/integrations-and-data-ingestion/how-to-integrate-with/s3-azure-gcs) * [How to export with (Data Forwarding)...](https://ask.birdie.ai/~/revisions/imP4CTJ80lIhIX6zY2BL/integrations-and-data-ingestion/how-to-export-with...) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ask.birdie.ai/integrations-and-data-ingestion/how-to-export-with.../s3-azure-gcs.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.