# Service perimeter around managed services

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

Service perimeter around managed services is a Google Cloud guardrail written in vPC Service Controls. A service perimeter creates a security boundary that blocks, by default, communication from inside the perimeter to Google Cloud services across it, such as copying data to a Cloud Storage bucket outside the perimeter.

```text
gcloud access-context-manager perimeters create NAME \
--title=TITLE \
--resources=RESOURCES \
--restricted-services=RESTRICTED-SERVICES \
--ingress-policies=INGRESS-FILENAME.yaml \
--egress-policies=EGRESS-FILENAME.yaml \
[--access-levels=LEVELS] \
[--enable-vpc-accessible-services] \
[--vpc-allowed-services=ACCESSIBLE-SERVICES] \
--policy=POLICY_NAME

gcloud access-context-manager perimeters \
dry-run create ProdPerimeter --perimeter-title="Production Perimeter" \
--perimeter-type="regular" \
--perimeter-resources=projects/12345,projects/67890 \
--perimeter-restricted-services=storage.googleapis.com,bigquery.googleapis.com \
--perimeter-ingress-policies=ingress.yaml \
--perimeter-egress-policies=egress.yaml \
--policy=330193482019
```

- **Blocks:** A service perimeter creates a security boundary that blocks, by default, communication from inside the perimeter to Google Cloud services across it, such as copying data to a Cloud Storage bucket outside the perimeter.
- **Breaks:** Google documents that a VM in a VPC network inside the perimeter cannot reach Cloud Storage buckets outside it, and that ingress or egress rules are needed for any cross-perimeter access. ([source](https://cloud.google.com/vpc-service-controls/docs/overview))
- **Test before applying:** Google documents dry run mode for perimeters: requests that violate the perimeter policy are logged and not denied. ([source](https://cloud.google.com/vpc-service-controls/docs/dry-run-mode))
- **Mechanism:** [VPC Service Controls (service perimeters)](/mechanisms/vpc-service-controls/): Google Cloud managed services and the projects in the perimeter; Google says it does not block access to third-party APIs or services on the internet.
- **Taken from:** [provider documentation](https://cloud.google.com/vpc-service-controls/docs/create-service-perimeters), provider documentation

## What the source says

"Enforced perimeters actively prevent access to protected services." (read 10 Nov 2026).

On what it breaks: "VPC Service Controls doesn't allow a VM within a VPC network that is inside a service perimeter to access Cloud Storage buckets that are outside the perimeter."

## Related guardrails

- [Deny AWS RAM sharing with external accounts](/guardrails/aws-scp-deny-ram-external-sharing/): AWS, Service control policies (SCPs), data exfiltration
- [Block public sharing of EBS snapshots (declarative policy)](/guardrails/aws-declarative-snapshot-block-public-access/): AWS, Declarative policies, data exfiltration
- [Storage SAS tokens should adhere to 7 day maximum validity](/guardrails/azure-policy-storage-sas-7-days/): Azure, Azure Policy (built-in definitions), data exfiltration
- [Domain restricted sharing](/guardrails/gcp-orgpolicy-domain-restricted-sharing/): Google Cloud, Organization Policy Service (managed and legacy constraints), data exfiltration
- [Allowed destinations for exporting resources](/guardrails/gcp-orgpolicy-allowed-export-destinations/): Google Cloud, Organization Policy Service (managed and legacy constraints), data exfiltration
- [Custom constraint limiting IAM role grants to organization members](/guardrails/gcp-custom-allow-internal-and-special-identities/): Google Cloud, Custom organization policy constraints, data exfiltration

## Related pages

- [Allowed destinations for exporting resources (Google Cloud Organization Policy Service)](/guardrails/gcp-orgpolicy-allowed-export-destinations/)
- [Custom constraint limiting IAM role grants to organization members (Google Cloud Custom organization policy constraints)](/guardrails/gcp-custom-allow-internal-and-special-identities/)
- [Principal access boundary limiting the resources principals can access (Google Cloud Principal access boundary (PAB) policies)](/guardrails/gcp-pab-eligible-resources/)

## Sources

- Service perimeter around managed services: https://cloud.google.com/vpc-service-controls/docs/create-service-perimeters (read 10 Nov 2026)
- What it breaks: https://cloud.google.com/vpc-service-controls/docs/overview (read 10 Nov 2026)
- How to test it first: https://cloud.google.com/vpc-service-controls/docs/dry-run-mode (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/guardrails/gcp-vpcsc-service-perimeter/
