Documentation AEM as a Cloud Service User Guide

Configure Advanced Networking for AEM as a Cloud Service

Last update: March 26, 2025

Applies to:
Experience Manager as a Cloud Service

Topics:
Security

CREATED FOR:

Admin

This article introduces the advanced networking features available in AEM as a Cloud Service. These features include self-service and API provisioning of VPN, non-standard ports, and dedicated egress IP addresses.

In addition to this documentation, there is also a series of tutorials designed to walk you through each of the advanced networking options. See Advanced networking.

IMPORTANT

You can configure advanced networking in AEM as a Cloud Service either through the Cloud Manager UI or by using the Cloud Manager API (for example, cURL).

This article focuses on using the UI method. If you prefer to automate configuration through the API, see the Virtual Private Network (VPN) tutorial.

Automating advanced networking with the API
To automate advanced networking setup (such as VPN creation), you can use the Cloud Manager API:

curl -X POST https://cloudmanager.adobe.io/api/program/{PROGRAM_ID}/environment/{ENV_ID}/vpn \
  -H "Authorization: Bearer {ACCESS_TOKEN}" \
  -H "x-api-key: {API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "providerId": "aws",
    "portMappings": [
      {
        "name": "SSH",
        "protocol": "TCP",
        "port": 22
      }
    ]
  }'

See the full tutorial and more API examples in the Virtual Private Network (VPN) tutorial.

Overview

AEM as a Cloud Service offers the following advanced networking options:

Flexible port egress - Configure AEM as a Cloud Service to allow outbound traffic out of non-standard ports.
Dedicated egress IP address - Configure traffic out of AEM as a Cloud Service to originate from a unique IP.
Virtual Private Network (VPN) - Secure traffic between your infrastructure and AEM as a Cloud Service, if you have a VPN.

This article describes each of these options in detail and why you might use them, before describing how they are configured using the Cloud Manager UI and by using the API. The article concludes with some advanced use cases.

CAUTION

If you are already provisioned with legacy dedicated egress technology and want to configure one of these advanced networking options, contact Adobe Client Care.

Attempting to configure advanced networking with legacy egress technology can impact site connectivity.

Requirements and Limitations

When configuring advanced networking features, the following restrictions apply.

A program can provision a single advanced networking option (flexible port egress, dedicated egress IP address, or VPN).
Advanced networking is not available for sandbox programs.
A user must have the Administrator role to add and configure network infrastructure in your program.
The production environment must be created before network infrastructure can be added in your program.
Your network infrastructure must be in the same region as your production environment’s primary region.
- In the case where your production environment has extra publish regions, you may create another network infrastructure mirroring each additional region.
- You are not allowed to create more network infrastructures than the maximum number of regions configured in your production environment.
- You can define as many network infrastructures as available regions in your production environment, but the new infrastructure must be the same type as the previously created infrastructure.
- When creating multiple infrastructures, you are permitted to select from only those regions in which advanced networking infrastructure has not been created.

Configuring and Enabling Advanced Networking

Using advanced networking features requires two steps:

Configuration of the advanced networking option, whether flexible port egress, dedicated egress IP address, or VPN, must first be done at the program level.
To be used, the advanced networking option must then be enabled at the environment level.

Both steps can be done either using the Cloud Manager UI or the Cloud Manager API.

When using the Cloud Manager UI, this means creating advanced network configurations using a wizard at the program level and then editing each environment where you want to enable the configuration.
When using the Cloud Manager API, the /networkInfrastructures API endpoint is invoked at the program level to declare the desired type of advanced networking. It is followed by a call to the /advancedNetworking endpoint for each environment to enable the infrastructure and configure environment-specific parameters.

Flexible Port Egress

This advanced networking feature lets you configure AEM as a Cloud Service to egress traffic through ports other than HTTP (port 80) and HTTPS (port 443), which are open by default.

TIP

When deciding between flexible port egress and dedicated egress IP address, it is recommended you choose flexible port egress if a specific IP address is not required. The reason is because Adobe can optimize the performance of flexible port egress traffic.

NOTE

