Who provides enterprise support for Amazon SQS?
AWS supports the SQS service under its AWS Support plans. AceMQ supports your use of it: producers, consumers, Lambda mappings, retry policy, IAM and KMS, around the clock.
What does 24/7 Amazon SQS support cover with AceMQ?
Round-the-clock incident response, a written root cause on every P1, and standing work that prevents repeats: alarms on ApproximateAgeOfOldestMessage and DLQ depth, plus visibility timeout and batching reviews.
Why is the same SQS message processed more than once?
Standard queues deliver at least once, so a duplicate is allowed. The usual causes are a handler that runs longer than the visibility timeout, a batch where one slow message pushes the others past it, and a worker that dies after doing the work but before DeleteMessage. We calibrate the timeout from measured duration, add ChangeMessageVisibility heartbeats where needed and make the consumer idempotent, because duplicates cannot be eliminated on a standard queue.
Why is our FIFO queue limited to a few hundred messages a second?
Each FIFO partition is limited to 300 transactions per second per API action in default mode, and up to 3,000 messages a second per action when you batch ten at a time. A single or low-cardinality MessageGroupId serialises everything. Spreading group IDs across real entities and enabling high-throughput mode lifts the ceiling by a large multiple, per the AWS quotas page.
How do SQS dead-letter queues and redrive work?
A redrive policy names a DLQ and a maxReceiveCount. When a message is received that many times without being deleted, SQS moves it to the DLQ. Nothing is lost, and nothing is processed either. The DLQ needs its own alarm and a retention longer than the source queue, because the original enqueue time carries over. Redrive in controlled batches after the cause is fixed.
What should we do when Lambda does not scale with the SQS backlog?
Check the event source mapping before the function: batch size, batching window, MaximumConcurrency and partial batch responses. A function that errors causes retries that look like load. Then check account and reserved concurrency. We read these settings alongside queue age so the cause is visible in one place.
Why are messages disappearing between SNS or EventBridge and our queue?
Usually an access policy. The queue policy must allow the publishing service principal, with the right source ARN condition, and an SSE-KMS queue needs a key policy that lets that service use the key. Delivery failures are logged on the SNS side, not in your consumer.
Does SQS support messages over 256 KB?
Yes. The AWS quotas page (read 17 November 2026) gives a maximum of 1 MiB per message. Beyond that, the Extended Client Library for Java and Python stores the payload in S3, up to 2 GB, and both producer and consumer must use it.
Should we be using SQS at all, or Kafka, RabbitMQ or Amazon MQ?
SQS is a good default for durable work queues with simple retry behaviour. It is not a log: there is no replay and no fan-out to independent consumer groups. If you need ordered replay or routing rules, Kafka or RabbitMQ fits better. AceMQ supports all of them, so advice is not steered by what we sell.
Can AceMQ help us secure SQS for regulated data?
Yes. We review queue and IAM policies, SSE-KMS key policies, VPC endpoints and cross-account access, and how payloads are handled. We do not certify compliance. We make sure the queue configuration matches the control you have to show.
Can we hire AceMQ for a one-off SQS review?
Yes. A review of visibility timeouts, redrive policies, alarms and queue and KMS key policies can be a single scoped job. Teams that find it useful often move to annual 24/7 support afterward, covering incidents and ongoing tuning with the same engineers.
How is Amazon SQS support priced?
Contracts run $24,000 to $72,000 a year (USD). We price by the number of queues and AWS accounts, the consumer platforms such as Lambda or ECS, how much FIFO and DLQ tuning is involved and the response plan. Tell us your setup and a quote follows within 1 hour.