// the find
awslabs/backstage-plugins-for-aws
AWS plugins for Backstage
Official AWS Labs collection of Backstage plugins covering ECS, ECR, CodePipeline, CodeBuild, Security Hub, Cost Insights, and AWS Config-based catalog ingestion. If your team runs on AWS and already has Backstage, this is the first place to look before writing your own integrations. It follows the modern Backstage backend plugin architecture correctly.
AWS Labs backing means these stay current with Backstage's breaking backend system changes — that's the biggest maintenance headache with Backstage plugins, and the changelog shows they've kept pace. The frontend/backend/common package split for each service is exactly how Backstage wants plugins structured, so wiring them into an existing app is predictable. The AWS Config catalog provider is genuinely useful: it lets you auto-ingest existing AWS resources into the catalog without tagging everything manually first. Cost Insights implementation fills a real gap — the core Backstage cost plugin ships with no AWS backend, so teams either skip it or roll their own.
153 stars for an official AWS Labs project is a signal that adoption is thin, which usually means edge cases and less-common configurations are undertested in production. CodeCommit scaffolder actions are included, but AWS deprecated CodeCommit for new customers in 2024 — it's minor but shows some maintenance debt accumulating. The Generative AI plugin description ('Build assistants powered by Generative AI') reveals nothing about what it actually does or which Bedrock models it expects; the README for that plugin will need reading before you can evaluate whether it's useful. Notable gaps: no CloudWatch metrics/alarms on entity pages, no Lambda function visibility, no EKS. Teams that have split workloads across those services will need to fill in the blanks themselves.