After creation, flexible port egress infrastructure types cannot be edited. The only way to change configuration values is to delete and recreate them.

UI Configuration

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
On the My Programs console, select the program.
From the Program Overview page, navigate to the Environments tab and select Network Infrastructure in the left panel.
In the Add network infrastructure wizard, select Flexible port egress.
From the Region drop-down menu, choose the desired region, then click Continue.
The Confirmation tab summarizes your selection and the next steps. Click Save to create the infrastructure.

A new record appears below the Network Infrastructure heading in the side panel. It includes details such as the type of infrastructure, status, region, and the environments where it is enabled.

New entry under Network Infrastructure

NOTE

Creation of the infrastructure for flexible port egress can take up to an hour after which it can be configured at the environment level.

API Configuration

Once per program, the POST /program/<programId>/networkInfrastructures endpoint is invoked, simply passing the value of flexiblePortEgress for the kind parameter and region. The endpoint responds with the network_id, and other information including the status.

Once called, it typically takes approximately 15 minutes for the networking infrastructure to be provisioned. A call to the Cloud Manager’s network infrastructure GET endpoint would show a status of ready.

TIP

The full set of parameters, exact syntax, and important information like what parameters cannot be changed later, can be referenced in the API documentation.

Traffic Routing

For http or https traffic going to ports other than 80 or 443 a proxy should be configured using the following host and port environment variables:

for HTTP: AEM_PROXY_HOST/ AEM_HTTP_PROXY_PORT (default to proxy.tunnel:3128 in AEM releases < 6094)
for HTTPS: AEM_PROXY_HOST/ AEM_HTTPS_PROXY_PORT (default to proxy.tunnel:3128 in AEM releases < 6094)

For example, here’s sample code to send a request to www.example.com:8443:

String url = "www.example.com:8443"
String proxyHost = System.getenv().getOrDefault("AEM_PROXY_HOST", "proxy.tunnel");
int proxyPort = Integer.parseInt(System.getenv().getOrDefault("AEM_HTTPS_PROXY_PORT", "3128"));
HttpClient client = HttpClient.newBuilder()
      .proxy(ProxySelector.of(new InetSocketAddress(proxyHost, proxyPort)))
      .build();

HttpRequest request = HttpRequest.newBuilder().uri(URI.create(url)).build();
HttpResponse<String> response = client.send(request, BodyHandlers.ofString());

If using non-standard Java™ networking libraries, configure proxies using the properties above, for all traffic.

Non-http/s traffic with destinations through ports declared in the portForwards parameter should reference a property called AEM_PROXY_HOST, along with the mapped port. For example:

DriverManager.getConnection("jdbc:mysql://" + System.getenv("AEM_PROXY_HOST") + ":53306/test");

The table below describes traffic routing:

Traffic

Destination condition

Port

Connection

External destination example

Http or https protocol

Standard http/s traffic

80 or 443

Allowed

Non-standard traffic (on other ports outside 80 or 443) through http proxy configured using the following environment variable and proxy port number. Do not declare the destination port in the Cloud Manager API call's portForwards parameter:

AEM_PROXY_HOST (default to `proxy.tunnel` in AEM releases < 6094)
AEM_HTTPS_PROXY_PORT (default to port 3128 in AEM releases < 6094)

Ports outside 80 or 443

Allowed

example.com:8443

Non-standard traffic (on other ports outside of ports 80 or 443) not using http proxy

Ports outside 80 or 443

Blocked

Non-http or non-https

Client connects to the AEM_PROXY_HOST environment variable using a portOrig declared in the portForwards API parameter.

Any

Allowed

mysql.example.com:3306

Everything else

Any

Blocked

db.example.com:5555

Apache / Dispatcher Configuration

The AEM Cloud Service Apache / Dispatcher tier’s mod_proxy directive can be configured using the properties described above.

ProxyRemote "http://example.com:8080" "http://${AEM_PROXY_HOST}:3128"
ProxyPass "/somepath" "http://example.com:8080"
ProxyPassReverse "/somepath" "http://example.com:8080"

SSLProxyEngine on //needed for https backends

