Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini menjelaskan cara menggunakan Kontrol Layanan VPC dengan Batch.
Kontrol Layanan VPC
memungkinkan Anda melindungi resource dan data Google Cloud layanan
dengan mengisolasi resource tertentu ke dalam perimeter layanan. Perimeter
layanan memblokir koneksi dengan Google Cloud layanan di luar
perimeter dan koneksi apa pun dari internet yang tidak diizinkan secara eksplisit.
Jika project atau jaringan Anda menggunakan Kontrol Layanan VPC untuk membatasi akses jaringan untuk Batch, Anda harus mengonfigurasi tugas Batch agar berjalan di perimeter layanan yang diperlukan.
Untuk mempelajari caranya, lihat
Membuat tugas yang berjalan dalam perimeter layanan
dalam dokumen ini.
Untuk mengetahui informasi selengkapnya tentang konsep jaringan dan
kapan harus mengonfigurasi jaringan, lihat
Ringkasan jaringan batch.
Untuk mendapatkan izin yang
diperlukan untuk menggunakan Kontrol Layanan VPC dengan Batch,
minta administrator Anda untuk memberi Anda
peran IAM berikut:
Untuk mengonfigurasi perimeter layanan:
Access Context Manager Editor (roles/accesscontextmanager.policyEditor)
di project
Untuk mengidentifikasi perimeter layanan untuk project atau jaringan:
Access Context Manager Reader (roles/accesscontextmanager.policyReader)
di project
Untuk mengidentifikasi jaringan dan subnet untuk tugas:
Compute Network Viewer (roles/compute.networkViewer)
di project
Anda mungkin juga bisa mendapatkan
izin yang diperlukan melalui peran
khusus atau peran
bawaan lainnya.
Jika membuat tugas yang berjalan di perimeter layanan, Anda harus mengidentifikasi
jaringan yang ingin digunakan untuk tugas tersebut. Jaringan yang Anda tentukan untuk
tugas yang berjalan di perimeter layanan harus memenuhi persyaratan berikut:
Jaringan mencakup subnetwork (subnet)
di lokasi tempat Anda ingin menjalankan tugas.
Jaringan berada di perimeter layanan yang diperlukan dan menggunakan
Akses Google Pribadi untuk mengizinkan akses ke domain untuk API dan
layanan yang digunakan tugas Anda. Untuk mengetahui informasi selengkapnya, lihat
Mengonfigurasi perimeter layanan untuk Batch
dalam dokumen ini.
Untuk mengonfigurasi perimeter layanan untuk Batch, lakukan hal berikut:
Rencanakan konfigurasi untuk perimeter layanan Anda. Untuk ringkasan tahap konfigurasi perimeter layanan, lihat dokumentasi Kontrol Layanan VPC untuk Detail dan konfigurasi perimeter layanan.
Untuk menggunakan Batch, perimeter layanan harus memenuhi persyaratan berikut:
Layanan terbatas: Untuk mengamankan Batch dalam perimeter layanan, Anda harus menyertakan layanan Google Cloud yang diperlukan untuk tugas Batch Anda dalam perimeter tersebut, seperti layanan berikut:
Batch API (batch.googleapis.com)
Cloud Logging API (logging.googleapis.com): Diperlukan jika Anda ingin tugas Anda menulis log ke Cloud Logging. (Disarankan)
Container Registry API (containerregistry.googleapis.com):
Diperlukan jika Anda mengirimkan tugas yang menggunakan container dengan image dari
Container Registry.
Artifact Registry API (artifactregistry.googleapis.com):
Diperlukan jika Anda mengirimkan tugas yang menggunakan container dengan image dari
Artifact Registry.
Filestore API (file.googleapis.com): Diperlukan jika tugas Anda menggunakan
berbagi file Filestore.
Cloud Storage API (storage.googleapis.com): Diperlukan untuk beberapa tugas yang menggunakan bucket Cloud Storage.
Wajib diisi jika Anda menggunakan image untuk tugas Batch yang tidak memiliki agen layanan Batch yang telah diinstal sebelumnya.
Untuk setiap layanan yang Anda sertakan selain Batch, Anda juga
perlu memverifikasi bahwa perimeter layanan Anda memenuhi persyaratan yang tercantum
untuk layanan tersebut dalam dokumentasi
Produk dan batasan yang didukung Kontrol Layanan VPC.
Jaringan VPC: Setiap tugas Batch memerlukan jaringan VPC, sehingga perimeter layanan Anda harus menyertakan jaringan VPC yang dapat digunakan untuk menjalankan tugas Batch. Untuk mempelajari cara mengonfigurasi jaringan VPC yang dapat menjalankan tugas Batch Anda di dalam perimeter layanan, lihat dokumen berikut:
Saat membuat tugas yang berjalan di perimeter layanan, Anda juga harus
memblokir akses eksternal untuk semua VM tempat tugas berjalan dan menentukan jaringan dan
subnet yang memungkinkan tugas mengakses API yang diperlukan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-12 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)."]]
