> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/aws-sqs.md).

# AWS SQS

Connect to AWS SQS to manage your queues.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector           | Authentication  |
| ------------------- | --------------- |
| S3 Events (via SQS) | AWS credentials |
| AWS SQS             | AWS credentials |

#### S3 Events (via SQS)

Connect to AWS SQS queue for processing S3 event notifications. Automatically triggers workflows when files are uploaded, modified, or deleted in S3.

**Set up in AWS SQS**

1. In AWS, create (or identify) an SQS queue and configure your S3 bucket to send event notifications for object create/modify/delete events to that queue.
2. Create AWS credentials (access key ID and secret access key) for an IAM user or role with permission to read from the queue, and note the queue URL and region.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **S3 Events (via SQS)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required | What to enter                                                     |
| ----------------- | -------- | ----------------------------------------------------------------- |
| SQS Queue URL     | Yes      | The full URL of your SQS queue.                                   |
| AWS Region        | Yes      | The AWS region where your SQS queue is located (e.g., us-east-1). |
| Access Key ID     | Yes      | Your AWS access key ID.                                           |
| Secret Access Key | Yes      | Your AWS secret access key.                                       |

**Provider documentation:** [Setup reference](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-create-queue.html).

#### AWS SQS

Connect to AWS SQS queue for processing S3 event notifications. Automatically triggers workflows when files are uploaded, modified, or deleted.

**Set up in AWS SQS**

1. Create AWS credentials (access key ID and secret access key) for an IAM user or role with permission to receive messages from that queue.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **AWS SQS**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required | What to enter                                                     |
| ----------------- | -------- | ----------------------------------------------------------------- |
| SQS Queue URL     | Yes      | The full URL of your SQS queue.                                   |
| AWS Region        | Yes      | The AWS region where your SQS queue is located (e.g., us-east-1). |
| Access Key ID     | Yes      | Your AWS access key ID.                                           |
| Secret Access Key | Yes      | Your AWS secret access key.                                       |

**Provider documentation:** [Setup reference](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-create-queue.html).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **AWS SQS** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Get Messages

Get messages from an SQS queue

**Inputs**

| Field              | Type          | Required | Description                                                                                          |
| ------------------ | ------------- | -------- | ---------------------------------------------------------------------------------------------------- |
| Max Messages       | integer       | No       | Maximum number of messages to return (1-10). Default: 1. Default: 1.                                 |
| System Attributes  | string\_array | No       | List of system attributes to return with each message. Defaults to 'All'. Default: \["All"].         |
| Message Attributes | string\_array | No       | List of custom message attributes to return with each message. Defaults to 'All'. Default: \["All"]. |

**Outputs**

| Field         | Type        | Description                                   |
| ------------- | ----------- | --------------------------------------------- |
| Messages      | dict\_array | List of messages received from the SQS queue. |
| Message Count | integer     | Number of messages received.                  |

### Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

#### S3 SQS Events

Trigger workflows when files are uploaded, modified, or deleted in S3 buckets via SQS notifications.

Configure this trigger to monitor S3 buckets for file events through SQS. You can filter by bucket names, file prefixes/suffixes, event types, and object sizes. Requires an SQS queue configured to receive S3 event notifications.

**Configuration**

| Field                       | Type          | Required | Description                                                                                                                                                                                  |
| --------------------------- | ------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Allowed S3 Buckets          | string\_array | Yes      | List of S3 bucket names to monitor for events.                                                                                                                                               |
| S3 Event Types              | string\_array | Yes      | S3 event types to trigger on (e.g., s3:ObjectCreated:Put). Default: \["s3:ObjectCreated:Put", "s3:ObjectCreated:Post", "s3:ObjectCreated:Copy", "s3:ObjectCreated:CompleteMultipartUpload"]. |
| Object Key Prefixes         | string\_array | No       | Object key prefixes to filter on (e.g., uploads/, data/).                                                                                                                                    |
| Object Key Suffixes         | string\_array | No       | Object key suffixes to filter on (e.g., .pdf, .csv, .json).                                                                                                                                  |
| Minimum Object Size (bytes) | integer       | No       | Minimum object size in bytes to trigger on. Default: 0.                                                                                                                                      |
| Maximum Object Size (bytes) | integer       | No       | Maximum object size in bytes to trigger on (0 = no limit). Default: 0.                                                                                                                       |

**Event inputs**

| Field               | Type     | Required | Description                                                             |
| ------------------- | -------- | -------- | ----------------------------------------------------------------------- |
| S3 Bucket Name      | string   | Yes      | Name of the S3 bucket where the event occurred. Default: .              |
| S3 Object Key       | string   | Yes      | Full path/key of the S3 object that triggered the event. Default: .     |
| Object Size (bytes) | integer  | Yes      | Size of the S3 object in bytes. Default: 0.                             |
| Object ETag         | string   | Yes      | ETag of the S3 object for versioning/integrity. Default: .              |
| S3 Event Name       | string   | Yes      | Type of S3 event that occurred (e.g., s3:ObjectCreated:Put). Default: . |
| Event Timestamp     | date     | Yes      | When the S3 event occurred. Default: 2026-10-02 00:16:23.048125+00:00.  |
| AWS Region          | string   | Yes      | AWS region where the S3 event occurred. Default: .                      |
| Content Type        | string   | No       | MIME content type of the S3 object (if available).                      |
| Storage Class       | string   | No       | S3 storage class of the object (e.g., STANDARD, IA).                    |
| Object Version ID   | string   | No       | S3 object version ID (if versioning is enabled).                        |
| Request ID          | string   | Yes      | AWS request ID for the S3 operation. Default: .                         |
| Source IP           | string   | No       | IP address that triggered the S3 event (if available).                  |
| S3 Object URL       | string   | Yes      | Direct S3 URL to access the object. Default: .                          |
| Raw Event Data      | textarea | Yes      | Complete raw S3 event data as JSON. Default: {}.                        |

**Outputs**

| Field               | Type    | Description                                              |
| ------------------- | ------- | -------------------------------------------------------- |
| S3 Bucket Name      | string  | Name of the S3 bucket where the event occurred.          |
| S3 Object Key       | string  | Full path/key of the S3 object that triggered the event. |
| Object Size (bytes) | integer | Size of the S3 object in bytes.                          |
| S3 Event Name       | string  | Type of S3 event that occurred.                          |
| Event Timestamp     | date    | When the S3 event occurred.                              |
| S3 Object URL       | string  | Direct S3 URL to access the object.                      |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/aws-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.