ProxyRemote "https://example.com:8443" "http://${AEM_PROXY_HOST}:3128"
ProxyPass "/somepath" "https://example.com:8443"
ProxyPassReverse "/somepath" "https://example.com:8443"

Dedicated Egress IP Address

A dedicated IP address can enhance security when integrating with SaaS vendors (like a CRM vendor) or other integrations outside of AEM as a Cloud Service that offer an allowlist of IP addresses. By adding the dedicated IP address to the allowlist, it ensures that only traffic from the AEM Cloud Service is permitted to flow into the external service. This approach is in addition to traffic from any other IPs allowed.

The same dedicated IP is applied to all environments in a program, and applies to both Author and Publish services.

Without the dedicated IP address feature enabled, traffic from AEM as a Cloud Service flows through a shared set of IPs. These IPs are used by other customers of AEM as a Cloud Service.

Configuring a dedicated egress IP address is similar to flexible port egress. The main difference is that after configuration, traffic will always egress from a dedicated, unique IP. To find that IP, use a DNS resolver to identify the IP address associated with p{PROGRAM_ID}.external.adobeaemcloud.com. The IP address is not expected to change, but if it must change, advanced notification is provided.

TIP

When deciding between flexible port egress and dedicated egress IP address, choose flexible port egress if a specific IP address is not required. The reason is because Adobe can optimize the performance of flexible port egress traffic.

NOTE

If you were provisioned with a dedicated egress IP before 2021.09.30 (that is, before the September 2021 release), your dedicated egress IP feature only supports HTTP and HTTPS ports.

This outcome includes HTTP/1.1, and HTTP/2 when encrypted. Also, one dedicated egress endpoint can talk to any target only over HTTP / HTTPS on ports 80/443 respectively.

NOTE

Once created, dedicated egress IP address infrastructure types cannot be edited. The only way to change configuration values is to delete and recreate them.

UI Configuration

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
On the My Programs console, select the program.
From the Program Overview page, navigate to the Environments tab and select Network Infrastructure in the left panel.
In the Add network infrastructure wizard that opens, click Dedicated egress IP address.
From the Region drop-down menu, choose the desired region, then click Continue.
The Confirmation tab summarizes your selection and the next steps. Click Save to create the infrastructure.

A new record appears below the Network Infrastructure heading in the side panel. It includes details such as the type of infrastructure, status, region, and the environments where it is enabled.

New entry under Network Infrastructure

NOTE

Creation of the infrastructure for flexible port egress can take up to an hour after which it can be configured at the environment level.

API Configuration

Once per program, the POST /program/<programId>/networkInfrastructures endpoint is invoked, simply passing the value of dedicatedEgressIp for the kind parameter and region. The endpoint responds with the network_id, and other information including the status.

Once called, it typically takes approximately 15 minutes for the networking infrastructure to be provisioned. A call to the Cloud Manager’s network infrastructure GET endpoint would show a status of ready.

TIP

The full set of parameters, exact syntax, and important information like what parameters cannot be changed later, can be referenced in the API documentation.

Traffic Routing

Http or https traffic go through a preconfigured proxy, provided they use standard Java™ system properties for proxy configurations.

Non-http/s traffic with destinations through ports declared in the portForwards parameter should reference a property called AEM_PROXY_HOST, along with the mapped port. For example:

DriverManager.getConnection("jdbc:mysql://" + System.getenv("AEM_PROXY_HOST") + ":53306/test");

Traffic

Destination condition

Port

Connection

External destination example

Http or https protocol

Traffic to Azure (*.windows.net) or Adobe services

Any

Through the shared cluster IPs (not the dedicated IP)

adobe.io
api.windows.net

Host matching the nonProxyHosts parameter

80 or 443

Through the shared cluster IPs

Host matching the nonProxyHosts parameter

Ports outside 80 or 443

Blocked

Through http proxy configuration, configured by default for http/s traffic using the standard Java™ HTTP client library

Any

Through the dedicated egress IP

Ignores http proxy configuration (for example, if explicitly removed from standard Java™ HTTP client library or if a Java™ library that ignores standard proxy configuration is used)

