Independent AWS Lambda support

AWS Lambda Support for Event-Driven Workloads on SQS, Kinesis and API Gateway

Last reviewed by Tyler Eastridge

AceMQ gives AWS teams 24/7 support for Lambda functions triggered by SQS, Kinesis, DynamoDB streams, EventBridge and API Gateway, including VPC-attached functions. Most calls start with one of three problems: throttling with 429 errors at modest traffic, messages processed more than once, or p99 latency spikes from cold starts.

24/7 AWS Lambda support with response targets from 15 minutes, by plan.

Support quotes answered within 1 hour, by a senior engineer.

Planning a build, upgrade or migration instead? See AceMQ AWS Lambda consulting and services.

160+
Customers supported
10+
Years in production support
40+
Sev 1 incidents handled a year
24/7
Americas, EMEA and APAC
1hour
Quote reply

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

Incident Triage

Problems we fix every week on AWS Lambda

Seven Lambda symptoms, each tied to the metric or log line we read first, such as ConcurrentExecutions, IteratorAge or Init Duration.

Common AWS Lambda production problems and how AceMQ resolves them
Symptom you're seeingWhat we check first
429 TooManyRequestsException at low traffic on one functionLambda concurrency is shared across the account Region. Check ConcurrentExecutions against the account limit and look for another function consuming it; reserved concurrency on a busy function starves its neighbours.
SQS messages processed repeatedly, DLQ filling with one payloadCheck that the visibility timeout is at least six times the function timeout, and use ReportBatchItemFailures so one bad record does not return the whole batch.
p99 spikes with a healthy p50Read Init Duration in the REPORT log line. Package size, SDK imports at module scope and VPC attachment drive it; provisioned concurrency removes it for a price, SnapStart for some Java runtimes.
VPC functions fail to start in a surgeCheck ENI and subnet IP exhaustion and NAT gateway limits. Spread across more subnets and review the security group path to dependencies.
Bill doubled with flat requestsCompare Duration times memory; a memory change alters cost and speed together. Add Lambda Power Tuning runs, and check retries from a failing downstream that multiply invocations.
Consistent timeouts at the configured limitThe function waits on a connection that never opens. Check the connection reuse outside the handler and the downstream timeout set below the function timeout.
Kinesis or DynamoDB stream shard falls behindWatch IteratorAge. A poison record blocks the shard until it expires; set BisectBatchOnFunctionError, maximum retry attempts and an on-failure destination.

Each production incident closes with an RCA naming the quota, mapping or timeout involved and the setting changed to stop a repeat.

Functions throttled or a queue redriving the same payload? Request a quote, reply within an hour.

Contact Us

Deployment coverage

Which Lambda setups does AceMQ support, and who covers what?

SetupWhat AceMQ coversWhat AWS coversExcluded
Lambda with SQS, SNS and EventBridgeEvent source mapping settings, batch handling, DLQs, idempotency designThe Lambda service and its events, per your AWS Support planService faults in AWS
Lambda with Kinesis and DynamoDB streamsIterator age, shard parallelism, failure handlingThe serviceSource table design beyond streams
API Gateway or function URL to LambdaTimeouts, payload limits, authorisers, error mappingThe serviceApplication code
VPC-attached LambdaSubnet sizing, ENIs, NAT, endpointsThe serviceYour network design outside the function path
Runtimes and packaging (Node.js, Python, Java, .NET, containers)Cold-start reduction, layers, container imagesRuntime behaviour as documentedLanguage-level defects in your code
Infrastructure as code (SAM, CDK, Terraform)Deploy failures, drift, aliases, rollbacksNot coveredThe tool's own defects

Support options

AWS Support vs independent support: an honest comparison

AWS Support plans cover AWS services and, per AWS's plans page, list third-party software support in Business Support+, Enterprise Support and Unified Operations (aws.amazon.com/premiumsupport/plans/, read 17 Nov 2026).

AWS Business Support+ / AWS Enterprise Support
Independent support from AceMQ
Business-critical system downAWS Business Support+: Under 30 minutesAWS Enterprise Support: Under 15 minutes
Business-critical system downFrom 15 minutes, by plan
Production system downAWS Business Support+: Under 1 hourAWS Enterprise Support: Under 1 hour
Production system downBy plan
General guidanceAWS Business Support+: Under 24 hoursAWS Enterprise Support: Under 24 hours
General guidanceBy plan
ScopeAWS Business Support+: AWS services and their behaviourAWS Enterprise Support: AWS services; escalation depth
ScopeYour event-driven design across Lambda, queues, streams and databases
Where AceMQ is not the right fitAWS Business Support+: If AWS must confirm a service fault, you need an AWS case; keep your plan and add AceMQ for design and operationsAWS Enterprise Support:
Where AceMQ is not the right fit

What's Included

Everything in your AWS Lambda support contract

