Cloud Renames Contribute
RenamedData & BIGoogle Cloud

Cloud Composer Managed Service for Apache Airflow

Managed workflow orchestration service built on Apache Airflow.

Open in interactive timeline ↗All Google Cloud renamesHome

Naming timeline

  1. Cloud Composer

    Managed workflow orchestration service built on Apache Airflow launched in Beta on May 1, 2018 (GA in July 2018).

  2. Managed Service for Apache AirflowCurrent name

    · Google Cloud Next '26

    Rebranded from Cloud Composer to Managed Service for Apache Airflow (Managed Airflow) on April 15, 2026.

What is Cloud Composer called now?

Cloud Composer is now called Managed Service for Apache Airflow, with the latest change on 15 April 2026 (Google Cloud Next '26). Managed workflow orchestration service built on Apache Airflow. Only the customer-facing name changed; the underlying technical identifiers remain backward compatible.

Also known as

  • Managed Airflow (Gen 3)

Technical identifiers

Technical identifiers unchanged. Only the customer-facing product name changed; the APIs, CLI commands, IAM roles and Terraform resources below keep their legacy identifiers for backward compatibility.

REST / gRPC APIscomposer.googleapis.com
gcloud / CLI Commandsgcloud composer
IAM Predefined Rolesroles/composer.*
Terraform Resourcesgoogle_composer_*

APIs, client libraries, CLI commands, and IAM roles remain unchanged and reference Composer.

Notes & disambiguation

  • Announced on April 15, 2026 in Cloud Composer release notes (and April 28, 2026 across Data Analytics release notes): Cloud Composer evolved to become Managed Service for Apache Airflow.
  • All API endpoints (composer.googleapis.com), CLI commands (gcloud composer), client libraries, IAM roles (roles/composer.*), and Terraform resources (google_composer_*) remain unchanged and continue referencing Composer.

Sources & official documentation

Catalog last updated . Spotted an error? Suggest an edit