80 or 443

Through the shared cluster IPs

Ignores http proxy configuration (for example, if explicitly removed from standard Java™ HTTP client library or if a Java™ library that ignores standard proxy configuration is used)

Ports outside 80 or 443

Blocked

Non-http or non-https

The client connects to AEM_PROXY_HOST env variable using a portOrig declared in the portForwards API parameter

Any

Through the dedicated egress IP

mysql.example.com:3306

Anything else

Blocked

Feature Usage

The feature is compatible with Java™ code or libraries that result in outbound traffic, provided they use standard Java™ system properties for proxy configurations. In practice, this approach should include most common libraries.

Below is a code sample:

public JSONObject getJsonObject(String relativePath, String queryString) throws IOException, JSONException {
  String relativeUri = queryString.isEmpty() ? relativePath : (relativePath + '?' + queryString);
  URL finalUrl = endpointUri.resolve(relativeUri).toURL();
  URLConnection connection = finalUrl.openConnection();
  connection.addRequestProperty("Accept", "application/json");
  connection.addRequestProperty("X-API-KEY", apiKey);

  try (InputStream responseStream = connection.getInputStream(); Reader responseReader = new BufferedReader(new InputStreamReader(responseStream, Charsets.UTF_8))) {
    return new JSONObject(new JSONTokener(responseReader));
  }
}

Some libraries require explicit configuration to use standard Java™ system properties for proxy configurations.

An example using Apache HttpClient that requires explicit calls to
HttpClientBuilder.useSystemProperties() or use
HttpClients.createSystem():

public JSONObject getJsonObject(String relativePath, String queryString) throws IOException, JSONException {
  String relativeUri = queryString.isEmpty() ? relativePath : (relativePath + '?' + queryString);
  URL finalUrl = endpointUri.resolve(relativeUri).toURL();

  HttpClient httpClient = HttpClientBuilder.create().useSystemProperties().build();
  HttpGet request = new HttpGet(finalUrl.toURI());
  request.setHeader("Accept", "application/json");
  request.setHeader("X-API-KEY", apiKey);
  HttpResponse response = httpClient.execute(request);
  String result = EntityUtils.toString(response.getEntity());
}

Debugging Considerations

To validate that traffic is indeed outgoing on the expected dedicated IP address, check logs in the destination service, if available. Otherwise, it may be useful to call out to a debugging service such as https://ifconfig.me/ip, which returns the calling IP address.

Virtual Private Network (VPN)

A VPN allows connecting to an on-premise infrastructure or data center from the author, publish, or preview instances. This ability can be useful, for example, to secure access to a database. It also allows connecting to SaaS vendors such as a CRM vendor that supports VPN.

Most VPN devices with IPSec technology are supported. Consult the information in the RouteBased configuration instructions column in this list of devices. Configure the device as described in the table.

NOTE

The following are limitations to a VPN infrastructure:

Support is limited to a single VPN connection
DNS Resolvers must be listed in the Gateway Address space to resolve private host names.

UI Configuration

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
On the My Programs console, select the program.
From the Program Overview page, navigate to the Environments tab and select Network Infrastructure in the left panel.
In the Add network infrastructure wizard that starts, select Virtual private network and provide the necessary information before clicking Continue.
- Region - The region in which the infrastructure should be created.
- Address Space - The address space can only be one /26 CIDR (64 IP addresses) or larger IP range in your own space.
  - This value can’t be changed later.
- DNS Information - A list of remote DNS resolvers.
  - Press Enter after inputting a DNS server address to add another.
  - Click the X after an address to remove it.
- Shared Key - Your VPN preshared key.
  - Select Show shared key to reveal the key so you can double-check its value.
On the Connections tab of the wizard, provide a Connection name to identify your VPN connection and click Add Connection.
In the Add connection dialog box, define your VPN connection, then click Save.
- Connection name - A descriptive name of your VPN connection, which you provided in the previous step and can be updated here.
- Address - The VPN device IP address.
- Address space - The IP address ranges to route through the VPN.
  - Press Enter after inputting a range to add another.
  - Click the X after a range to remove it.
