Configuring Advanced Networking for AEM as a Cloud Service configuring-advanced-networking
This article introduces the different advanced networking features in AEM as a Cloud Service, including self-service and API provisioning of VPN, non-standard ports, and dedicated egress IP addresses.
Overview 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.
Requirements and Limitations requirements
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 in 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 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 configuring-enabling
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
/networkInfrastructuresAPI endpoint is invoked at the program level to declare the desired type of advanced networking. It is followed by a call to the/advancedNetworkingendpoint for each environment to enable the infrastructure and configure environment-specific parameters.
Flexible Port Egress 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.
UI Configuration configuring-flexible-port-egress-provision-ui
-
Log into Cloud Manager at 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 and the region where it should be created from the Region drop-down menu and 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 including details of the type of infrastructure, status, region, and environments on which it has been enabled.
API Configuration configuring-flexible-port-egress-provision-api
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 would show a status of ready.
Traffic Routing flexible-port-egress-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 toproxy.tunnel:3128in AEM releases < 6094) - for HTTPS:
AEM_PROXY_HOST/AEM_HTTPS_PROXY_PORT(default toproxy.tunnel:3128in 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:
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)
AEM_PROXY_HOST environment variable using a portOrig declared in the portForwards API parameter.mysql.example.com:3306db.example.com:5555Apache / Dispatcher Configuration apache-dispatcher
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 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 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 coming out of AEM as a Cloud Service flows through a set of IPs shared with other customers of AEM as a Cloud Service.
Configuring 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.
UI Configuration configuring-dedicated-egress-provision-ui
-
Log into Cloud Manager at 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 Dedicated egress IP address and the region where it should be created from the Region drop-down menu and 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 including details of the type of infrastructure, status, region, and environments on which it has been enabled.
API Configuration configuring-dedicated-egress-provision-api
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 would show a status of ready.
Traffic Routing dedicated-egress-ip-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");
api.windows.net
nonProxyHosts parameternonProxyHosts parameterAEM_PROXY_HOST env variable using a portOrig declared in the portForwards API parametermysql.example.com:3306Feature Usage 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 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
or use
:
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 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 , which returns the calling IP address.
Virtual Private Network (VPN) vpn
A VPN allows connecting to an on-premise infrastructure or data center from the author, publish, or preview instances. This 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 Configure the device as described in the table.
- 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 configuring-vpn-ui
-
Log into Cloud Manager at 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 - This is the region in which 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 - This is a list of remote DNS resolvers.
- Press
Enterafter inputting a DNS server address to add another. - Click the
Xafter an address to remove it.
- Press
-
Shared Key - This is 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, define your VPN connection, then click Save.
-
Connection name - This is a descriptive name of your VPN connection, which you provided in the previous step and can be updated here.
-
Address - This is the VPN device IP address.
-
Address space - These are the IP address ranges to route through the VPN.
- Press
Enterafter inputting a range to add another. - Click the
Xafter a range to remove it.
- Press
-
IP Security Policy - Adjust from the default values as required
-
-
The dialog 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 including details of the type of infrastructure, status, region, and environments on which it has been enabled.
API Configuration configuring-vpn-api
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 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 through 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.
Traffic Routing vpn-traffic-routing
The table below describes traffic routing.
api.windows.net
nonProxyHosts parameternonProxyHosts parameter10.0.0.1:443It can be a hostname as well.
AEM_PROXY_HOST env variable using a portOrig declared in the portForwards API parameter10.0.0.1:3306It can be a hostname as well.
AEM_PROXY_HOST env variable using a portOrig declared in the portForwards API parameterUseful Domains for Configuration vpn-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.
p{PROGRAM_ID}.external.adobeaemcloud.comp{PROGRAM_ID}.{REGION}-gateway.external.adobeaemcloud.comEnabling Advanced Networking Configurations on Environments enabling
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 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 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.
Enabling Using the UI enabling-ui
-
Log into Cloud Manager at 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 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.
Enabling Using the API enabling-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 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.
Editing and Deleting Advanced Networking Configurations on Environments editing-deleting-environments
After enabling advanced networking configurations to environments, you can update the details of those configurations or delete them.
Editing or Deleting using the UI editing-ui
-
Log into Cloud Manager at 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 with Delete or abort with Cancel.
The changes are reflected on the Environments tab.
Editing or Deleting using the API editing-api
To delete advanced networking for a particular environment, invoke DELETE [/program/{programId}/environment/{environmentId}/advancedNetworking]().
Editing and Deleting a Program’s Network Infrastructure editing-deleting-program
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.
- 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 delete-ui
-
Log into Cloud Manager at 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 heading in the left panel. Then click the ellipsis button next to the infrastructure that you want to delete.
-
In the ellipsis menu, select either Edit or Delete.
-
If you choose Edit, the Edit network infrastructure wizard opens. Edit as required following the steps as described when creating the infrastructure.
-
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 and Deleting with the API delete-api
To delete the network infrastructure for a program, invoke DELETE /program/{program ID}/networkinfrastructure/{networkinfrastructureID}.
Changing a Program’s Advanced Networking Infrastructure Type changing-program
It is only possible to have one type of advanced networking infrastructure configured for a program at a time, The advanced networking infrastructure must 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.
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 advanced-networking-configuration-for-additional-publish-regions
When an additional region is added to an environment that already has advanced networking configured, traffic from the additional publish region that matches the advanced networking rules route through the primary region by default. 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.
Dedicated Egress IP Addresses additional-publish-regions-dedicated-egress
Advanced networking already enabled in the primary region already-enabled
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 this is not done, there is a short period where requests from the new region’s IP addresses are denied by your own infrastructure. This is not necessary if you have locked down your infrastructure by way of a FullyQualified Domain Name (FQDN), (
p1234.external.adobeaemcloud.com, for example), because 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 your infrastructure must be locked down by IP to allow AEM traffic, add the IPs that match
p1234.external.adobeaemcloud.com. There should be one per region.
Advanced networking not yet configured in any region not-yet-configured
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 POST call to the . The only difference in the payload’s JSON configuration relative to 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 - 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 vpn-regions
The procedure is nearly identical to the dedicated egress IP addresses instructions. The only difference is that in addition to the region property being configured differently from the primary region, the connections.gateway field can optionally be configured. 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-advanced-networking
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. We encourage our 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, ÃÛ¶¹ÊÓƵ Experience Manager (AEM) can improve the efficiency of external calls. This 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.
In light of this information, ÃÛ¶¹ÊÓƵ advises reassessing your current AEM configuration and consider the deliberate incorporation of connection pooling in conjunction with Advanced Networking settings. By managing the number of parallel connections and minimizing the possibility of stale connections, these measures lead to a reduction in 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 in order to ensure stability across environments and to prevent that 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).
We do not see a significant difference in the number of outgoing connections. Why are we receiving the notification 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.
Is it possible that we experienced a similar situation in the past without being alerted?
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) will be 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 different points in the networking infrastructure. However, this will be 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 will be 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 are we to the limit? What is the maximum 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.
If we use a Dedicated Egress IP, will this limit still be applicable?
Yes, the limit is still applicable if using a dedicated egress IP.