aws_sqs
Sends messages to an SQS queue.
Introduced in version 3.36.0.
-
Common
-
Advanced
outputs:
label: ""
aws_sqs:
url: "" # No default (required)
message_group_id: "" # No default (optional)
message_deduplication_id: "" # No default (optional)
delay_seconds: "" # No default (optional)
max_in_flight: 64
metadata:
exclude_prefixes: []
batching:
count: 0
byte_size: 0
period: ""
check: ""
processors: [] # No default (optional)
outputs:
label: ""
aws_sqs:
url: "" # No default (required)
message_group_id: "" # No default (optional)
message_deduplication_id: "" # No default (optional)
delay_seconds: "" # No default (optional)
max_in_flight: 64
metadata:
exclude_prefixes: []
batching:
count: 0
byte_size: 0
period: ""
check: ""
processors: [] # No default (optional)
max_records_per_request: 10
region: "" # No default (optional)
endpoint: "" # No default (optional)
tcp:
connect_timeout: 0s
keep_alive:
idle: 15s
interval: 15s
count: 9
tcp_user_timeout: 0s
credentials:
profile: "" # No default (optional)
id: "" # No default (optional)
secret: "" # No default (optional)
token: "" # No default (optional)
from_ec2_role: "" # No default (optional)
role: "" # No default (optional)
role_external_id: "" # No default (optional)
max_retries: 0
backoff:
initial_interval: 1s
max_interval: 5s
max_elapsed_time: 30s
Metadata values are sent along with the payload as attributes with the data type String. If the number of metadata values in a message exceeds the message attribute limit (10) then the top ten keys ordered alphabetically will be selected.
The fields message_group_id, message_deduplication_id and delay_seconds can be set dynamically using function interpolations, which are resolved individually for each message of a batch.
Credentials
By default Redpanda Connect will use a shared credentials file when connecting to AWS services. It’s also possible to set them explicitly at the component level, allowing you to transfer data across accounts. You can find out more in Amazon Web Services.
Performance
This output benefits from sending multiple messages in flight in parallel for improved performance. You can tune the max number of in flight messages (or message batches) with the field max_in_flight.
This output benefits from sending messages as a batch for improved performance. Batches can be formed at both the input and output level. You can find out more in this doc.
Fields
backoff.initial_interval
The initial period to wait between retry attempts. The retry interval increases for each failed attempt, up to the backoff.max_interval value. This field accepts Go duration format strings such as 100ms, 1s, or 5s.
Type: string
Default: 1s
backoff.max_elapsed_time
The maximum period to wait before retry attempts are abandoned. If zero then no limit is used.
Type: string
Default: 30s
batching
Allows you to configure a batching policy.
Type: object
# Examples:
batching:
byte_size: 5000
count: 0
period: 1s
# ---
batching:
count: 10
period: 1s
# ---
batching:
check: this.contains("END BATCH")
count: 0
period: 1m
batching.byte_size
An amount of bytes at which the batch should be flushed. If 0 disables size based batching.
Type: int
Default: 0
batching.check
A Bloblang query that should return a boolean value indicating whether a message should end a batch.
Type: string
Default: ""
# Examples:
check: this.type == "end_of_transaction"
batching.count
A number of messages at which the batch should be flushed. If 0 disables count based batching.
Type: int
Default: 0
batching.period
A period in which an incomplete batch should be flushed regardless of its size.
Type: string
Default: ""
# Examples:
period: 1s
# ---
period: 1m
# ---
period: 500ms
batching.processors[]
A list of processors to apply to a batch as it is flushed. This allows you to aggregate and archive the batch however you see fit. Please note that all resulting messages are flushed as a single batch, therefore splitting the batch into smaller batches using these processors is a no-op.
Type: processor
# Examples:
processors:
- archive:
format: concatenate
# ---
processors:
- archive:
format: lines
# ---
processors:
- archive:
format: json_array
credentials
Optional manual configuration of AWS credentials to use. More information can be found in Amazon Web Services.
Type: object
credentials.from_ec2_role
Use the credentials of a host EC2 machine configured to assume an IAM role associated with the instance.
Requires version 4.2.0 or later.
Type: bool
credentials.secret
The secret for the credentials being used.
|
This field contains sensitive information that usually shouldn’t be added to a configuration directly. For more information, see Secrets. |
Type: string
credentials.token
The token for the credentials being used, required when using short term credentials.
Type: string
delay_seconds
An optional delay time in seconds for message. Value between 0 and 900 This field supports interpolation functions.
Type: string
max_in_flight
The maximum number of parallel message batches to have in flight at any given time.
Type: int
Default: 64
max_records_per_request
The maximum number of records delivered in a single SQS request. Enter only values from 0 to 10.
Type: int
Default: 10
max_retries
The maximum number of retries before giving up on the request. If set to zero there is no discrete limit.
Type: int
Default: 0
message_deduplication_id
An optional deduplication ID to set for messages. This field supports interpolation functions.
Type: string
message_group_id
An optional group ID to set for messages. This field supports interpolation functions.
Type: string
metadata.exclude_prefixes[]
Provide a list of explicit metadata key prefixes to be excluded when adding metadata to sent messages.
Type: array
Default: []
tcp
Configure TCP socket-level settings to optimize network performance and reliability. These low-level controls are useful for:
-
High-latency networks: Increase
connect_timeoutto allow more time for connection establishment -
Long-lived connections: Configure
keep_alivesettings to detect and recover from stale connections -
Unstable networks: Tune keep-alive probes to balance between quick failure detection and avoiding false positives
-
Linux systems with specific requirements: Use
tcp_user_timeout(Linux 2.6.37+) to control data acknowledgment timeouts
Most users should keep the default values. Only modify these settings if you’re experiencing connection stability issues or have specific network requirements.
Type: object
tcp.connect_timeout
Maximum amount of time a dial will wait for a connect to complete. Zero disables.
Type: string
Default: 0s
tcp.keep_alive.count
Maximum unanswered keep-alive probes before dropping the connection. Zero defaults to 9.
Type: int
Default: 9
tcp.keep_alive.idle
Duration the connection must be idle before sending the first keep-alive probe. Zero defaults to 15s. Negative values disable keep-alive probes.
Type: string
Default: 15s
tcp.keep_alive.interval
Duration between keep-alive probes. Zero defaults to 15s.
Type: string
Default: 15s