- IP Security Policy - Adjust from the default values as required
The dialog box closes and you return to the Connections tab of the wizard. Click Continue.
The Confirmation tab summarizes your selection and the next steps. Click Save to create the infrastructure.

A new record appears below the Network Infrastructure heading in the side panel. It includes details such as the type of infrastructure, status, region, and the environments where it is enabled.

API Configuration

Once per program, the POST /program/<programId>/networkInfrastructures endpoint is invoked. It passes in a payload of configuration information. That information includes the value of vpn for the kind parameter, region, address space (list of CIDRs - note that this value cannot be modified later), DNS resolvers (for resolving names in your network). It also includes VPN connection information such as gateway configuration, shared VPN key, and the IP Security policy. The endpoint responds with the network_id, and other information including the status.

Once called, it typically takes from 45 to 60 minutes for the networking infrastructure to be provisioned. The GET method in the API can be called to return the status, which eventually flips from creating to ready. Consult the API documentation for all states.

TIP

The full set of parameters, exact syntax, and important information like what parameters cannot be changed later, can be referenced in the API documentation.

Traffic Routing

The table below describes traffic routing.

Traffic

Destination Condition

Port

Connection

External destination example

Http or https protocol

Traffic to Azure or Adobe services

Any

Through the shared cluster IPs (not the dedicated IP)

adobe.io
api.windows.net

Host matching the nonProxyHosts parameter

80 or 443

Through the shared cluster IPs

Host matching the nonProxyHosts parameter

Ports outside 80 or 443

Blocked

If the IP falls in the VPN gateway address space range, and through http proxy configuration (configured by default for http/s traffic using the standard Java™ HTTP client library)

Any

Through the VPN

10.0.0.1:443
It can be a hostname as well.

If the IP does not fall in the VPN gateway address space range, and through http proxy configuration (configured by default for http/s traffic using the standard Java™ HTTP client library)

Any

Through the dedicated egress IP

Ignores http proxy configuration (for example, if explicitly removed from the standard Java™ HTTP client library or if using a Java™ library that ignores standard proxy configuration)

80 or 443

Through the shared cluster IPs

Ignores http proxy configuration (for example, if explicitly removed from the standard Java™ HTTP client library or if using a Java™ library that ignores standard proxy configuration)

Ports outside 80 or 443

Blocked

Non-http or non-https

If the IP falls in the VPN gateway address space range and the client connects to AEM_PROXY_HOST env variable using a portOrig declared in the portForwards API parameter

Any

Through the VPN

10.0.0.1:3306
It can be a hostname as well.

If the IP does not fall in the VPN gateway address space range and client connects to AEM_PROXY_HOST env variable using a portOrig declared in the portForwards API parameter

Any

Through the dedicated egress IP

Anything else

Any

Blocked

Useful Domains for Configuration

The diagram below provides a visual representation of a set of domains and associated IPs that are useful for configuration and development. The table further below the diagram describes those domains and IPs.

VPN Domain Configuration

Domain pattern

Egress (from AEM) meaning

Ingress (to AEM) meaning

p{PROGRAM_ID}.external.adobeaemcloud.com

Dedicated egress IP address for traffic going to the Internet rather than through private networks

Connections from the VPN would show at the CDN as coming from this IP. To allow only connections from the VPN to go into AEM, configure Cloud Manager to allow only this IP and block everything else. See the "Restrict ingress to VPN connections" section for more details.

p{PROGRAM_ID}.{REGION}-gateway.external.adobeaemcloud.com

N/A

The IP of the VPN gateway on the AEM side. Your network engineering team can use this IP to allow only VPN connections to your VPN gateway from a specific IP address.

Enabling Advanced Networking Configurations on Environments

Once you have configured an advanced networking option for a program, whether flexible port egress, dedicated egress IP address, or VPN, to use it, you must enable it at the environment level.

When you enable an advanced networking configuration for an environment, you can also enable optional port forwarding and non-proxy hosts. Parameters are configurable per environment to offer flexibility.

