Adding Anthos Service Mesh services to the service perimeters

If you have created a service perimeter in your organization, you must add the Anthos Service Mesh certificate authority (Mesh CA), Strackdriver logging, Cloud Monitoring and Cloud Trace services to the perimeter, in the following cases:

  • The cluster on which you have installed Anthos Service Mesh is in a project that is included in a service perimeter.
  • The cluster on which you have installed Anthos Service Mesh is a service project in a Shared VPC network.

By adding these services to the service perimeter, your Anthos Service Mesh cluster can access these services. Access to the services is also restricted within your cluster's Virtual Private Cloud (VPC) network.

Not adding the aforementioned services may cause the Anthos Service Mesh installation to fail or cause functions to be missing. For example, if you don't add Mesh CA to the service perimeter, the workloads can not get certificates from the Mesh CA.

Before you begin

The setup for the VPC Service Controls service perimeter is at the organization level. Ensure that you have been granted the proper roles for administering VPC Service Controls. If you have multiple projects, you can apply the service perimeter to all of the projects by adding each project to the service perimeter.

Adding Anthos Service Mesh services to an existing service perimeter


  1. Follow the steps in Updating a service perimeter to edit the perimeter.
  2. On the Edit VPC Service Perimeter page, under Services to protect, click Add Services.
  3. On the Specify services to restrict dialog, click Filter services, and enter Cloud Service Mesh Certificate Authority API.
  4. Select the service's checkbox.
  5. Click Add Cloud Service Mesh Certificate Authority API.
  6. Repeat steps 2 - 5, to add Stackdriver Logging API, Cloud Trace API, and Cloud Monitoring API.
  7. Click Save.


To update the list of restricted services, use the update command and specify the services to add as a comma-delimited list:

gcloud access-context-manager perimeters update PERIMETER_NAME \,,,[,OTHER_SERVICES \


  • PERIMETER_NAME is the name of the service perimeter that you want to update.

  • OTHER_SERVICES is an optional comma-separated list of one or more services to include in the perimeter in addition to For example:, or,,

  • POLICY_NAME is the numeric name of your organization's access policy. For example, 330193482019.

Refer to Updating a service perimeter for additional information.