Bagian ini menjelaskan penggunaan Apigee Connect untuk komunikasi antara platform manajemen hybrid dan layanan MART di platform runtime.
Pengantar
Apigee Connect memungkinkan platform pengelolaan hybrid Apigee terhubung dengan aman ke layanan MART di platform runtime tanpa mengharuskan Anda mengekspos endpoint MART di internet. Jika menggunakan
Apigee Connect, Anda tidak perlu mengonfigurasi gateway masuk MART dengan alias host dan
sertifikat DNS resmi.
Mengonfigurasi Apigee Connect
Konfigurasikan Apigee Connect dalam penggantian Anda dengan properti konfigurasi connectAgent.
[[["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-18 UTC."],[[["\u003cp\u003eApigee Connect enables secure communication between the Apigee hybrid management plane and the MART service without exposing the MART endpoint to the internet.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration of Apigee Connect is done using the \u003ccode\u003econnectAgent\u003c/code\u003e property in your overrides file.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eapigee-mart\u003c/code\u003e service account, which requires the \u003ccode\u003eroles/apigeeconnect.Agent\u003c/code\u003e role, is utilized by Apigee Connect.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee Connect API must be enabled in the Google Cloud API Library for Apigee Connect to function.\u003c/p\u003e\n"],["\u003cp\u003eChanges to the Apigee Connect configuration are applied using the \u003ccode\u003eapigee-org\u003c/code\u003e chart with a Helm upgrade or install command, and its log categories include DATA_READ and DATA_WRITE.\u003c/p\u003e\n"]]],[],null,["# Apigee Connect\n\n| You are currently viewing version 1.12 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 section describes using Apigee Connect for communication between the hybrid management\nplane and the MART service in the runtime plane.\n\nIntroduction\n------------\n\nApigee Connect allows the Apigee hybrid management plane to connect securely to the MART service in\nthe runtime plane without requiring you to expose the MART endpoint on the internet. If you use\nApigee Connect, you do not need to configure the MART ingress gateway with a host alias and an\nauthorized DNS certificate.\n\nConfiguring Apigee connect\n--------------------------\n\n\nConfigure Apigee connect in your overrides with the [`connectAgent`](/apigee/docs/hybrid/v1.12/config-prop-ref#connectagent) configuration property.\n\n### Service account\n\n\nApigee connect uses the [`apigee-mart`](/apigee/docs/hybrid/v1.12/mart-service-account) service account. This service account requires the Apigee Connect Agent `roles/apigeeconnect.Agent` role. See [Service accounts and roles used by hybrid components](/apigee/docs/hybrid/v1.12/sa-about#recommended-sas).\n\n\nUse the [`connectAgent.serviceAccountPath`](/apigee/docs/hybrid/v1.12/config-prop-ref#connectagent-serviceaccountpath) or [`connectAgent.serviceAccountRef`](/apigee/docs/hybrid/v1.12/config-prop-ref#connectagent-serviceaccountref) configuration properties to specify the `apigee-mart` service account key. Alternatively you can [store the service account key in Hashicorp Vault](/apigee/docs/hybrid/v1.12/storing-sa-keys-in-vault).\n\n### API\n\n\nApigee Connect requires the **Apigee Connect API** in the [Google Cloud API Library](/apigee/docs/hybrid/v1.12/cloud.google.com/endpoints/docs/openapi/enable-api). For instructions on enabling APIs in the Google Cloud console, see [Step 3: Enable APIs](/apigee/docs/hybrid/v1.12/precog-enableapi).\n\n### Applying Apigee connect configuration\n\n\nApply changes to the Apigee connect configuration with the `apigee-org` chart with the following command: \n\n```\nhelm upgrade ORG_NAME apigee-org/ \\\n --namespace apigee \\\n --atomic \\\n -f OVERRIDES_FILE.yaml\n```\n| **Note:** If you see an error saying `Error: UPGRADE FAILED: \"`*ORG_NAME*`\" has no deployed releases`, replace `upgrade` with `install` and try the command again.\n\n### Image\n\n\nApigee connect uses the `gcr.io/apigee-release/hybrid/apigee-connect-agent:1.3.6` image. If you want to use a private image repository, see [Use a private image repository with Apigee hybrid](/apigee/docs/hybrid/v1.12/container-images).\n\nChecking Apigee connect logs\n----------------------------\n\n\nCheck the Apigee Connect Agent log. \n\n```\nkubectl logs -n namespace apigee-connect-agent-pod-name\n```\n\nThe Apigee Connect Agent reports the following log categories: \n\nFor help on viewing audit logs in Apigee hybrid see [Audit logging information](/apigee/docs/hybrid/v1.12/audit-logging-info).\n\nYou can set the level of logging with the [`connectAgent.logLevel`](/apigee/docs/hybrid/v1.12/config-prop-ref#connectagent-loglevel) configuration property."]]