Port Forwarding - Port forwarding rules should be declared for any destination ports other than 80/443, but only if not using the http or https protocol.
- Port forwarding rules are defined by specifying the set of destination hosts (names or IP and ports).
- The client connection that uses port 80/443 over http / https must still use proxy settings in their connection to have the properties of advanced networking applied to the connection.
- For each destination host, you must map the intended destination port to a port from 30000 through 30999.
- Port forwarding rules are available for all advanced networking types.
Non-Proxy Hosts - Non-proxy hosts let you declare a set of hosts that should route through a shared IPs address range rather than the dedicated IP.
- This approach may be useful since traffic egressing through shared IPs may be further optimized.
- Non-proxy hosts are only available for dedicated egress IP address and VPN advanced networking types.

NOTE

You cannot enable an advanced networking configuration for an environment if the environment is in the Updating status.

Enabling Using the UI

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
On the My Programs console, select the program.
From the Program Overview page, navigate to the Environments tab and select the environment where you want to enable the advanced networking configuration under the Environments heading in the left panel. Then select the Advanced network configuration tab of the selected environment and click Enable network infrastructure.
The Configure advanced networking dialog box opens.
On the Non-proxy hosts tab, for dedicated egress IP addresses and VPNs, you can optionally define a set of hosts. These defined hosts should be routed through a shared IPs address range rather than the dedicated IP, by providing the host name in the Non-Proxy Host field and clicking Add.
- The host is added to the list of hosts on the tab.
- Repeat this step if you want to add multiple hosts.
- Click the X to the right of the row if you wan to remove a host.
- This tab is not available for flexible port egress configurations.
On the Port forwards tab, you can optionally define port forwarding rules for any destination ports other than 80/443 if not using HTTP or HTTPS. Provide a Name, Port Orig, and Port Dest and click Add.
- The rule is added to the list of rules on the tab.
- Repeat this step if you want to add multiple rules.
- Click the X to the right of the row if you want to remove a rule.
Click Save in the dialog box so you can apply the configuration to the environment.

The advanced networking configuration is applied to the selected environment. Back on the Environments tab, you can see the details of the configuration applied to the selected environment and their status.

Environment configured with advanced networking

Enabling Using the API

To enable an advanced networking configuration for an environment, the PUT /program/<program_id>/environment/<environment_id>/advancedNetworking endpoint must be invoked per environment.

The API should respond in just a few seconds, indicating a status of updating. After about 10 minutes, a call to the Cloud Manager’s environment GET endpoint shows a status of ready, indicating that the update to the environment is applied.

Per environment port forwarding rules can be updated by invoking the PUT /program/{programId}/environment/{environmentId}/advancedNetworking endpoint, and including the full set of configuration parameters, rather than a subset.

Dedicated egress IP address and VPN advanced networking types support a nonProxyHosts parameter. This support lets you declare a set of hosts that should route through a shared IPs address range rather than the dedicated IP. The nonProxyHost URLs may follow the patterns of example.com or *.example.com, where the wildcard is only supported at the start of the domain.

Even if there are no environment traffic routing rules (hosts or bypasses), PUT /program/<program_id>/environment/<environment_id>/advancedNetworking must still be called, just with an empty payload.

TIP

The full set of parameters, exact syntax, and important information like what parameters cannot be changed later, can be referenced in the API documentation.

Editing and Deleting Advanced Networking Configurations on Environments

After enabling advanced networking configurations to environments, you can update the details of those configurations or delete them.

NOTE

You cannot edit network infrastructure if it has the status Creating, Updating, or Deleting.

Editing or Deleting using the UI

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
On the My Programs console, select the program.
From the Program Overview page, navigate to the Environments tab and select the environment where you want to enable the advanced networking configuration under the Environments heading in the left panel. Then select the Advanced network configuration tab of the selected environment and click the ellipsis button.
In the ellipsis menu, select either Edit or Delete.
- If you choose Edit, update the information per the steps described in the previous section, Enabling Using the UI, and click Save.
- If you choose Delete, confirm the deletion in the Delete network configuration dialog box with Delete or abort with Cancel.

