# Adobe Firefly: Simplified observability with Amazon Managed Prometheus

[AWS](https://yomu.fyi/company/aws) · Dev Arora · Aug 13, 2026

**Type:** Problem & solution

## Summary

Adobe Firefly powers generative creative features using a large-scale GPU training infrastructure hosted on Amazon Elastic Kubernetes Service. As workloads scaled to thousands of nodes and GPUs, Adobe's self-managed Prometheus setup struggled with query latency across high-cardinality telemetry data. To resolve these performance bottlenecks, the team moved two million critical time series metrics to Amazon Managed Service for Prometheus while using managed scrapers alongside their existing infrastructure. This setup accelerated query response times by more than 28x over 24-hour windows, reducing query execution times to approximately ten seconds. Additionally, the migration expanded practical monitoring windows from six hours to 24 hours, giving teams reliable visibility across long-running distributed training jobs.

## Context

Adobe operates GPU-based model training infrastructure on Amazon Elastic Kubernetes Service (Amazon EKS) to power Adobe Firefly. As training scaled across thousands of nodes and GPUs, generating high-cardinality telemetry across compute, memory, and network layers, their self-hosted Prometheus infrastructure could not meet query performance and availability requirements for large data volumes.

## Approach / What changed

Adobe iteratively migrated critical telemetry, encompassing 2 million time series metrics for job monitoring, pod/node health, and GPU health, to Amazon Managed Service for Prometheus. They deployed Amazon Managed Service for Prometheus collectors (managed scrapers) on Amazon EKS to forward metrics directly into managed workspaces alongside their existing self-managed Prometheus setup.

## Takeaways

- Query performance improved by up to 28.8x for 24-hour windows, reducing queries that previously timed out at 60 seconds to approximately 10 seconds.
- Observability query windows expanded from a practical limit of 6 hours to 24 hours, aiding lifecycle analysis for distributed jobs spanning 256 or more nodes.
- Adobe used managed scrapers to ingest metrics alongside their self-managed deployment, enabling an incremental migration of 2 million critical time series metrics without workflow disruption.

**Tags:** [AWS](https://yomu.fyi/topic/aws), [Kubernetes](https://yomu.fyi/topic/kubernetes), [Monitoring](https://yomu.fyi/topic/monitoring), [Observability](https://yomu.fyi/topic/observability), [Scalability](https://yomu.fyi/topic/scalability)

[Read original post](https://aws.amazon.com/blogs/architecture/adobe-firefly-simplified-observability-with-amazon-managed-prometheus)