Repository navigation
[PREVIEW COPY] docs(gcp): document VPC Service Controls requirements for GCP integrations - #25887
Merged
3 commits merged intoSep 29, 2026
Merged
3 commits merged into
3 commits merged into
Conversation
…tions Customers with a VPC SC perimeter around their GCP project were hitting PERMISSION_DENIED errors with no documented way to resolve them, since neither the WIF nor service account setup guides mentioned VPC SC ingress rules. Documents the required APIs for each connection method (WIF needs sts.googleapis.com and iamcredentials.googleapis.com in addition to the four APIs shared with the service account flow).
The V2 docs split moved this guidance to integrations-custom-roles.mdx and the service account page links to it, but the WIF page never got the same cross-reference — flagged in the VPC SC support thread. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Domain restriction constraints (iam.allowedPolicyMemberDomains / iam.managed.allowedPolicyMembers) only affect the service account connection method, since it adds New Relic's own service account as an external IAM member. WIF pools/providers are the customer's own org resources and are already part of their organization principal set, so the constraint doesn't apply — remove the misleading cross-reference from the WIF page instead of describing a no-op. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
|
netlify build |
1 of 2 tasks
Contributor
Author
🚀 Netlify Preview Building!If the build is successful, the preview for this pull request will be available at the following URL (usually takes 10-20 minutes): https://nr-sparsi-docs-gcp-vpc-service-control--docs-website-netlify.netlify.app |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirror PR Summary
This is a preview copy of PR #25790 from @nr-sparsi, created at 2026-09-28 13:52:25 IST.
Original PR Details
docs/gcp-vpc-service-controlsnr-sparsi-docs-gcp-vpc-service-control1269764ad0a30420a75a25e99bf2eb492872ad06(1269764)Original PR Description:
Summary
sts.googleapis.com,iamcredentials.googleapis.com) beyond the four shared with the service account flow, since WIF uses them for token exchange and short-lived credential generation.PERMISSION_DENIED ... vpcServiceControlsUniqueIdentifiererror signature customers see when the perimeter blocks these calls, so it's searchable.Context
Raised from a customer support thread where a GCP WIF integration behind a VPC SC perimeter was failing with
PERMISSION_DENIEDerrors. Support (#help-aws-gcp) identified and confirmed the required ingress rules, and the customer separately confirmed neither the WIF nor service account setup docs mention VPC SC at all.Test plan
Verified via
web_fetchthat neither the current WIF nor service account setup pages mention VPC SC.Docs preview build renders the new sections correctly (Callout, headings, code block).