Amazon sqs
Setting up the Amazon sqs connector
| No | Item | Required | Example | Notes |
|---|---|---|---|---|
| 1 | Queue URL | Yes | https://sqs.eu-west-1.amazonaws.com/1234567890/my-example-queue | URL of the SQS Queue |
| 2 | AWS Region | Yes | AWS Region of the SQS Queue | |
| 3 | Delete Messages After Read | Yes | If Enabled, messages will be deleted from the SQS Queue after being read. If Disabled, messages are left in the queue and can be read more than once. WARNING: Enabling this option can result in data loss in cases of failure, use with caution, see documentation for more detail. | |
| 4 | Max Batch Size | No | 5 | Max amount of messages to get in one batch (10 max) |
| 5 | Max Wait Time | No | 5 | Max amount of time in seconds to wait for messages in a single poll (20 max) |
| 6 | Message Attributes To Return | No | attr1,attr2 | Comma separated list of Mesage Attribute names to return |
| 7 | Message Visibility Timeout | No | 15 | Modify the Visibility Timeout of the individual message from the Queue's default (seconds). |
| 8 | AWS IAM Access Key ID | No | xxxxxHRNxxx3TBxxxxxx | The Access Key ID of the AWS IAM Role to use for pulling messages |
| 9 | AWS IAM Secret Key | No | hu+qE5exxxxT6o/ZrKsxxxxxxBhxxXLexxxxxVKz | The Secret Key of the AWS IAM Role to use for pulling messages |
Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.