CloudPath knowledge base
A report-backed catalog of AWS services shaped for quick browsing. The page preserves category, stage, lifecycle status, region and partition limitations, retirement notes, and notable caveats from the research report instead of flattening them into a generic spreadsheet.
111
68
40
4
Stage
Generally available according to the research report's normalized lifecycle model.
Public preview or other pre-GA availability called out in the report.
No longer offered as an active AWS service or capability in the report snapshot.
Status
Available for normal use in the report snapshot.
Available, but only in the explicitly listed regions or partitions.
Still available, but AWS guidance in the report points learners toward alternatives.
AWS has published an end date or support cutoff in the report sources.
Already shut down or unavailable to customers in the report snapshot.
Category
Managed batch processing that schedules and runs batch jobs across compute resources at scale.
PaaS-like deployment service for web applications that handles provisioning and scaling underlying resources.
Serverless compute engine for containers that lets you run containers without managing servers/clusters directly.
Serverless compute service to run code in response to events without managing servers, billed by execution.
Resizable virtual compute capacity (instances) for running applications with granular control over compute, storage, and networking.
Managed container orchestration service for running and scaling containerized apps on AWS.
Managed Kubernetes service running control-plane across multiple AZs for resilient Kubernetes clusters.
Simplified VPS-style service with predictable pricing for basic compute/storage/networking and easy app hosting.
Every catalog entry is populated from the uploaded AWS services research report. The page does not invent alternative maturity labels or hide lifecycle exceptions.
When the report flags source conflicts, retirement windows, region limits, or replacement guidance, that note is surfaced directly on the service card so learners can make safer architecture choices.