Skip to main content

Connect to Amazon SQS

Learn how to connect Amazon SQS to Retool.

You can use the SQS integration to create a resource and make it available in Retool. Once complete, your users can write queries that interact with SQS data.

You can use the Amazon SQS integration in apps and workflows to send, receive, and delete messages from a queue.

Requirements​

The SQS integration requirements depend on whether you have a cloud-hosted or self-hosted Retool organization. You may also need to make SQS configuration changes before creating the resource.

Sufficient user permissions to create resources

All users for Retool organizations on Free or Team plans have global Edit permissions and can add, edit, and remove resources. If your organization manages user permissions for resources, you must be a member of a group with Edit all permissions.

Allow Retool to access the data source

If the data source is behind a firewall or restricts access based on IP address, then you must ensure that your Retool organization can access it. If necessary, configure your data source to allow access from Retool's IP addresses.

CIDR IP addresses
3.77.79.248/30
35.90.103.132/30
44.208.168.68/30
Individual IP addresses
3.77.79.249
3.77.79.250
35.90.103.132
35.90.103.133
35.90.103.134
35.90.103.135
44.208.168.68
44.208.168.69
44.208.168.70
44.208.168.71

Retool is building support for querying firewalled resources without allowlisting Retool’s IP address. To learn more or be considered for early access, contact cloud-connect@retool.com.

SQS settings and authentication

You must have sufficient access and familiarity with your SQS data source so you can provide:

  • Required connection settings (e.g., URL and server variables).
  • Authentication credentials (e.g., API keys).

In some cases, you may need to make changes to your SQS configuration, such as generating authentication credentials or allowing access through a firewall. Refer to the configuration and authentication sections to learn more.

Set up SQS policy credentials

Set up an Amazon SQS queue for Retool to access. Generate an SQS policy for that resource with rights to the following actions:

"Effect":"Allow",
"Action":[
  "sqs:SendMessage",
  "sqs:ReceiveMessage",
  "sqs:DeleteMessage",
  "sqs:GetQueueAttributes",
  "sqs:ListTopics"
]

Configure the resource​

Sign in to your Retool organization and navigate to the Resources tab. Click Create new > Resource, then select SQS.

Configuration​

Specify the name, location, and description to use for your SQS resource. Retool displays the resource name and type in query editors to help users identify them.

Provide the following configuration settings to create the resource. Depending on how your data source is configured, you may also need to provide optional settings for Retool to connect.

Name

The name to use for the resource.

Description

A description of the resource.

Override default outbound Retool region

Retool connects to your data source from the us-west-2 region. Choosing a different outbound region can improve performance through geographic proximity.

RegionLocation
us-west-2US West (Oregon)
eu-central-1(Frankfurt, Germany)

Authentication​

The SQS integration supports the following authentication methods. Depending on which authentication method you use, you may need to make changes to your SQS configuration.

AWS Identity and Access Management

Authentication is performed using the provided AWS security credentials. You must be able to obtain and provide these credentials to create the resource.

Region

The AWS region with which to connect (e.g., us-east-1). This is often part of the base URL.

RegionLocation
us-east-1US East (N. Virginia)
us-east-2US East (Ohio)
us-west-1US West (N. California)
us-west-2US West (Oregon)
af-south-1Africa (Cape Town)
ap-east-1Asia Pacific (Hong Kong)
ap-northeast-1Asia Pacific (Tokyo)
ap-northeast-2Asia Pacific (Seoul)
ap-northeast-3Asia Pacific (Osaka)
ap-south-1Asia Pacific (Mumbai)
ap-south-2Asia Pacific (Bahrain)
ap-southeast-1Asia Pacific (Singapore)
ap-southeast-2Asia Pacific (Sydney)
ap-southeast-3Asia Pacific (Jakarta)
ap-southeast-4Asia Pacific (Hong Kong)
ca-central-1Canada (Central)
eu-central-1Europe (Frankfurt)
eu-central-2Europe (Warsaw)
eu-north-1Europe (Stockholm)
eu-south-1Europe (Milan)
eu-south-2Europe (London)
eu-west-1Europe (Ireland)
eu-west-2Europe (London)
eu-west-3Europe (Paris)
me-central-1Middle East (Bahrain)
me-south-1Middle East (Bahrain)
sa-east-1South America (São Paulo)
us-gov-east-1AWS GovCloud (US-East)
us-gov-west-1AWS GovCloud (US-West)
Access key ID

The access key ID with which to authenticate.

Secret key ID

The secret key ID with which to authenticate.

Role to assume (ARN)

A different role to use for accessing the API.

Queue Name Prefix

The prefix that Retool appends to queues.

Test the connection​

Click Test Connection to verify that Retool can successfully connect to the data source. If the test fails, check the resource settings and try again.

Testing a connection only checks whether Retool can successfully connect to the resource. It cannot check whether the provided credentials have sufficient privileges or can perform every supported action.

Save the resource​

Click Create resource to complete the setup. You can then click either Create app to immediately start building a Retool app or Back to resources to return to the list of resources.

Enable the Java DB Connector​

For Retool Self-hosted users, Retool provides a Java DBConnector, designed to enhance the performance and stability of certain integrations. This connector is required for the Amazon SQS, Databricks, and Kafka connectors.

The instructions for enabling the Java DB connector differ based on whether you are using Helm as a package manager:

  1. Upgrade to Retool Self-hosted version 3.52 or later.
  2. Run helm search repo retool/retool to check Retool's chart version. If you are on a version earlier than 6.0.9, then upgrade your deployment.
  3. Open values.yaml and add the following:
dbconnector:
  java:
    enabled: true

Next steps​

Your SQS resource is now ready to use. Check out related queries and code documentation to learn how to interact with SQS data.