The changes are reflected on the Environments tab.

Editing or Deleting using the API

To delete advanced networking for a particular environment, invoke DELETE [/program/{programId}/environment/{environmentId}/advancedNetworking]().

TIP

The full set of parameters, exact syntax, and important information like what parameters cannot be changed later, can be referenced in the API documentation.

Editing and Deleting a Program’s Network Infrastructure

Once network infrastructure is created for a program, only limited properties can be edited. If you no loner require it, you can delete the advanced networking infrastructure for your entire program.

NOTE

The following are limitations to editing and deleting network infrastructure:

Delete only deletes the infrastructure if all environments have their advanced networking disabled.
You cannot edit network infrastructure if it has the status Creating, Updating, or Deleting.
Only the VPN advanced networking infrastructure type can be edited once created and then only limited fields.
For security reasons, the Shared key must always be provided when editing an advanced VPN networking infrastructure, even if you are not editing the key itself.

Editing and Deleting with the UI

Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization
On the My Programs console, select the program.
From the Program Overview page, navigate to the Environments tab.
In the left panel, click Network Infrastructure.
Click next to the infrastructure that you want to delete.
Click either Edit or Delete.
Do one of the following:
- If you chose Edit, the Edit network infrastructure wizard opens. Edit as required following the steps as described when creating the infrastructure.
- If you chose Delete, confirm the deletion in the Delete network configuration dialog box with Delete or abort with Cancel.

The changes are reflected on the Environments tab.

Editing and Deleting with the API

To delete the network infrastructure for a program, invoke DELETE /program/{program ID}/networkinfrastructure/{networkinfrastructureID}.

Changing a Program’s Advanced Networking Infrastructure Type

It is only possible to have one type of advanced networking infrastructure configured for a program at a time. The advanced networking infrastructure must be either flexible port egress, dedicated egress IP address, or VPN.

If you decide that you need another advanced networking infrastructure type than the one you have already configured, delete the existing one, and create another one. Do the following:

Delete advanced networking in all environments.
Delete the advanced networking infrastructure.
Create the advanced networking infrastructure type you now require, either flexible port egress, dedicated egress IP address, or VPN.
Reenable advanced networking at the environment level.

WARNING

This procedure results in a downtime of advanced networking services between deletion and recreation.
If downtime would cause significant business impact, contact customer support for assistance, describing what has already been created and the reason for the change.

Advanced Networking Configuration for Other Publish Regions

When an additional region is added to an environment with advanced networking already configured, traffic from the additional publish region follows the existing rules. By default, matching traffic is routed through the primary region. However, if the primary region becomes unavailable, the advanced networking traffic is dropped if advanced networking hasn’t been enabled in the additional region. If you want to optimize latency and increase availability in case one of the regions undergoes an outage, it is necessary to enable advanced networking for the additional publish regions. Two different scenarios are described in the following sections.

NOTE

All regions share environment advanced networking configuration, so it is not possible to route traffic to different destinations based on the region the traffic is egressing out of.

Dedicated Egress IP Addresses

Advanced networking already enabled in the primary region

If an advanced networking configuration is already enabled in the primary region, follow these steps:

If you locked down your infrastructure such that the dedicated AEM IP address is allowlisted, temporarily disable any deny rules in that infrastructure. If you skip this step, your infrastructure temporarily denies requests from the new region’s IP addresses. This step is not necessary if you have locked down your infrastructure using a Fully Qualified Domain Name (FQDN), such as p1234.external.adobeaemcloud.com. All AEM regions egress advanced networking traffic from the same FQDN.
Create the program-scoped networking infrastructure for the secondary region through a POST call to the Cloud Manager Create Network Infrastructure API, as described in advanced networking documentation. The only difference in the payload’s JSON configuration relative to primary region is the region property
If you need to lock down your infrastructure by IP to allow AEM traffic, add the IPs that correspond to p1234.external.adobeaemcloud.com. There should be one per region.

Advanced networking not yet configured in any region