Functions, event sources, VPC networking and the cost model around them, handled together because most incidents cross at least two of those.

  • 01

    Emergency Incident Response

    Functions throttled, an event source stalled, a redrive loop, or a cost anomaly running in real time. With response targets from 15 minutes, by plan, a senior engineer joins a live bridge with access to diagnose — not a ticket acknowledgement.

  • 02

    Cost Governance

    Memory right-sizing against measured duration, invocation pattern review, log retention and ingest cost, and detection of recursive or self-triggering invokes before they show up on a monthly bill.

  • 03

    Cold Start & Latency Tuning

    Init-phase profiling, package size and dependency reduction, lazy client construction, provisioned or SnapStart configuration where it pays for itself, and honest advice on where it does not.

  • 04

    Event Source & Integration Design

    SQS, Kinesis, DynamoDB Streams, EventBridge and API Gateway integrations tuned for batch size, visibility timeout, partial batch failure reporting, retry behaviour, and idempotency.

  • 05

    IAM, VPC & Security Review

    Least-privilege execution roles, VPC subnet and IP capacity planning, security group and endpoint configuration, and secret handling that does not put credentials in environment variables.

  • 06

    Observability & Root Cause Analysis

    Structured logging, X-Ray or OpenTelemetry tracing across async boundaries, and alarms on the metrics that matter — throttles, iterator age, and errors — so failures surface before customers report them.

Why AceMQ

Why serverless teams call us

  • We Treat Serverless Cost as an Engineering Problem

    Lambda bills climb from memory set once and never measured, log retention nobody chose, and invoke patterns that quietly multiply. We measure each, fix the cause, and document it so the saving survives the next feature.

  • Named Engineers, Zero Cold Start

    The same senior engineers stay on your account. They know your event sources, your concurrency posture, and your deployment tooling — so a P1 call starts with diagnosis, not twenty minutes of you explaining your architecture.

  • We Debug the Layers AWS Support Won't

    AWS operates the platform. Your handler code, your event source configuration, your IAM policy design, your concurrency allocation, and your cost profile are yours — and that is exactly where production incidents originate.

  • No Tier-1 Triage Layer

    You reach a senior engineer directly by phone, email, or Slack. No help desk collecting information to pass along, and no escalation approval standing between you and someone who can actually fix it.

  • Deep on the Queues Behind the Functions

    Most Lambda incidents are really event-source incidents. Messaging is our core discipline — SQS semantics, Kinesis shard behaviour, ordering, idempotency, and poison-message handling are home ground rather than adjacent knowledge.

  • Genuine Follow-the-Sun Coverage

    Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.

Lambda estates we cover

Every supported runtime and container-image function, across multi-account estates, regulated AWS accounts and whichever deployment tool you use.

  • AWS Lambda (all supported runtimes)
  • Node.js, Python, Java, .NET, Go runtimes
  • Container image Lambda functions
  • Lambda in VPC with private subnets
  • API Gateway & Lambda Function URLs
  • SQS, SNS & EventBridge event sources
  • Kinesis & DynamoDB Streams
  • AWS Step Functions orchestration
  • AWS SAM, CDK & Terraform deployments
  • Serverless Framework projects
  • Multi-account & multi-region estates
  • GovCloud & regulated AWS accounts

Version coverage

Versions we support

Versions we support
AreaWhat we support
RuntimesNode.js, Python, Java, .NET and custom runtimes, plus container-image functions, on the versions you run
Architecturesx86_64 and arm64 (Graviton)
ToolingSAM, CDK, Terraform and Serverless Framework deployments
Event sourcesSQS, SNS, EventBridge, Kinesis, DynamoDB Streams, MSK and Kafka sources

Escalation Path

Your first hour of an AWS Lambda outage

When throttling or a redrive loop starts, the responder opens CloudWatch and the event source mapping first, not a form asking for your architecture.

  1. From 15 min (by plan)first responseEmergencyProduction functions throttled or failing broadly, an event source stuck, customer-facing API returning errors
  2. 1 hourfirst responseCriticalSQS redrive loops, stream consumers hours behind, VPC functions failing during a surge
  3. 4 hoursfirst responseHighp99 cold-start spikes, bills doubling on flat traffic, timeouts at the configured limit
  4. Next Dayfirst responseStandardQuestions on memory sizing, provisioned concurrency, SnapStart and deployment tooling

Targets track your plan. A shard falling behind on a Kinesis stream and a question about reserved concurrency are not on one clock.

Want a named engineer for your serverless estate? Ask for a quote or write to us.

Contact Us

Pricing

What does AceMQ AWS Lambda support cost?

Support for AWS Lambda is quoted per scope, usually $24,000 to $72,000 a year. What moves it: how many functions and accounts carry production, which event sources feed them, and the response level.

Prices are in USD. Response targets begin at 15 minutes depending on plan, 24/7, and quotes are returned within 1 hour. Covering your queues, streams or containers in one contract earns a discount.

Support In Practice

Lambda incidents we have resolved

AWS Lambda support and optimization work from AceMQ. Each card links to the full write-up: the serverless estate, what AceMQ diagnosed or changed, and the result.

