Cloud Monitoring uses Workspaces to organize monitoring information. This page describes Workspace concepts.

For information on how to create a Workspace, see Creating a Workspace.

What is a Workspace?

A Workspace is a tool for monitoring resources contained in one or more Google Cloud projects or AWS accounts. A Workspace accesses metric data from its monitored projects, but the metric data remains in those projects.

Host projects

Every Workspace has a host project. The host project is the Google Cloud project used to create the Workspace. The name of the Workspace is set to the name of host project. This isn't configurable.

The following diagram shows Workspace W monitoring its host project, W:

Illustration of a single-project workspace.

The host project for a Workspace stores all of the configuration content for dashboards, alerting policies, uptime checks, notification channels, and group definitions that you configure. If you delete the host project, you also delete the Workspace.

To create a Workspace for a Google Cloud project, you must have one of the roles listed in Workspace authorization.

For detailed steps on creating a Workspace, see Creating a Workspace.

Monitored projects

A Google Cloud project or AWS account can be monitored by exactly 1 Workspace. A Workspace always monitors its Google Cloud host project. However, you can configure a Workspace to monitor up to 375 Google Cloud projects and AWS accounts.

If you plan to use a Workspace to monitor more than the host project, then the best practice is to use a new, empty Google Cloud project to host the Workspace and then to add the projects and AWS accounts you want to monitor to your Workspace. This strategy lets you choose a useful name for your host project and Workspace, and it gives you a little more flexibility in moving monitored projects between Workspaces. The following diagram shows Workspace W monitoring Google Cloud projects A and B and AWS account D:

Illustration of a multi-project workspace.

For more information, see Adding monitored projects.

AWS Connector projects

In the preceding diagram, a Google Cloud project connects your monitored AWS account to the Workspace. The AWS connector project can be a Google Cloud project created specifically for this purpose or it can be an existing project. In either case, the AWS connect project must be in the same parent organization as the Workspace. The best practice is to create a Google Cloud project specifically to be the AWS connector project.

In the figure, the connector project has a name beginning with AWS Link. To find the name and details about your AWS connector projects, in the Monitoring menu of the Cloud Console, select Settings.

The billing account associated with the AWS connector project is used for Cloud Monitoring and Cloud Logging charges for the AWS account. For more information, see Billing.

Don't use AWS connector projects for any other purpose, and don't delete them if your Workspace is connected to your AWS account.

For more information, see Adding monitored projects.


There is no charge for creating a Workspace.

Charges for logging and metric data ingested by the monitored projects are associated with that projects' billing account. For AWS accounts, this means the billing accounts of the AWS connector projects:

  • For Google Cloud projects, if you have VM instances that contain software that sends monitoring data or logs to Cloud Monitoring APIs, then you are charged for that data. This software includes the Monitoring agents, Logging agents, and third party libraries like Prometheus that you might install. You continue to accrue charges while that software is running.

  • When you add an AWS account to a Workspace, monitoring and logging data is sent by Cloud Monitoring agents, Cloud Logging agents, or other software to the AWS connector project, whose billing account receives any charges.

For more information about pricing and free allotments, see Cloud Monitoring pricing.

To stop all Cloud Monitoring charges for metrics usage, do one of the following:

  • Disable the Monitoring APIs
  • Stop Cloud Monitoring agents, Cloud Logging agents, and other software modules from sending metrics or logs to your Google Cloud project, or to the AWS connector projects.

Removing a project from its Workspace doesn't affect Cloud Monitoring charges for logs and metrics usage.

What's next