Migrate standard VPC connector to Direct VPC egress
Stay organized with collections
Save and categorize content based on your preferences.
This page is for networking specialists who want to migrate standard VPC
network traffic from using Serverless VPC Access connectors
to using Direct VPC egress
when sending traffic to a VPC network.
Direct VPC egress is faster and can handle more traffic than connectors,
delivering lower latency and higher throughput because it uses a new, direct
network path rather than connector instances.
Click the service that you want to migrate from a connector to Direct
VPC egress, then click Edit and deploy new revision.
Click the Networking tab.
From Connect to a VPC for outbound traffic, click Send traffic directly to a VPC.
In the Network field, select the VPC
network that you want to send traffic to.
In the Subnet field, select the subnet where your service receives IP
addresses from. You can deploy multiple services on the same subnet.
Optional: Enter the names of the network tags
that you want to associate with your service or services. Network tags are
specified at the revision-level. Each service revision can have different
network tags, such as network-tag-2.
For Traffic routing, select one of the following:
Route only requests to private IPs to the VPC to send only
traffic to internal addresses through the VPC network.
Route all traffic to the VPC to send all outbound traffic
through the VPC network.
Click Deploy.
To verify that your service is on your VPC network, click
the service, then click the Networking tab. The network and subnet
are listed in the VPC card.
You can now send requests directly from your Cloud Run service to
any resource on the VPC network, as allowed by your
firewall rules.
gcloud
To migrate a Cloud Run service from a connector to Direct VPC
egress using the Google Cloud CLI:
Update your Cloud Run service with the following command:
SUBNET with the name of your subnet. You can deploy or execute
multiple services or jobs on the same subnet.
Optional: NETWORK_TAG_NAMES with the comma-separated names
of the network tags
you want to associate with a service. For services, network tags are
specified at the revision-level. Each service revision can have
different network tags, such as network-tag-2.
Click the job that you want to migrate from a connector to Direct
VPC egress, then click Edit.
Click the Networking tab.
Click Container, Variables & Secrets, Connections, Security to
expand the job properties page.
Click the Connections tab.
From Connect to a VPC for outbound traffic, click Send traffic directly to a VPC.
In the Network field, select the VPC
network that you want to send traffic to.
In the Subnet field, select the subnet where your job receives IP
addresses from. You can deploy multiple jobs on the same subnet.
Optional: Enter the names of the network tags
that you want to associate with your service or services. Network tags are
specified at the revision-level. Each service revision can have different
network tags, such as network-tag-2.
For Traffic routing, select one of the following:
Route only requests to private IPs to the VPC to send only
traffic to internal addresses through the VPC network.
Route all traffic to the VPC to send all outbound traffic
through the VPC network.
Click Update.
To verify that your job is on your VPC network, click
the job, then click the Configuration tab. The network and subnet are
listed in the VPC card.
You can now execute your Cloud Run job and send requests from the
job to any resource on the VPC network, as allowed by your
firewall rules.
gcloud
To migrate a Cloud Run job from a connector to Direct VPC
egress using the Google Cloud CLI:
Update your Cloud Run job with the following command:
SUBNET with the name of your subnet. You can deploy or execute
multiple services or jobs on the same subnet.
Optional: NETWORK_TAG_NAMES with the names of the
network tags
you want to associate with a job. For jobs, network tags are specified
at the execution-level. Each job execution can have different network
tags, such as network-tag-2.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# Migrate standard VPC connector to Direct VPC egress\n\nThis page is for networking specialists who want to migrate standard VPC\nnetwork traffic from using [Serverless VPC Access connectors](/run/docs/configuring/vpc-connectors)\nto using [Direct VPC egress](/run/docs/configuring/vpc-direct-vpc)\nwhen sending traffic to a VPC network.\n\nDirect VPC egress is faster and can handle more traffic than connectors,\ndelivering lower latency and higher throughput because it uses a new, direct\nnetwork path rather than connector instances.\n\nBefore migration, we recommend that you familiarize yourself with Direct VPC\negress [prerequisites](/run/docs/configuring/vpc-direct-vpc#before_you_begin),\n[limitations](/run/docs/configuring/vpc-direct-vpc#limitations),\n[IP address allocation](/run/docs/configuring/vpc-direct-vpc#direct-vpc-ip-allocation),\nand [IAM permissions](/run/docs/configuring/vpc-direct-vpc#set_up_iam_permissions).\n\nMigrate services to Direct VPC egress\n-------------------------------------\n\n| **Important:** Connectors continue to incur charges even if they have no traffic and are disconnected. For details, see [pricing](/vpc/pricing#serverless-vpc-pricing). If you no longer need your connector, be sure to [delete](/run/docs/configuring/vpc-connectors#delete) it to avoid continued billing.\n\nMigrate services to Direct VPC egress gradually\n-----------------------------------------------\n\nWhen you migrate Cloud Run services from Serverless VPC Access\nconnectors to Direct VPC egress, we recommend that you do so in a gradual\ntransition.\n\nTo transition gradually:\n\n1. Follow the instructions in this section to update your service to use Direct VPC egress.\n2. [Split a small percentage of traffic](/run/docs/rollouts-rollbacks-traffic-migration#split-traffic) to determine whether the traffic works correctly.\n3. Update the traffic split to send all traffic to the new revision using Direct VPC egress.\n\nTo migrate traffic with Direct VPC egress for a service, use the\nGoogle Cloud console or Google Cloud CLI: \n\n### Console\n\n1. In the Google Cloud console, go to the **Cloud Run** page.\n\n [Go to Cloud Run](https://console.cloud.google.com/run)\n2. Click the service that you want to migrate from a connector to Direct\n VPC egress, then click **Edit and deploy new revision**.\n\n3. Click the **Networking** tab.\n\n4. From **Connect to a VPC for outbound traffic** , click **Send traffic directly to a VPC**.\n\n5. In the **Network** field, select the VPC\n network that you want to send traffic to.\n\n6. In the **Subnet** field, select the subnet where your service receives IP\n addresses from. You can deploy multiple services on the same subnet.\n\n7. Optional: Enter the names of the [network tags](/vpc/docs/add-remove-network-tags#restrictions)\n that you want to associate with your service or services. Network tags are\n specified at the revision-level. Each service revision can have different\n network tags, such as `network-tag-2`.\n\n8. For **Traffic routing**, select one of the following:\n\n - **Route only requests to private IPs to the VPC** to send only traffic to internal addresses through the VPC network.\n - **Route all traffic to the VPC** to send all outbound traffic through the VPC network.\n9. Click **Deploy**.\n\n10. To verify that your service is on your VPC network, click\n the service, then click the **Networking** tab. The network and subnet\n are listed in the **VPC** card.\n\n You can now send requests directly from your Cloud Run service to\n any resource on the VPC network, as allowed by your\n firewall rules.\n\n### gcloud\n\n\nTo migrate a Cloud Run service from a connector to Direct VPC\negress using the Google Cloud CLI:\n\n1. Update your Cloud Run service with the following command:\n\n ```bash\n gcloud run services update SERVICE_NAME \\\n --clear-vpc-connector \\\n --network=NETWORK \\\n --subnet=SUBNET \\\n --network-tags=NETWORK_TAG_NAMES \\\n --vpc-egress=EGRESS_SETTING \\\n --region=REGION\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name of your service.\n - \u003cvar translate=\"no\"\u003eNETWORK\u003c/var\u003e with the name of your VPC network.\n - \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e with the name of your subnet. You can deploy or execute multiple services or jobs on the same subnet.\n - Optional: \u003cvar translate=\"no\"\u003eNETWORK_TAG_NAMES\u003c/var\u003e with the comma-separated names of the [network tags](/vpc/docs/add-remove-network-tags#restrictions) you want to associate with a service. For services, network tags are specified at the revision-level. Each service revision can have different network tags, such as `network-tag-2`.\n - \u003cvar translate=\"no\"\u003eEGRESS_SETTING\u003c/var\u003e with an [egress setting value](/sdk/gcloud/reference/run/deploy#--vpc-egress):\n - `all-traffic`: Sends all outbound traffic through the VPC network.\n - `private-ranges-only`: Sends only traffic to internal addresses through the VPC network.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with a region for your service.\n2. To verify that your service is on your VPC network, run\n the following command:\n\n ```bash\n gcloud run services describe SERVICE_NAME \\\n --region=REGION\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name of your service.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region for your service that you specified in the previous step.\n\n The output should contain the name of your network, subnet, and egress\n setting, for example: \n\n VPC access:\n Network: default\n Subnet: subnet\n Egress: private-ranges-only\n\nYou can now send requests from your Cloud Run service to any\nresource on the VPC network, as allowed by your firewall\nrules.\n\nMigrate jobs to Direct VPC egress\n---------------------------------\n\n| **Important:** Connectors continue to incur charges even if they have no traffic and are disconnected. For details, see [pricing](/vpc/pricing#serverless-vpc-pricing). If you no longer need your connector, be sure to [delete](/run/docs/configuring/vpc-connectors#delete) it to avoid continued billing.\n\nYou can migrate traffic with Direct VPC egress for a job by using the\nGoogle Cloud console or Google Cloud CLI. \n\n### Console\n\n1. In the Google Cloud console, go to the **Cloud Run** page.\n\n [Go to Cloud Run](https://console.cloud.google.com/run)\n2. Click the job that you want to migrate from a connector to Direct\n VPC egress, then click **Edit**.\n\n3. Click the **Networking** tab.\n\n4. Click **Container, Variables \\& Secrets, Connections, Security** to\n expand the job properties page.\n\n5. Click the **Connections** tab.\n\n6. From **Connect to a VPC for outbound traffic** , click **Send traffic directly to a VPC**.\n\n7. In the **Network** field, select the VPC\n network that you want to send traffic to.\n\n8. In the **Subnet** field, select the subnet where your job receives IP\n addresses from. You can deploy multiple jobs on the same subnet.\n\n9. Optional: Enter the names of the [network tags](/vpc/docs/add-remove-network-tags#restrictions)\n that you want to associate with your service or services. Network tags are\n specified at the revision-level. Each service revision can have different\n network tags, such as `network-tag-2`.\n\n10. For **Traffic routing**, select one of the following:\n\n - **Route only requests to private IPs to the VPC** to send only traffic to internal addresses through the VPC network.\n - **Route all traffic to the VPC** to send all outbound traffic through the VPC network.\n11. Click **Update**.\n\n12. To verify that your job is on your VPC network, click\n the job, then click the **Configuration** tab. The network and subnet are\n listed in the **VPC** card.\n\nYou can now execute your Cloud Run job and send requests from the\njob to any resource on the VPC network, as allowed by your\nfirewall rules.\n\n### gcloud\n\n\nTo migrate a Cloud Run job from a connector to Direct VPC\negress using the Google Cloud CLI:\n\n1. Update your Cloud Run job with the following command:\n\n ```bash\n gcloud run jobs update JOB_NAME \\\n --clear-network \\\n --image=IMAGE_URL \\\n --network=NETWORK \\\n --subnet=SUBNET \\\n --network-tags=NETWORK_TAG_NAMES \\\n --vpc-egress=EGRESS_SETTING \\\n --region=REGION\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eJOB_NAME\u003c/var\u003e with the name of your job.\n - \u003cvar translate=\"no\"\u003eNETWORK\u003c/var\u003e with the name of your VPC network.\n - \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e with the name of your subnet. You can deploy or execute multiple services or jobs on the same subnet.\n - Optional: \u003cvar translate=\"no\"\u003eNETWORK_TAG_NAMES\u003c/var\u003e with the names of the [network tags](/vpc/docs/add-remove-network-tags#restrictions) you want to associate with a job. For jobs, network tags are specified at the execution-level. Each job execution can have different network tags, such as `network-tag-2`.\n - \u003cvar translate=\"no\"\u003eEGRESS_SETTING\u003c/var\u003e with an [egress setting value](/sdk/gcloud/reference/run/deploy#--vpc-egress):\n - `all-traffic`: Sends all outbound traffic through the VPC network.\n - `private-ranges-only`: Sends only traffic to internal addresses through the VPC network.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with a region for your job.\n2. To verify that your job is on your VPC network, run\n the following command:\n\n ```bash\n gcloud run jobs describe JOB_NAME \\\n --region=REGION\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eJOB_NAME\u003c/var\u003e with the name of your job.\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region for your job that you specified in the previous step.\n\n The output should contain the name of your network, subnet, and egress\n setting, for example: \n\n VPC access:\n Network: default\n Subnet: subnet\n Egress: private-ranges-only\n\nYou can now send requests from your Cloud Run job to any\nresource on the VPC network, as allowed by your firewall\nrules."]]