Honeycomb Achieves the AWS Financial Services Competency
Honeycomb is proud to share that we have achieved the Amazon Web Services (AWS) Financial Services Competency.
By: Matthew Scott

You Don't Need Three Pillars, You Need Single Threads
One of the customers I’m currently working with is a large financial institution that has a robust three pillar implementation. Every critical application ships their telemetry to either or both their cloud-native tool and a central tool. This worked fine when they had relatively monolithic applications, but with their architecture moving towards a service-based one, it’s getting harder to manage.
Read More
Honeycomb is proud to share that we have achieved the Amazon Web Services (AWS) Financial Services Competency. This recognition validates our technical expertise and proven customer success in assisting financial services organizations with building, running, and understanding their production systems on AWS.
Securing this competency is a direct response to our customers’ feedback in this space: observability in regulated, high-stakes environments requires more than dashboards and alerts. Financial services and insurance organizations need to be able to ask questions they didn't know they’d need to ask, and get answers fast.
We built the case for this competency on real production work.
Helping a digital banking platform managing hundreds of millions of users. Supporting a consumer lender where a 4-hour incident window creates real regulatory exposure. Ensuring visibility for a payments infrastructure where a missed trace is a potential fraud event. The problems are different from a typical SaaS company, and they require a different level of observability.
That’s where Honeycomb thrives.
Register for O11yCon
Honeycomb’s in-person observability conference
where you can hear real stories from teams building
observability for agents in production
What the competency means in practice
Modern financial platforms running microservices, cloud-native infrastructure, and AI-assisted workflows operate under conditions most organizations don't face: strict compliance requirements, high-cardinality transaction data, and the pressure of knowing that when something goes wrong at 2 a.m., it might affect a payment, a loan disbursement, or a customer's ability to access their money. This kind of complexity requires high-cardinality, high-dimensionality telemetry and the ability to explore that data without knowing in advance what you're looking for.
Here's what that looks like in production.
- Nubank: At the scale of 110 million users and 4,500+ microservices, tracing a single financial transaction end-to-end was a reliability and regulatory requirement. With Honeycomb deployed on AWS using OpenTelemetry-based distributed tracing, the team gained real-time visibility across all transaction flows, enabling faster issue detection and the confidence to scale without losing sight of their payment and credit systems.
- Salary Finance: For a consumer lender, a four to eight hour mean time to resolution creates real risk of delays in loan disbursement and potential regulatory exposure. After implementing Honeycomb for full-system tracing across AWS services, the team cut MTTR to under two hours, enabled proactive issue detection, and gained compliance-grade audit visibility across their lending operations.
- Moov: For payments infrastructure, complex transaction flows across financial rails mean that a missing trace (also known as a "trace gap") could represent a potential exposure to fraud or compliance issues. Using Honeycomb's high-cardinality observability to trace each transaction in real time, the team improved payment reliability, accelerated debugging, and built full transaction traceability across the payment lifecycle.
Why this matters for your team
Getting to production fast matters. But in financial services, staying in production reliably, while meeting audit requirements, controlling costs, and understanding your systems matters more.
Honeycomb's integration with foundational AWS services like Amazon GuardDuty, AWS CloudTrail, and AWS Security Hub means teams can get observability running quickly, with consistent context across their cloud environments. Less time standing up tooling. More time understanding what's actually happening.
What's next
If you're building or operating production systems in financial services on AWS and want to understand what your systems are actually doing—not just whether they're up—talk to us.
And if you're coming to O11yCon in San Francisco on May 20-21, this is exactly the kind of real-world production challenge we'll be digging into across our practitioner and leadership tracks.