> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/data-analytics-and-bi/amazon-sqs.md).

# Amazon SQS

How to connect using the SQS system integration

<div align="left"><figure><img src="https://391958821-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpokYqd27yrOUxIBhyvbF%2Fuploads%2FUkweSXxJA426rRKHHdFz%2Famazon-sqs-leader.avif?alt=media&amp;token=ce589037-210d-4720-aa26-0312540ff251" alt=""><figcaption></figcaption></figure></div>

## Overview

Amazon Simple Queue Service (SQS) is a managed message queue service from AWS that can be used to pass messages between applications and services.

Couchdrop can send data to Amazon SQS from file actions and Automations. This allows file-based workflows to publish messages to an SQS queue without requiring custom integration middleware.

For example, a file can arrive in Couchdrop through SFTP, FTP, cloud storage, an API, or an inbound Webhook, and an Automation can then send data from that workflow to an SQS queue.

## How Amazon SQS works with Couchdrop

Amazon SQS is configured in Couchdrop as a **System Integration**.

Unlike storage connections that appear as virtual folders, an SQS connection does not appear in the Couchdrop filesystem. Instead, the connection becomes available for use as a file action inside an Automation.

## How to connect Amazon SQS

{% hint style="warning" %}

#### Before you start

To connect Amazon SQS to Couchdrop, you will need:

* An existing Amazon SQS queue and its queue name
* An AWS IAM Key
* An AWS IAM Secret
* The AWS region containing the queue
* An IAM role with adequate access to Amazon SQS and the target queue
  {% endhint %}

{% stepper %}
{% step %}

### Create a System Integration

Log in to Couchdrop and add a new **System Integration**.
{% endstep %}

{% step %}

### Select Amazon SQS

Select **SQS** from the list of available integrations.
{% endstep %}

{% step %}

### Configure the connection

Provide the SQS queue name, AWS IAM Key, AWS IAM Secret, and AWS region.

Make sure the IAM role associated with the credentials has adequate access to Amazon SQS and the queue you want Couchdrop to use.
{% endstep %}

{% step %}

### Save the integration

Click **Add System Integration** to create the Amazon SQS connection.

The connection can now be selected from file actions inside Couchdrop Automations.
{% endstep %}
{% endstepper %}

## Using Amazon SQS in Automations

Once the System Integration has been created, Amazon SQS can be used as part of a Couchdrop Automation.

SQS does not provide a folder that you browse or transfer files into. Instead, an Automation uses the configured connection to publish data to the SQS queue as part of a workflow.

This lets you connect file-based activity in Couchdrop with applications and services that consume messages from Amazon SQS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.couchdrop.io/integrations/data-analytics-and-bi/amazon-sqs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.