Halaman ini menjelaskan cara meluncurkan solusi Apigee Developer Portal Kickstart dari Cloud Marketplace
dengan opsi konfigurasi default.
Dalam banyak kasus, ada beberapa opsi untuk penyesuaian portal yang sesuai dengan kebutuhan penskalaan, keamanan, atau pemantauan Anda. Lihat
Menyesuaikan solusi Apigee Developer Portal Kickstart di Cloud Marketplace untuk mengetahui opsi penyesuaian tertentu yang harus dipertimbangkan sebelum men-deploy portal Anda.
Sebelum memulai
Tutorial ini dimaksudkan untuk memandu Anda memahami langkah-langkah yang diperlukan untuk konfigurasi portal default.
Sebelum men-deploy portal untuk penggunaan pengujian atau produksi, lihat
Menyesuaikan solusi Apigee Developer Portal Kickstart di Cloud Marketplace untuk mengetahui langkah-langkah konfigurasi prasyarat yang diperlukan untuk tugas berikut:
Meluncurkan Apigee Developer Portal Kickstart baru
Ikuti langkah-langkah di bawah untuk mengonfigurasi dan men-deploy solusi Apigee Developer Portal Kickstart dari Cloud Marketplace:
Di Google Cloud console, buka
halaman Cloud Marketplace dan pilih solusi Apigee Developer Portal Kickstart.
Klik Launch.
Konfigurasi New Apigee Developer Portal deployment.
Masukkan Nama deployment. Contoh, portal-dev. Nama deployment Anda:
Tidak boleh lebih dari 10 karakter.
Cocok dengan ekspresi reguler [a-z]([-a-z0-9]*[a-z0-9])?. Artinya, karakter pertama harus berupa huruf kecil, dan semua karakter berikutnya harus berupa tanda hubung, huruf kecil, atau angka, kecuali karakter terakhir yang tidak boleh berupa tanda hubung.
Lihat panduan Compute Engine tentang
Konvensi penamaan untuk mengetahui detail tambahan.
Pilih Zona Pilihan untuk deployment Anda dari menu drop-down. Untuk mengetahui detail selengkapnya tentang resource Compute Engine yang tersedia di berbagai zona, lihat Region dan Zona.
Pilih Jenis mesin untuk instance Compute Engine dari daftar drop-down.
Nilai defaultnya adalah 1vCPU.
Opsional: Klik Sesuaikan untuk mengubah Jenis mesin, Inti, dan Memori yang dipilih untuk instance Compute Engine.
Buat Akun Layanan baru atau Pilih Akun Layanan yang ada
untuk instance Compute Engine dalam deployment Anda. Akun Layanan digunakan oleh Compute Engine untuk mengakses Google API lainnya.
Untuk membuat Akun layanan baru, berikan informasi berikut:
Nama akun layanan: ID unik ini akan muncul di alamat email akun layanan yang disediakan selama pembuatan. Contoh, sa-name@project-id..
ID akun layanan: ID harus terdiri dari 6 hingga 30 karakter, dan dapat
berisi karakter alfanumerik huruf kecil dan tanda pisah.
Deskripsi akun layanan: deskripsi singkat akun layanan
Untuk memilih Akun Layanan yang ada, Pilih Akun Layanan dari menu drop-down
Akun Layanan yang tersedia dalam project Anda dengan peran yang benar.
Opsional: Konfigurasi opsi Boot Disk:
Pilih Boot disk type dari menu drop-down. Nilai defaultnya adalah
Standard Persistent Disk.
Pilih Boot disk size dari menu dropdown. Nilai defaultnya adalah
200GB.
Lihat Opsi penyimpanan untuk perbandingan opsi penyimpanan dan harga disk.
Opsional: Konfigurasi opsi Jaringan:
Portal baru disediakan dengan alamat IP default untuk terhubung ke instance CloudSQL.
Secara opsional, centang kotak untuk mengonfigurasi HTTPS di portal baru menggunakan domain nip.io.
nip.io adalah layanan pihak ketiga yang dapat menyediakan DNS karakter pengganti untuk alamat IP.
Jika ingin menggunakan nip.io untuk pengembangan dan pengujian, Anda dapat mengubah domain dalam
konfigurasi load balancer sebelum penggunaan produksi. Lihat Menggunakan
domain pengujian untuk mengetahui contoh langkah-langkah yang diperlukan.
Opsional: Konfigurasi Cloud Logging dan Monitoring:
Cloud Logging dan Cloud Monitoring diaktifkan secara default untuk deployment Apigee Developer Portal Kickstart yang baru.
Untuk menonaktifkan layanan Cloud, hapus centang pada kotak yang sesuai.
Secara default, Apigee Developer Portal Kickstart menggunakan
Kunci Enkripsi yang Dikelola Google
untuk mengamankan akses ke instance Cloud SQL Anda.
Untuk menggunakan kunci enkripsi yang dikelola pelanggan (CMEK) yang dikonfigurasi untuk mengamankan akses ke Cloud SQL, masukkan Nama Resource Kunci enkripsi
di kolom teks.
Klik Deploy.
Selamat, Anda berhasil men-deploy Apigee Developer Portal Kickstart.
Melihat deployment portal Anda
Untuk melihat detail deployment portal Anda:
Dari halaman Apigee Developer Portal Kickstart, klik View Past deployments.
Tindakan ini akan mengarahkan Anda ke dasbor Deployment Manager.
Untuk melihat detail deployment portal tertentu, pilih deployment portal yang diinginkan dari daftar. Halaman
detail akan merekomendasikan langkah selanjutnya, menautkan ke dokumentasi tambahan, dan memberikan link serta ID untuk
layanan Cloud yang disediakan, termasuk yang berikut:
Grup Instance
Instance Cloud SQL
Instance Filestore
Aturan Firewall
Load Balancer
Untuk mengetahui informasi selengkapnya tentang cara mengelola, memperbarui, dan menghapus deployment, lihat dokumentasi
Deployment Manager.
Pembersihan
Agar tidak menimbulkan biaya pada akun Google Cloud Anda untuk resource yang digunakan dalam panduan memulai ini, Anda dapat menghapus deployment Anda. Anda juga dapat
menghapus project Google Cloud yang digunakan untuk tutorial ini.
[[["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\u003eThis page outlines how to launch the Apigee Developer Portal Kickstart solution from the Cloud Marketplace using default configuration settings for Apigee and Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eBefore deploying a portal, users should consider customizations such as private IP addresses, customer-managed encryption keys, connecting to an Apigee org, configuring HTTPS, or launching a production-ready portal.\u003c/p\u003e\n"],["\u003cp\u003eTo deploy the portal, users must navigate to the Apigee Developer Portal Kickstart in the Cloud Marketplace, configure deployment settings like name, zone, and machine type, and optionally customize boot disk, networking, logging, monitoring, and encryption options.\u003c/p\u003e\n"],["\u003cp\u003eAfter deployment, users can view details, manage, update, or delete the deployment via the Deployment Manager dashboard, which also provides links to provisioned Cloud services and next steps for the user.\u003c/p\u003e\n"],["\u003cp\u003eUsers can avoid incurring charges by deleting their deployment and project after use, and they can find support resources and further customization options through the provided links.\u003c/p\u003e\n"]]],[],null,["# Get started with Apigee Developer Portal Kickstart from Cloud Marketplace\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nThis page describes how to launch the Apigee Developer Portal Kickstart solution from Cloud Marketplace\nwith *default* configuration options.\n\nIn many cases, there are multiple options for portal customization to suit your scaling, security, or monitoring needs. See [Customize the Apigee Developer Portal Kickstart solution in Cloud Marketplace](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize) for specific customization options\nto consider before deploying your portal.\n\nBefore you begin\n----------------\n\nThis tutorial is intended to familiarize you with the steps required for a default portal configuration.\nBefore you deploy a portal for testing or production usage, see [Customize the Apigee Developer Portal Kickstart solution in Cloud Marketplace](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize) for the prerequisite configuration steps needed for the following tasks:\n\n- [Configure a private IP address for using CloudSQL in a VPC network](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize#vpc-service-controls)\n- [Use customer-managed encryption keys for your deployment](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize#cmek)\n- [Connect your portal to an Apigee or Apigee hybrid org](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize#connect)\n- [Configure HTTPS for testing](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize#https)\n- [Launch a production-ready portal](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize#production)\n\nLaunching a new Apigee Developer Portal Kickstart\n-------------------------------------------------\n\nFollow the steps below to configure and deploy the Apigee Developer Portal Kickstart solution from Cloud Marketplace:\n\n1. In the Google Cloud console, go to the [Cloud Marketplace page](https://console.cloud.google.com/marketplace) and select the **Apigee Developer Portal Kickstart** solution.\n2. Click **Launch**.\n3. Configure the **New Apigee Developer Portal deployment** .\n 1. Enter the **Deployment name** . For example, `portal-dev`. The name of your deployment:\n - Should not exceed 10 characters.\n - Match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?`. This means that the first character must be a lowercase letter, and all the following characters must be hyphens, lowercase letters, or digits, except the last character, which cannot be a hyphen.\n - See Compute Engine guidelines on [Naming conventions](https://cloud.google.com/compute/docs/naming-resources#resource-name-format) for addition details.\n 2. Select the **Preferred Zone** for your deployment from the dropdown list. For more details regarding Compute Engine resources available in various zones, see [Regions and Zones](https://cloud.google.com/compute/docs/regions-zones).\n 3. Select the **Machine type** for the Compute Engine instance from the dropdown list. The default value is `1vCPU`.\n - Optional: Click **Customize** to change the selected **Machine type** , **Cores** , and **Memory** for the Compute Engine instance.\n - See [Creating a VM Instance with a custom machine type](https://cloud.google.com/compute/docs/instances/creating-instance-with-custom-machine-type)for more information on machine type customization options.\n 4. **Create a new Service Account** or **Select an existing Service Account** for the Compute Engine instances in your deployment. The Service Account is used by Compute Engine to access other Google APIs.\n - To create a new Service account, provide the following information:\n - **Service account name** : This unique identifier will appear in the service account's email address that is provisioned during creation. For example, \u003cvar translate=\"no\"\u003esa-name\u003c/var\u003e`@`\u003cvar translate=\"no\"\u003eproject-id\u003c/var\u003e`.iam.gserviceaccount.com`.\n - **Service account ID**: The ID must be between 6 and 30 characters, and can contain lowercase alphanumeric characters and dashes.\n - **Service account description**: a brief description of the service account\n - See [Creating a service account](https://cloud.google.com/iam/docs/creating-managing-service-accounts) for additional details.\n - To select an existing Service Account, **Select a Service Account** from the dropdown list of available Service Accounts within your project with the correct roles.\n | **Note** : The existing Service Account must have the following roles: `\n | `\n | - roles/storage.objectViewer\n | - roles/logging.logWriter\n | - roles/runtimeconfig.admin\n | - roles/apigee.developerAdmin\n | - roles/cloudsql.client\n | - roles/monitoring.metricWriter\n | `\n | `\n 5. Optional: Configure Boot Disk options:\n - Select the **Boot disk type** from the dropdown list. The default value is `\n Standard Persistent Disk`.\n - Select the **Boot disk size** from the dropdown list. The default value is `\n 200GB`.\n - See [Storage options](https://cloud.google.com/compute/docs/disks) for a comparison of storage options and disk pricing.\n 6. Optional: Configure **Networking** options:\n - New portals are provisioned with a default IP address for connecting to the CloudSQL instance.\n - Optionally, select the checkbox to configure HTTPS on the new portal using an `nip.io` domain. [nip.io](https://nip.io/) is a third-party service that can provide a wildcard DNS for an IP address. If you wish to use `nip.io` for development and testing, you can modify the domain in the load balancer configuration prior to production use. See [Using a\n testing domain](https://cloud.google.com/anthos/run/docs/default-domain) for an example of the steps required.\n 7. Optional: Configure **Cloud Logging and Monitoring** :\n - Cloud Logging and Cloud Monitoring are enabled for new Apigee Developer Portal Kickstart deployments by default.\n - To disable either Cloud service, uncheck the corresponding box.\n - See the [Cloud Logging](https://cloud.google.com/logging/docs) and [Cloud Monitoring](https://cloud.google.com/monitoring/docs) documentation for more details on configuration options.\n 8. Optional: Configure **Encryption** options:\n - By default, the Apigee Developer Portal Kickstart uses [Google Managed Encryption Keys](https://cloud.google.com/storage/docs/encryption/default-keys) to secure access to your Cloud SQL instance.\n - To use a configured customer-managed encryption key (CMEK) to secure access to Cloud SQL, enter the **Resource Name of the Encryption key** in the text field.\n 9. Click **Deploy**.\n\n Congratulations, you have successfully deployed a Apigee Developer Portal Kickstart!\n\n Viewing your portal deployment\n ------------------------------\n\n\n To see the details of your portal deployment:\n 1. From the Apigee Developer Portal Kickstart page, click **View Past deployments** . This will take you to the [**Deployment Manager**](https://console.cloud.google.com/dm/deployments) dashboard.\n 2. To view the details of a given portal deployment, select the desired portal deployment from the list. The detail page will recommend next steps, link to additional documentation, and provide links and IDs for provisioned Cloud services, including the following:\n - Instance Group\n - Cloud SQL Instance\n - Filestore Instance\n - Firewall Rule\n - Load Balancer\n 3. For more information on managing, updating, and deleting deployments, see the [Deployment Manager](https://cloud.google.com/deployment-manager/docs) documentation.\n\n Clean up\n --------\n\n To avoid incurring charges to your Google Cloud account for the resources used in this quickstart, you can [delete your deployment](https://console.cloud.google.com/dm/deployments). You can also delete the Google Cloud project used for this tutorial.\n\n What's next\n -----------\n\n - Additional options for [Customize the Apigee Developer Portal Kickstart solution in Cloud Marketplace](/apigee/docs/api-platform/publish/drupal/apigee-cloud-marketplace-customize).\n - Learn more about [Support resources](/apigee/docs/api-platform/publish/drupal/get-support-cloud-marketplace) for the Apigee Developer Portal Kickstart solution."]]
