Starting in version 1.14.2, Apigee hybrid supports large message payloads up to 30MB. The default message payload size is 10MB. See Message payload size.
To enable large message payload support for your hybrid installation, you need to make the following changes to your runtime configuration:
ENV_RELEASE_NAME is a name used to keep track of installation and upgrades of the
apigee-env chart. This name must be unique from the other Helm release names in your installation.
Usually this is the same as ENV_NAME. However, if your environment has the same name
as your environment group, you must use different release names for the environment and environment group,
for example dev-env-release and dev-envgroup-release. For more information on releases
in Helm, see Three big concepts class="external" in the
Helm documentation.
ENV_NAME is the name of the environment you are upgrading.
OVERRIDES_FILE is your edited overrides.yaml file.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["# Configure large message payload support in Apigee hybrid\n\n| You are currently viewing version 1.14 of the Apigee hybrid documentation. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nOverview\n--------\n\n\nStarting in version 1.14.2, Apigee hybrid supports large message payloads up to 30MB. The default message payload size is 10MB. See [Message payload size](/apigee/docs/api-platform/fundamentals/best-practices-api-proxy-design-and-development#size).\n\n\nTo enable large message payload support for your hybrid installation, you need to make the following changes to your runtime configuration:\n\n- Increase the heap size to 4Gi.\n- Increase [`runtime.resources.limits.memory`](/apigee/docs/hybrid/v1.14/config-prop-ref#runtime-resources-limits-memory) to 6Gi.\n- Increase [`runtime.resources.requests.memory`](/apigee/docs/hybrid/v1.14/config-prop-ref#runtime-resources-requests-memory) to 4Gi.\n\nConfigure large message payload support for Apigee hybrid\n---------------------------------------------------------\n\n1. Add the following stanza to your `overrides.yaml` file: \n\n ```\n runtime:\n cwcAppend:\n bin_setenv_max_mem: 4096m # Increase max heap size to 4 gigs\n resources:\n requests:\n memory: 4Gi\n limits:\n memory: 6Gi\n ```\n2. Upgrade the `apigee-env` chart for each environment in your installation:\n\n Dry run: \n\n ```\n helm upgrade ENV_RELEASE_NAME apigee-env/ \\\n --install \\\n --namespace APIGEE_NAMESPACE \\\n --set env=ENV_NAME \\\n -f OVERRIDES_FILE \\\n --dry-run=server\n ```\n - \u003cvar translate=\"no\"\u003eENV_RELEASE_NAME\u003c/var\u003e is a name used to keep track of installation and upgrades of the `apigee-env` chart. This name must be unique from the other Helm release names in your installation. Usually this is the same as \u003cvar translate=\"no\"\u003eENV_NAME\u003c/var\u003e. However, if your environment has the same name as your environment group, you must use different release names for the environment and environment group, for example `dev-env-release` and `dev-envgroup-release`. For more information on releases in Helm, see [Three big concepts class=\"external\"](https://helm.sh/docs/intro/using_helm/#three-big-concepts) in the Helm documentation.\n - \u003cvar translate=\"no\"\u003eENV_NAME\u003c/var\u003e is the name of the environment you are upgrading.\n - \u003cvar translate=\"no\"\u003eOVERRIDES_FILE\u003c/var\u003e is your edited `overrides.yaml` file.\n\n Upgrade the chart: \n\n ```\n helm upgrade ENV_RELEASE_NAME apigee-env/ \\\n --install \\\n --namespace APIGEE_NAMESPACE \\\n --set env=ENV_NAME \\\n -f OVERRIDES_FILE\n ```"]]
