Network infrastructure exception when creating dedicated egress IP in AEMaaCS
You might encounter a failure when creating a dedicated egress IP in Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites due to a missing primary region parameter. The API returns a 400 error with a Primary region invalid message. Adding the correct parameter resolves the issue. To resolve the issue, include the primary region parameter in the request.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
Issue/Symptoms
When trying to create a dedicated egress IP using the Cloud Manager API, the following error is returned:
- Status code: 400
- Error type: Network infrastructure exception
- Error message: Primary region invalid
Resolution resolution
Follow these steps to resolve the issue:
- Verify that the server instance is located in the intended region.
- Ensure you have valid OAuth Server-to-Server credentials created via AEM App Builder.
- Ensure all required parameters are included in the API request.
- Add the parameter
isPrimaryRegion: trueto the API request for primary region setup. - Run the updated API request and check the response.
- Confirm that the dedicated egress IP is successfully created and added to the environment.
If the issue continues, check for server-side errors or contact Adobe Support.
Related reading
- Dedicated egress IP address in the AEM as a Cloud Service Tutorials
- Outbound API calls use inconsistent IPs in the AEMaaCS
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f