Langkah ini menjelaskan cara membuat akun layanan Google Cloud
yang diperlukan agar Apigee hybrid dapat beroperasi.
Membuat akun layanan
Apigee hybrid menggunakan akun layanan Google Cloud untuk
mengizinkan komponen hybrid berkomunikasi dengan melakukan panggilan API yang diotorisasi.
Pada langkah ini, Anda akan menggunakan alat command line hybrid Apigee untuk membuat kumpulan akun layanan
dan mendownload file kunci pribadi akun layanan.
Di lingkungan hybrid produksi, Apigee merekomendasikan penggunaan akun layanan
terpisah untuk setiap komponen. Untuk tujuan tutorial ini, Anda dapat membuat satu akun layanan
bernama "apigee-non-prod" yang dapat digunakan untuk semua komponen.
Untuk mempelajari akun layanan lebih lanjut dan membaca daftar lengkap akun layanan yang direkomendasikan untuk
lingkungan produksi, lihat hal berikut:
Apigee menyediakan alat, create-service-account, yang membuat akun layanan,
menetapkan peran ke akun layanan, serta membuat dan mendownload file kunci untuk akun
layanan dalam satu perintah.
Untuk mempelajari create-service-account dan semua
opsinya lebih lanjut, lihat create-service-account.
Pastikan variabel lingkungan HYBRID_FILES dan PROJECT_ID telah ditetapkan.
PROJECT_ID harus ditetapkan ke project ID Google Cloud Anda, karena alat create-service-account membaca variabel lingkungan PROJECT_ID untuk membuat akun layanan di project yang benar.
echo $HYBRID_FILES
echo $PROJECT_ID
Buat akun layanan non-prod dengan perintah berikut. Perintah ini membuat satu akun layanan bernama apigee-non-prod untuk digunakan di lingkungan non-produksi dan menempatkan file kunci yang didownload di direktori $HYBRID_FILES/service-accounts.
Pastikan kunci akun layanan dibuat menggunakan perintah berikut. Anda bertanggung jawab untuk menyimpan
kunci pribadi ini dengan aman. Nama file kunci diawali dengan nama project Google Cloud Anda.
ls $HYBRID_FILES/service-accounts
Hasilnya akan terlihat seperti berikut:
project_id-apigee-non-prod.json
Sekarang Anda telah membuat akun layanan dan menetapkan peran yang diperlukan oleh komponen hibrida
Apigee. Selanjutnya, buat sertifikat TLS yang diperlukan oleh gateway traffic masuk hybrid.
[[["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-09-04 UTC."],[[["\u003cp\u003eApigee hybrid utilizes Google Cloud service accounts for authorized API communication between its components.\u003c/p\u003e\n"],["\u003cp\u003eA command-line tool, \u003ccode\u003ecreate-service-account\u003c/code\u003e, is available to create service accounts, assign roles, and download the necessary key files.\u003c/p\u003e\n"],["\u003cp\u003eFor non-production environments, a single service account named "apigee-non-prod" can be used for all components, simplifying setup.\u003c/p\u003e\n"],["\u003cp\u003eProduction environments are recommended to use a separate service account per component for enhanced security and organization.\u003c/p\u003e\n"],["\u003cp\u003eThe tool will create the service account, create the key files, and assign the service accounts' roles, all in a single command.\u003c/p\u003e\n"]]],[],null,["# Step 4: Create service accounts\n\n| You are currently viewing version 1.9 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nThis step explains how to create the Google Cloud service accounts\nthat are required for Apigee hybrid to operate.\n\nCreate the service accounts\n---------------------------\n\n\nApigee hybrid uses Google Cloud [service accounts](/iam/docs/service-accounts) to\nallow hybrid components to communicate by making authorized API calls.\n\n\nIn this step, you use an Apigee hybrid command-line tool to create a set of service accounts\nand download the service account private key files.\n\nIn a production hybrid environment Apigee recommends using a separate\nservice account for each component. For the purposes of this tutorial, you can create a single service\naccount named \"apigee-non-prod\" that you can use for all components.\n\n\nTo learn more about service accounts and read the full list of service accounts recommended for\nproduction environments, see the following:\n\n- [About service accounts](/apigee/docs/hybrid/v1.9/sa-about)\n- [Service accounts and roles used by hybrid components](/apigee/docs/hybrid/v1.9/sa-about#recommended-sas)\n\n\nApigee provides a tool, `create-service-account`, that creates the service accounts,\nassigns the roles to the service accounts, and creates and downloads the key files for the service\naccount in a single command.\n\n- To learn more about `create-service-account` and all its options see, [`create-service-account`](/apigee/docs/hybrid/v1.9/create-service-account).\n- To learn about the related Google Cloud concepts, see [Creating\n and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts) and [Creating\n and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys).\n\n1. Make sure your **HYBRID_FILES** and **PROJECT_ID** environment variables are set.\n\n **PROJECT_ID** must be set to your Google cloud project ID, because the\n `create-service-account` tool reads the **PROJECT_ID** environment variable to\n create the service accounts in the correct project. \n\n echo $HYBRID_FILES\n echo $PROJECT_ID\n\n2. Create a *non-prod* service account with the following command. This command creates a single service account named `apigee-non-prod` for use in non-production environments and places the downloaded key file in the `$HYBRID_FILES/service-accounts` directory. \n\n ```\n $HYBRID_FILES/tools/create-service-account --env non-prod --dir $HYBRID_FILES/service-accounts\n ```\n | **Note:** If you would prefer to create all the individual service accounts for a production environment, use the following command: \n |\n | ```\n | $HYBRID_FILES/tools/create-service-account --env prod --dir $HYBRID_FILES/service-accounts\n | ```\n\n\n If you see the following prompt, enter \u003ckbd\u003ey\u003c/kbd\u003e: \n\n ```transact-sql\n [INFO]: gcloud configured project ID is project_id.\n Enter: y to proceed with creating service account in project: project_id\n Enter: n to abort.\n ```\n\n\n If this is the first time you are creating an SA with a particular name assigned, then the\n tool creates it without further prompts.\n\n\n If, however, you see the following message and prompt, enter \u003ckbd\u003ey\u003c/kbd\u003e to generate\n new keys: \n\n ```transact-sql\n [INFO]: Service account apigee-non-prod@\u003cvar translate=\"no\"\u003eproject_id\u003c/var\u003e.iam.gserviceaccount.com already exists.\n ...\n [INFO]: The service account might have keys associated with it. It is recommended to use existing keys.\n Press: y to generate new keys.(this does not deactivate existing keys)\n Press: n to skip generating new keys.\n ```\n | **Note:** The Cloud Pub/Sub API must be enabled in the Google Cloud project that owns the service account for Synchronizer. To see if you enabled this API, see [Enable APIs](/apigee/docs/hybrid/v1.9/precog-enableapi).\n3. Verify that the service account key was created using the following command. You are responsible for storing these private keys securely. The key filenames are prefixed with the name of your Google Cloud project. \n\n ```\n ls $HYBRID_FILES/service-accounts\n ```\n\n\n The result should look something like the following: \n\n ```scdoc\n project_id-apigee-non-prod.json\n ```\n\n| **Tip:** Apigee hybrid includes a validator that checks your service accounts' key files and permissions when [apigeectl](/apigee/docs/hybrid/v1.9/cli-reference) applies the Apigee hybrid runtime components to your cluster. This validation is enabled by default. For more information, see [Service account\n| validation](/apigee/docs/hybrid/v1.9/sa-validation).\n\n\nYou now have created service accounts and assigned the roles needed by the Apigee hybrid\ncomponents. Next, create the TLS certificates required by the hybrid ingress gateway.\n[1](/apigee/docs/hybrid/v1.9/install-create-cluster) [2](/apigee/docs/hybrid/v1.9/install-cert-manager) [3](/apigee/docs/hybrid/v1.9/install-apigeectl) [4](/apigee/docs/hybrid/v1.9/install-service-accounts) [(NEXT) Step 5: Create TLS certificates](/apigee/docs/hybrid/v1.9/install-create-tls-certificates) [6](/apigee/docs/hybrid/v1.9/install-configure-cluster) [7](/apigee/docs/hybrid/v1.9/install-enable-synchronizer-access) [8](/apigee/docs/hybrid/v1.9/install-hybrid-runtime) [9](/apigee/docs/hybrid/v1.9/install-expose-apigee-ingress) [10](/apigee/docs/hybrid/v1.9/install-deploy-proxy)\n\n\u003cbr /\u003e"]]
