# Connect Reverse ETL Source to Amazon Audience

This guide takes you through the steps to connect a Reverse ETL source to the Amazon Audience destination.

## Set up the connection 

{{< warning >}}
**The Reverse ETL feature supports only source-driven pipeline configuration.**

Make sure you have [set up a RETL source]({{< ref "sources/reverse-etl/_index.md" >}}) and connected it to your Amazon destination before following the below steps.
{{< /warning >}}

1. [Confirm the connection settings]({{< ref "destinations/reverse-etl-destinations/amazon-audience/setup-guide.md#connection-settings" >}}) for Amazon Audience and click **Continue**.
2. In the [Data Mapping]({{< ref "data-pipelines/reverse-etl/developer-guides/visual-data-mapper.md" >}}) section, select **Create New Audience** or **Use Existing Audience** in the **Where do you want to sync data to?** section.
3. RudderStack supports only [Mirror mode]({{< ref "data-pipelines/reverse-etl/developer-guides/sync-modes.md#mirror-mode" >}}) for this integration.
4. In **Choose identifier**, specify the warehouse column that RudderStack uses to identify your records.
5. Map your warehouse columns to specific Amazon fields using the **Map fields** setting and click **Continue**.

{{< image src="images/event-stream-destinations/amazon-identifier-map-fields.webp" >}}

## Next steps

- [Configure advanced settings for Amazon Audience destination]({{< ref "destinations/reverse-etl-destinations/amazon-audience/configuration-settings.md" >}})

## FAQ

#### Why can't I add a Reverse ETL source from the destination page?

The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.

See [Reverse ETL FAQ]({{< ref "data-pipelines/reverse-etl/developer-guides/faq.md" >}}) for more information.