VPC Access connector failed to get healthy

I’m repeatedly getting this message when trying to create a serverless vpc connector either through terraform or manually. Parameters are default.

“An internal error occurred: VPC Access connector failed to get healthy. Please check GCE quotas, logs and org policies and recreate.”

In the console, I see “Connector is in a bad state, manual deletion recommended”.

No other useful information in the logs.

I do see this online, but my names are within the character limit.

https://cloud.google.com/knowledge/kb/serverless-vpc-access-connector-creation-failure-due-to-resource-defying-naming-convention-000004773

Would appreciate hints on where to look or how to make logs more verbose.

Thanks!

2 Likes

I believe I figured it out. I found this reference in the docs:

https://cloud.google.com/vpc/docs/configure-serverless-vpc-access#connector-creation-error

We use ClearDATA to harden our environment. They enforce org policy “Define trusted image projects” and specify a handful of allowed repos for images.

I just needed to add

projects/serverless-vpc-access-images

to

https://console.cloud.google.com/iam-admin/orgpolicies/compute-trustedImageProjects

Would sure be nice if GCP gave clearer, more specific errors.

3 Likes