1 / 5 case studies

  • Remediation

    AWS Lambda SQS Redrive Loop Remediation

    Digital Insurance Provider

    Breaking a redrive loop where SQS messages were reprocessed indefinitely because the queue visibility timeout was shorter than the Lambda function timeout.

    AWS LambdaAmazon SQSDockerPostgreSQL
  • Assessment

    AWS Lambda Cost and Right-Sizing Assessment

    Consumer Subscription Business

    Measuring memory, duration, and concurrency across a large Lambda estate to right-size functions that were provisioned by guesswork.

    AWS LambdaAmazon SQSDockerPostgreSQL
  • Remediation

    Amazon SQS Dead-Letter Queues That Expired Their Own Evidence

    Benefits Enrolment Platform

    Failed enrolment events were disappearing from the dead-letter queue before anyone looked at them. The fix was a retention setting, a receive count, and a redrive path that did not create duplicates.

    Amazon SQSAWS LambdaAWSTerraform
  • Consulting

    AWS Lambda Event-Source Architecture Consulting

    Freight and Transport Technology Company

    Designing event-source mapping, batching, ordering, and failure handling for a Lambda estate that had grown without a consistent event architecture.

    AWS LambdaAmazon SQSKafkaRabbitMQDocker
All use cases

Support options

Four tiers of AWS Lambda support.

AceMQ offers AWS Lambda support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for functions your team runs, proactive monitoring that finds throttling, retry and cost problems first, managed Lambda operations inside your own AWS account, and fully managed Lambda run on your behalf from AceMQ-managed AWS accounts and infrastructure, with the pipelines, collectors and brokers around it. Runtimes and event sources are covered in all four.

  • Tier 1

    AWS Lambda 24/7 Support & Incident Management

    You own the functions, we take incidents

    Best for: Developers who run Lambda themselves and want an AWS-fluent engineer for throttling and retry failures.

  • Tier 2

    AWS Lambda 24/7 Support with Proactive Monitoring

    We review concurrency, mappings and spend

    Best for: Estates where cost, cold starts and silent retries are only noticed after a bill or an outage.

  • Tier 3

    Managed AWS Lambda on Your Infrastructure

    We operate Lambda inside your AWS accounts

    Best for: Organizations that must keep every function and log inside their own accounts and regions.

  • Tier 4

    Fully Managed AWS Lambda on AceMQ Infrastructure

    We run the event-driven platform for you

    Best for: Teams who want functions in production without owning quotas, alarms and on-call.

FAQ

AWS Lambda support questions

Still have questions about AWS Lambda? Email an Expert

Who provides enterprise support for AWS Lambda?

AWS supports the Lambda service under your AWS Support plan. Independent providers such as AceMQ add 24/7 support for how your functions, queues and streams behave together. AceMQ costs $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.

Why are our functions throttled when this one has low traffic?

Concurrency is shared across the Region. Another function, a burst or a reserved-concurrency setting is using the pool.

Why are our SQS messages processed more than once?

SQS delivers at least once. A visibility timeout shorter than the function timeout, or a batch failure that returns every record, causes repeats; make the handler idempotent.

Is provisioned concurrency the answer to cold starts?

It removes cold starts for the instances you pay for. Measure Init Duration first; a smaller package or lazy imports often costs nothing.

Can you help when Lambda is only part of a larger event-driven system?

Yes. We support the queues, streams and databases around the functions, including Kafka and RabbitMQ.

Why does my VPC function fail in a traffic surge?

Usually IP address exhaustion in the subnets or a NAT limit.

Why is my Kinesis consumer falling behind?

Check IteratorAge for a poison record, then batch window, parallelisation factor and failure settings.

Who offers AWS Lambda consulting and professional services?

AceMQ offers a serverless review: concurrency and cost, event source settings, cold-start plan and alarm design, as named deliverables.

How fast will you respond?

Top plans begin a response within 15 minutes, any hour. A sample Sev 1: a function gets 429 errors at low traffic because another function reserved the account concurrency. An engineer checks ConcurrentExecutions and reserved settings on a call, restores capacity, then writes the RCA. P2 1 hour, P3 4 hours, P4 next business day.

Do we need a yearly agreement for Lambda help?

No. Work such as a throttling investigation, a cost review or an event-source redesign can be bought as a single engagement. An annual agreement gives you round-the-clock response and the same engineers, which suits teams whose functions sit on revenue-critical paths.

What goes into a Lambda support quote?

Typical contracts are $24,000 to $72,000 a year (USD). We scope by the number of functions and AWS accounts in production, the event sources behind them (SQS, Kinesis, API Gateway, Step Functions), whether you want reviews or operations on top of escalation, and the response target. A quote follows within 1 hour.

Let's talk

Serverless Removes the Servers, Not the Failure Modes

Send us a REPORT log line and your event source settings and we will find the throttle or the duplicate in 1 hour.

A senior AWS Lambda engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an AWS Lambda Architect