Service ownership at scale: new security and observability features
summary
Announces two usable features: scoped deployment secrets and router-level observability. Subgraph keys use a new Apollo key format (AK prefix, versioned ID, 256‑bit secret), created via Rover or the Platform API, scoped to specific subgraphs and variants, compatible with CI/CD (GitHub Actions example), default one‑year expiry, Rover 1.36+ and enterprise plan required. Subgraph Insights surfaces router fetch metrics (P50/P90/P95, heatmaps), error breakdowns, SDL and a contact directive, opt‑in via router flag, retention 1/7/90 days depending on plan.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:26Agenda and ownership
- 2:50Ownership drives impact
- 5:40Subgraph permissions and keys
- 7:24How subgraph keys work
- 16:20Subgraph insights for observability
- 19:36Demo: Subgraph insights
- 25:37Key takeaways
- 26:48Q&A
related talks
27mSupergraph AuthZ Security in Apollo Router with External Co-processing
42mGraphQL Summit Keynote
07mThe future of GraphQL routing
51mAPI Security: Securing GraphQL without going around in circles
15mNavigating GraphQL Vulnerabilities: SRE / DevSecOps
26mBeyond HTTP 200: Observability With GraphQL
21mGraphQL Authorization with Open Policy Agent
32mPanel - Things to Consider When Auditing Your GraphQL Infrastructure for Security