A 15 de setembro de 2026, todos os ambientes do Cloud Composer 1 e do Cloud Composer 2 versão 2.0.x vão atingir o fim da vida útil planeado e não vai poder usá-los. Recomendamos que planeie a migração para o Cloud Composer 3.
A execução de uma aplicação essencial para a empresa no Cloud Composer requer que várias partes tenham responsabilidades diferentes. Embora não seja uma lista exaustiva, este documento indica as responsabilidades da Google e do Cliente.
Responsabilidades da Google
Reforçar e
aplicar patches aos componentes e à infraestrutura subjacente do ambiente do Cloud Composer, incluindo o cluster do Google Kubernetes Engine, a base de dados do Cloud SQL (que aloja a base de dados do Airflow), o Pub/Sub, o Artifact Registry e outros elementos do ambiente. Em particular, isto inclui a atualização automática da infraestrutura subjacente, incluindo o cluster do GKE e a instância do Cloud SQL de um ambiente.
Fornecer Google Cloud integrações para a gestão de identidade e de acesso, os registos de auditoria do Google Cloud
e o Cloud Key Management Service.
Restringir e registar o acesso administrativo da Google aos clusters dos clientes para fins de apoio técnico contratual com a Transparência de acesso e a aprovação de acesso.
Publicação de informações sobre alterações incompatíveis com versões anteriores entre as versões do Cloud Composer e do Airflow nas notas de lançamento do Cloud Composer.
Manter a documentação do Cloud Composer atualizada:
Facultar uma descrição de todas as funcionalidades fornecidas pelo
Cloud Composer.
Fornecer instruções de resolução de problemas que ajudam a manter os ambientes num estado saudável.
Publicar informações sobre problemas conhecidos com soluções alternativas (se existirem).
Resolver incidentes de segurança críticos relacionados com ambientes do Cloud Composer e imagens do Airflow fornecidas pelo Cloud Composer (excluindo pacotes Python instalados pelo cliente) através da disponibilização de novas versões do ambiente que resolvem os incidentes.
Consoante o plano de apoio técnico do cliente, resolução de problemas de
problemas de estado do ambiente do Cloud Composer.
Resolução de problemas e, se possível, correção de problemas nas funcionalidades principais do Airflow.
Responsabilidades do cliente
Atualizar para novas versões do Cloud Composer e do Airflow para manter
o apoio técnico do produto e resolver problemas de segurança assim que
o serviço Cloud Composer publicar uma versão do Cloud Composer
que resolva os problemas.
Manter o código dos DAGs para o manter compatível com a versão do Airflow usada.
Manter as autorizações adequadas no IAM para a conta de serviço do ambiente. Em particular, manter as autorizações necessárias pelo
agente do Cloud Composer e pela
conta de serviço do ambiente. Manter a autorização necessária para a chave CMEK usada para a encriptação do ambiente do Cloud Composer e rodá-la de acordo com as suas necessidades.
Manter as autorizações adequadas no IAM para o contentor do ambiente.
Manter as autorizações de IAM adequadas para uma conta de serviço que realiza instalações de pacotes do PyPI. Para mais informações, consulte o artigo
Controlo de acesso.
Manter as autorizações adequadas do utilizador final na configuração de controlo de acesso da IU do IAM e do Airflow.
Manter o tamanho da base de dados do Airflow abaixo de 20 GB através da utilização do DAG de manutenção.
Resolver todos os problemas de análise de DAGs antes de apresentar registos de apoio técnico ao
apoio técnico ao cliente da Google Cloud.
Atribuir nomes aos DAGs de forma adequada (por exemplo, sem usar carateres invisíveis, como ESPAÇO ou TAB nos nomes dos DAGs) para que as métricas possam ser comunicadas corretamente para os DAGs.
Atualize o código dos DAGs para que não use operadores descontinuados e migre para as respetivas alternativas atualizadas. Os operadores descontinuados podem ser removidos dos fornecedores do Airflow, o que pode afetar os seus planos de atualização para uma versão posterior do Cloud Composer ou do Airflow. Os operadores descontinuados também não são mantidos e têm de ser usados "tal como estão".
Configurar as autorizações da IAM adequadas quando usar back-ends secretos, como o Secret Manager, para que a conta de serviço do ambiente tenha acesso ao mesmo.
Ajustar os parâmetros do ambiente do Cloud Composer (como a CPU e a memória dos componentes do Airflow) e as configurações do Airflow para cumprir as expetativas de desempenho e de carga dos ambientes do Cloud Composer através do guia de otimização do Cloud Composer e do guia de escalabilidade do ambiente.
Evitar a remoção de autorizações exigidas pelo agente do Cloud Composer e pelas contas de serviço do ambiente (a remoção destas autorizações pode levar a falhas nas operações de gestão ou a falhas de DAG e tarefas).
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-29 UTC."],[[["\u003cp\u003eThis document outlines the shared responsibilities between Google and customers when using Cloud Composer 3 for business-critical applications.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's responsibilities include hardening and patching the Cloud Composer environment, protecting access, and providing security features like encryption and access control.\u003c/p\u003e\n"],["\u003cp\u003eCustomers are responsible for upgrading to new Cloud Composer and Airflow versions, maintaining DAG code and IAM permissions, and ensuring Airflow database health.\u003c/p\u003e\n"],["\u003cp\u003eCustomers must manage IAM permissions for service accounts and buckets, as well as for PyPI package installations, and end user access.\u003c/p\u003e\n"],["\u003cp\u003eBoth parties have a vested interest in maintaining the performance and security of Cloud Composer, with Google managing the underlying infrastructure, and the customer managing their own DAGs, code and environment settings.\u003c/p\u003e\n"]]],[],null,["# Cloud Composer shared responsibility model\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\n**Cloud Composer 3** \\| [Cloud Composer 2](/composer/docs/composer-2/shared-responsibility \"View this page for Cloud Composer 2\") \\| [Cloud Composer 1](/composer/docs/composer-1/shared-responsibility \"View this page for Cloud Composer 1\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nRunning a business-critical application on Cloud Composer requires\nmultiple parties to carry different responsibilities. While not an exhaustive\nlist, this document lists the responsibilities for both Google and the Customer\nsides.\n\nGoogle Responsibilities\n-----------------------\n\n- [Hardening](/container-optimized-os/docs/concepts/security) and\n [patching](/kubernetes-engine/docs/resources/security-patching) the Cloud Composer\n environment's components and underlying infrastructure, including\n Google Kubernetes Engine cluster, Cloud SQL database (that hosts the Airflow\n database), Pub/Sub, Artifact Registry and other environment\n elements. In particular, this includes auto-upgrading the underlying\n infrastructure, including the GKE cluster and\n Cloud SQL instance of an environment.\n\n | **Note:** Cloud Composer 1 is in the post-maintenance mode and new versions of Cloud Composer 1 with security fixes are no longer published. Migrate to Cloud Composer 2 to get the latest version updates with security improvements.\n- Protecting access to Cloud Composer environments through\n incorporating access control provided by IAM,\n [encrypting data at rest by default](/security/encryption-at-rest/default-encryption),\n providing [additional customer-managed storage encryption](/kubernetes-engine/docs/how-to/using-cmek),\n [encrypting data in transit](/security/encryption-in-transit).\n\n- Providing Google Cloud integrations for Identity and Access Management, Cloud Audit Logs\n and Cloud Key Management Service.\n\n- Restricting and logging Google administrative access to customers' clusters\n for contractual support purposes with\n [Access Transparency](/access-transparency) and\n [Access Approval](/cloud-provider-access-management/access-approval/docs/overview).\n\n- Publishing information about backward incompatible changes between\n Cloud Composer and Airflow versions in\n [Cloud Composer Release Notes](/composer/docs/release-notes).\n\n- Keeping Cloud Composer documentation up to date:\n\n - Providing description of all functionalities provided by\n Cloud Composer.\n\n - Providing troubleshooting instructions that help to keep environments in\n a healthy state.\n\n - Publishing information about known issues with workarounds (if they\n exist).\n\n- Resolving critical security incidents related to Cloud Composer\n environments and Airflow images provided by Cloud Composer\n (excluding customer-installed Python packages) by delivering new\n environment versions addressing the incidents.\n\n- Depending on customer's Support Plan, troubleshooting of\n Cloud Composer environment health issues.\n\n- Maintaining and expanding the functionality of the\n [Cloud Composer Terraform provider](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/composer_environment).\n\n- Cooperating with the Apache Airflow community to maintain and develop\n [Google Airflow operators](https://airflow.apache.org/docs/apache-airflow-providers-google/stable/operators/cloud/cloud_composer.html).\n\n | **Note:** Google won't fix or troubleshoot issues in operator providers for third-party services or products.\n- Troubleshooting and, if possible, fixing issues in Airflow core\n functionalities.\n\nCustomer responsibilities\n-------------------------\n\n- Upgrading to new Cloud Composer and Airflow versions to keep\n support for the product and to resolve security issues once\n Cloud Composer service publishes a Cloud Composer\n version that addresses the issues.\n\n- Maintaining the DAGs code to keep it compatible with the used Airflow version.\n\n- Maintaining proper permissions in IAM for the environment's\n service account. Particularly, keeping permissions required by the\n [Cloud Composer Agent](/composer/docs/composer-3/access-control#composer-sa) and the\n [environment's service account](/composer/docs/composer-3/access-control#service-account). Maintaining\n required permission for the CMEK key used for Cloud Composer\n environment encryption and rotating it according to your needs.\n\n | **Caution:** We recommend to [set up a user-managed service account](/composer/docs/composer-3/access-control#custom-service-account) for Cloud Composer environments that has only the required set of permissions that are necessary to run the environment and perform operations defined in your DAGs. The **Composer Worker** (`composer.worker`) role provides this required set of permissions in most cases. Add extra permissions to this service account only when it's necessary for the operation of your DAGs. \n |\n | Although we recommend against using this approach, if you don't specify an environment's service account, then your Cloud Composer environment uses the default Compute Engine service account. The default Compute Engine service account usually has the **Editor** basic role, which contains many more permissions than necessary to run Cloud Composer environments and thus creates a risk of DAGs using broader permissions than intended.\n- Maintaining proper permissions in IAM for the environment's\n bucket\n\n .\n\n | **Caution:** Users with read-write access to the following components:\n | - Your environment's bucket\n | - Artifact Registry repositories with container images used by: `GKEPodOperator`, or `GKEStartPodOperator`\n |\n | can deploy their own versions of DAGs or container images to an environment\n | even without explicit Cloud Composer-related permissions.\n | These DAGs or images can be later executed in your environment\n | with the permissions of the Cloud Composer environment\n | service account.\n- Maintaining proper IAM permissions for a service account\n that performs PyPI packages installations. For more information, see\n [Access control](/composer/docs/composer-3/access-control#service-account-security).\n\n | **Caution:** Users with read-write access to the environment's bucket or those who can initiate PyPI packages installations can initate the process of building images on behalf of a service account which is used to perform such builds. This service account is called the environment's service account that is specified during the environment creation, It can be a user-provided service account, or the default service account.\n- Maintaining proper end user permissions in IAM and Airflow\n UI Access Control configuration.\n\n- Keeping Airflow database size below\n 20 GB through\n using the [maintenance DAG](/composer/docs/composer-3/cleanup-airflow-database).\n\n- Resolving all DAG parsing issues before raising support cases to\n Cloud Customer Care.\n\n- Naming DAGs in a proper way (for example, without using invisible characters\n like SPACE or TAB in DAG names) so that metrics can be reported correctly\n for DAGs.\n\n- Upgrade the code of DAGs so that it doesn't use deprecated operators and\n migrate to their up to date alternatives. Deprecated operators might be\n removed from Airflow providers, which might impact your plans to upgrade\n to a later Cloud Composer or Airflow version. The deprecated\n operators are also not maintained and they must be used 'as is'.\n\n- Configuring proper IAM permissions when using secret\n backends like Secret Manager so that the environment's\n service account has access to it.\n\n- Adjusting Cloud Composer environment parameters (such as CPU and\n memory for Airflow components) and Airflow configurations to meet\n performance and load expectations of Cloud Composer environments\n using\n [Cloud Composer optimization guide](/composer/docs/composer-3/optimize-environments)\n and [environment scaling guide](/composer/docs/composer-3/scale-environments).\n\n- Avoiding removing permissions required by Cloud Composer Agent and\n environment's service accounts (removing these permissions can lead either\n to failed management operations or to DAG and task failures).\n\n- Keeping\n [all services and APIs required by Cloud Composer](/composer/docs/composer-3/enable-composer-service#required-services)\n always enabled. These dependencies must have quotas configured at levels\n required for Cloud Composer.\n\n- [Following recommendations and best practices](/composer/docs/composer-3/write-dags) for\n implementing DAGs.\n\n- Diagnosing DAG and task failures using instructions for\n [scheduler troubleshooting](/composer/docs/composer-3/troubleshooting-scheduling),\n [DAG troubleshooting](/composer/docs/composer-3/troubleshooting-dags) and\n [triggerer troubleshooting](/composer/docs/composer-3/troubleshooting-triggerer).\n\nWhat's next\n-----------\n\n- [Access control with IAM](/composer/docs/composer-3/access-control)\n- [Clean up the Airflow database](/composer/docs/composer-3/cleanup-airflow-database)\n- [Security overview](/composer/docs/composer-3/composer-security-overview)"]]
