Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Este documento explica como usar o VPC Service Controls com o Batch.
O VPC Service Controls
permite proteger os recursos e dados dos serviços do Google Cloud
isolando recursos específicos em perímetros de serviço. Um perímetro de serviço bloqueia conexões com serviços do Google Cloud fora do perímetro e conexões da Internet que não são explicitamente permitidas.
Se o projeto ou a rede usar o VPC Service Controls para restringir
o acesso à rede do Batch, configure os
jobs do Batch para serem executados no perímetro de serviço necessário.
Para saber como, consulte
Criar um job que é executado em um perímetro de serviço
neste documento.
Para mais informações sobre conceitos de rede e
quando configurar a rede, consulte
Visão geral da rede em lote.
Para receber as permissões necessárias para usar os VPC Service Controls com o Batch,
peça ao administrador para conceder a você os
seguintes papéis do IAM:
Se você criar um job que seja executado em um perímetro de serviço, será necessário identificar a
rede que você quer usar para o job. A rede especificada para um
job executado em um perímetro de serviço precisa atender aos seguintes requisitos:
A rede inclui uma sub-rede no local em que você quer executar o job.
A rede está no perímetro de serviço necessário e usa o Acesso privado do Google para permitir o acesso aos domínios das APIs e dos serviços usados pelo seu job. Para mais informações, consulte
Configurar um perímetro de serviço para o Batch
neste documento.
Para configurar um perímetro de serviço para o Batch, faça o seguinte:
Planeje a configuração do perímetro de serviço. Para uma visão geral dos estágios de configuração dos perímetros de serviço, consulte a documentação do VPC Service Controls sobre Detalhes e configuração do perímetro de serviço.
Para usar o Batch, o perímetro de serviço precisa atender aos seguintes
requisitos:
Serviços restritos:para proteger o Batch em um perímetro de serviço, inclua os serviços Google Cloud necessários para seus jobs do Batch nesse perímetro, como:
API Batch (batch.googleapis.com)
API Cloud Logging (logging.googleapis.com): necessária se você quiser
que seus jobs gravem registros no Cloud Logging. (Recomendado)
API Container Registry (containerregistry.googleapis.com):
obrigatória se você enviar um job que usa contêineres com uma imagem do
Container Registry.
API Artifact Registry (artifactregistry.googleapis.com):
obrigatória se você enviar um job que usa contêineres com uma imagem do
Artifact Registry.
API Cloud Storage (storage.googleapis.com): necessária para alguns
jobs que usam um
bucket do Cloud Storage.
Obrigatório se você usar uma
imagem para seu job em lote que não tenha o
agente de serviço em lote
pré-instalado.
Para saber como ativar cada um desses serviços no seu perímetro de serviço, consulte
Serviços acessíveis por VPC.
Redes VPC:cada job do Batch
requer uma rede VPC. Portanto, o perímetro de serviço precisa
incluir uma rede VPC em que os jobs do Batch
podem ser executados. Para saber como configurar uma rede VPC que
pode executar seus jobs do Batch em um perímetro de serviço, consulte
os seguintes documentos:
Criar um job que seja executado em um perímetro de serviço
Ao criar um job que é executado em um perímetro de serviço, também é necessário
bloquear o acesso externo para todas as VMs em que um job é executado e especificar uma rede e
sub-rede que permitam que o job acesse as APIs necessárias.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-02 UTC."],[[["\u003cp\u003eVPC Service Controls protect Google Cloud resources by isolating them within service perimeters, blocking unauthorized connections.\u003c/p\u003e\n"],["\u003cp\u003eTo use Batch within a service perimeter, configure the perimeter to include necessary Google Cloud services like the Batch API, Cloud Logging API, and others depending on the job's needs.\u003c/p\u003e\n"],["\u003cp\u003eBatch jobs within a service perimeter require a VPC network that is also within the perimeter and uses Private Google Access.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating Batch jobs that run within a service perimeter, you must specify a network and subnet that allows access to required APIs and blocks external access for all VMs.\u003c/p\u003e\n"],["\u003cp\u003eDefault Batch VM OS images are recommended when using jobs with VPC Service Controls, as Batch does not guarantee support for custom VM OS images.\u003c/p\u003e\n"]]],[],null,["# Use VPC Service Controls with Batch\n\nThis document explains how to use VPC Service Controls with Batch.\n[VPC Service Controls](/vpc-service-controls/docs/overview#capabilities)\nallows you to protect the resources and data of Google Cloud services\nby isolating specific resources into service perimeters. A service\nperimeter blocks connections with Google Cloud services outside\nthe perimeter and any connections from the internet that are not explicitly\nallowed.\n\n- To configure a VPC Service Controls service perimeter to use Batch, see [Configure a service perimeter for Batch](#configure-service-perimeter) in this document.\n- If your project or network uses VPC Service Controls to restrict networking access for Batch, you must configure your Batch jobs to run in the required service perimeter. To learn how, see [Create a job that runs in a service perimeter](#create-job-service-perimeter) in this document.\n\nFor more information about networking concepts and\nwhen to configure networking, see\n[Batch networking overview](/batch/docs/networking-overview).\n| **Caution:** Batch does not guarantee VPC Service Controls support for jobs with custom VM OS images. Only default Batch VM OS images are recommended for jobs that use VPC Service Controls. For more information about VM OS images and how to restrict VM OS images, see [VM OS environment overview](/batch/docs/vm-os-environment-overview).\n\nBefore you begin\n----------------\n\n1. If you haven't used Batch before, review [Get started with Batch](/batch/docs/get-started) and enable Batch by completing the [prerequisites for projects and users](/batch/docs/get-started#prerequisites).\n2.\n\n To get the permissions that\n you need to use VPC Service Controls with Batch,\n\n ask your administrator to grant you the\n following IAM roles:\n\n - To configure a service perimeter: [Access Context Manager Editor](/iam/docs/roles-permissions/accesscontextmanager#accesscontextmanager.policyEditor) (`roles/accesscontextmanager.policyEditor`) on the project\n - To create a job:\n - [Batch Job Editor](/iam/docs/roles-permissions/batch#batch.jobsEditor) (`roles/batch.jobsEditor`) on the project\n - [Service Account User](/iam/docs/roles-permissions/iam#iam.serviceAccountUser) (`roles/iam.serviceAccountUser`) on the [job's service account](/batch/docs/create-run-job-custom-service-account#create-job-service-account), which by default is the [default Compute Engine service account](/compute/docs/access/service-accounts#default_service_account)\n - To identify the service perimeter for a project or network: [Access Context Manager Reader](/iam/docs/roles-permissions/accesscontextmanager#accesscontextmanager.policyReader) (`roles/accesscontextmanager.policyReader`) on the project\n - To identify the network and subnet for a job: [Compute Network Viewer](/iam/docs/roles-permissions/compute#compute.networkViewer) (`roles/compute.networkViewer`) on the project\n\n\n For more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\n You might also be able to get\n the required permissions through [custom\n roles](/iam/docs/creating-custom-roles) or other [predefined\n roles](/iam/docs/roles-overview#predefined).\n3. If you create a job that runs in a service perimeter, you need to identify the network that you want to use for the job. The network you specify for a job that runs in a service perimeter must meet the following requirements:\n - The network is a [Virtual Private Cloud (VPC) network](/vpc/docs/vpc) that is in the same project as the job or is a [Shared VPC network](/vpc/docs/shared-vpc) that is hosted by or shared with the project for the job.\n - The network includes a [subnetwork (subnet)](/vpc/docs/subnets) in the location where you want to run the job.\n - The network is in the required service perimeter and uses Private Google Access to allow access to the domains for the APIs and services that your job uses. For more information, see [Configure a service perimeter for Batch](#configure-service-perimeter) in this document.\n\n For more information, see [Create\n and manage VPC networks](/vpc/docs/create-modify-vpc-networks).\n\n\u003cbr /\u003e\n\nConfigure a service perimeter for Batch\n---------------------------------------\n\nTo configure a service perimeter for Batch, do the following:\n\n1. Plan the configuration for your service perimeter. For an overview of the\n configuration stages for service perimeters, see VPC Service Controls\n documentation for\n [Service perimeter details and configuration](/vpc-service-controls/docs/service-perimeters).\n\n To use Batch, the service perimeter must meet the following\n requirements:\n - **Restricted services:** To secure Batch within a\n service perimeter, you must include the Google Cloud services that\n are required for your Batch jobs in that perimeter,\n such as the following services:\n\n - **Batch API** (`batch.googleapis.com`)\n - **Cloud Logging API** (`logging.googleapis.com`): Required if you want your jobs to write logs into Cloud Logging. (Recommended)\n - **Container Registry API** (`containerregistry.googleapis.com`): Required if you submit a job that uses any containers with an image from Container Registry.\n - **Artifact Registry API** (`artifactregistry.googleapis.com`): Required if you submit a job that uses any containers with an image from Artifact Registry.\n - **Filestore API** (`file.googleapis.com`): Required if your job uses a [Filestore file share](/batch/docs/create-run-job-storage#use-nfs).\n - **Cloud Storage API** (`storage.googleapis.com`): Required for some jobs that use a [Cloud Storage bucket](/batch/docs/create-run-job-storage#use-bucket). Required if you use an image for your Batch job that does not have the [Batch service agent](/batch/docs/get-started) pre-installed.\n\n To learn how to enable each of these services in your service perimeter, see\n [VPC accessible services](/vpc-service-controls/docs/vpc-accessible-services).\n | **Caution:** For your Batch jobs to be fully protected by the service perimeter, you must specify *all* services that you plan to use.\n\n For each service you include other than Batch, you also\n need to verify that your service perimeter meets the requirements listed\n for that service in the\n [VPC Service Controls supported products and limitations](/vpc-service-controls/docs/supported-products)\n documentation.\n - **VPC networks:** Each Batch job\n requires a VPC network, so your service perimeter must\n include a VPC network that Batch jobs\n can run on. To learn how to configure a VPC network that\n can run your Batch jobs inside a service perimeter, see\n the following documents:\n\n - For an overview of using VPC networks in a service perimeter, see [VPC networks management in service perimeters](/vpc-service-controls/docs/vpc-perimeters-management).\n - To learn how to use Private Google Access with VPC Service Controls to configure access to the Google Cloud services that are required for your Batch jobs, see [Set up private connectivity to Google APIs and services](/vpc-service-controls/docs/set-up-private-connectivity).\n - For more information about the networking requirements for Batch jobs, see [Job networking overview](/batch/docs/networking-overview).\n2. [Create a new service perimeter](/vpc-service-controls/docs/create-service-perimeters)\n or [update an existing service perimeter](/vpc-service-controls/docs/manage-service-perimeters#update)\n to meet these requirements.\n\nCreate a job that runs in a service perimeter\n---------------------------------------------\n\nWhen you create a job that runs in a service perimeter, you must also\nblock external access for all the VMs a job runs on and specify a network and\nsubnet that allow the job to access required APIs.\n\nTo create a job that runs in a service perimeter, follow the steps in the\ndocumentation for\n[Create a job that blocks external access for all VMs](/batch/docs/job-without-external-access)\nand specify a network that meets the\n[network requirements for a job that runs in a service perimeter](#network-requirements).\n\nWhat's next\n-----------\n\n- If you have issues creating or running a job, see [Troubleshooting](/batch/docs/troubleshooting).\n- Learn more about [networking](/batch/docs/networking-overview).\n- Learn more about [creating a job](/batch/docs/create-run-job).\n- Learn how to [view jobs and tasks](/batch/docs/view-jobs-tasks)."]]