The procedure is mostly similar to the previous instructions. However, if the production environment has not yet been enabled for advanced networking, there is an opportunity to test the configuration by first enabling it in a staging environment:

Create networking infrastructure for all regions through a POST call to the Cloud Manager Create Network Infrastructure API. The only difference in the payload’s JSON configuration relative to the primary region is the region property.
For the staging environment, enable and configure the environment scoped advanced networking by running PUT api/program/{programId}/environment/{environmentId}/advancedNetworking. For more information, see the API documentation
If necessary, lock down external infrastructure, preferably by FQDN (for example, p1234.external.adobeaemcloud.com). You can otherwise do it by IP address
If the staging environment works as expected, enable and configure the environment-scoped advanced networking configuration for production.

VPN

The procedure is nearly identical to the dedicated egress IP addresses instructions. The only difference is that the region property is configured differently from the primary region. Additionally, you can optionally configure the connections.gateway field. The configuration can route to a different VPN endpoint operated by your organization, geographically closer to the new region.

Troubleshooting

Please be advised that the following points are provided as informative guidelines and encompass best practices for troubleshooting. These recommendations are intended to assist in effectively diagnosing and resolving issues.

Connection pooling

Connection pooling is a technique tailored to create and sustain a repository of connections, which stand ready for immediate use by any thread that may require them. Numerous connection pooling techniques can be found across various online platforms and resources, each with its unique merits and considerations. Adobe encourages customers to investigate these methodologies to identify the one most compatible with their system’s architecture.

Implementing an appropriate connection pooling strategy is a proactive measure to correct a common oversight in system configuration, which often leads to suboptimal performance. By correctly establishing a connection pool, Adobe Experience Manager (AEM) can improve the efficiency of external calls. This approach not only reduces resource consumption but also mitigates the risk of service disruptions and decreases the probability of encountering failed requests when communicating with upstream servers.

Based on this information, Adobe recommends reviewing your current AEM configuration. Also consider intentionally using connection pooling alongside your advanced networking settings. Managing the number of parallel connections and reducing stale connections helps optimize network performance. These actions lower the risk of proxy servers reaching their connection limits. Consequently, this strategic implementation is designed to decrease the likelihood of requests failing to reach external endpoints.

Connection Limits FAQ

When using advanced networking, the number of connections is limited to ensure stability across environments and to prevent lower environments from exhausting the available connections.

The connections are limited to 1000 per AEM instance and alerts are sent to customers when the number reaches 750.

Is the connection limit applied only to outbound traffic out of non-standard ports or to all outbound traffic?

The limit is only for connections using advanced networking (egress on non-standard ports, using dedicated egress IP, or VPN).

There doesn’t appear to be a significant increase in the number of outgoing connections. Why is the notification being received now?

If the customer creates connections dynamically (for example, one or more for each request), an increase in traffic can cause the connections to spike.

Could a similar situation have occurred in the past without triggering an alert?

Alerts are only sent when the soft limit is reached.

What happens if the maximum limit is reached?

When the hard limit is reached, new egress connections from AEM through advanced networking (egress on non-standard ports, using dedicated egress IP, or VPN) is dropped to protect against a DoS attack.

Can the limit be raised?

No, having a large number of connections can cause a significant performance impact and a DoS across pods and environments.

Are the connections automatically closed by the AEM system after a certain period?

Yes, connections are closed at the JVM level and at different points in the networking infrastructure. However, this workflow is too late for any production service. Connections should be explicitly closed when no longer needed or returned to the pool when using connection pooling. Otherwise, the resource consumption is too high and can cause exhaustion of resources.

If the maximum connection limit is reached, does it affect any licenses and result in extra costs?

No, there is no license or cost associated with this limit. It is a technical limit.

How close is the current usage to the limit? What is the maximum allowed limit?

The alert is triggered when connections exceed 750. The maximum limit is 1000 connections per AEM instance.

Is this limit applicable to VPNs?

Yes, the limit applies to connections using advanced networking, including VPNs.

Does the limit still apply when using a Dedicated Egress IP?

Yes, the limit is still applicable if using a dedicated egress IP.

recommendation-more-help