​
1. Add your Amazon SQS access

  1. In the Destinations tab, click on the “Add destination” button located on the top right of your screen. Then, select the Amazon SQS option from the list of connectors.

  2. Click Next and you’ll be prompted to add your access:

  • Queue name: Specify the queue name you want to send data to.
  • AWS region name: The region name from the respective Amazon SQS account.
  • Convert payload keys: Set this property if you want to convert the payload keys to a specific format (snake_case, camelCase or PascalCase). If set to ‘None’, the keys will be sent as is.
  1. Click Next.

​
2. Select your catalog data to send

  1. The next step is letting us know which data you want to send to the spreadsheet. Select the layer and then the desired table.

Tip: The table can be found more easily by typing its name.

  1. Click Next.

​
3. Configure your Amazon SQS data destination

  1. Describe your destination for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.

  2. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need to have the data updated on the destination (every day, once a week, only at specific times, etc.).

  3. Click Done.

​
Check your new destination!

  1. Once completed, you’ll receive confirmation that your new destination is set up!

  2. You can view your new destination on the Destinations page. Now, for you to be able to see it on your Amazon SQS, you have to wait for the pipeline to run. You can monitor it on the Destinations page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your data should be seen on the Amazon SQS.

If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!

BigQueryBotConversa