I need to ensure traffic from the it.tests and ui.tests are routed through known IPs. Is it possible to apply the same network configuration AEM instances use for egress traffic to pipelines?
Failing that, presume either the next best option is to whitelist all known IPs (is there a list of them) used by the pipelines, or setup our own proxy and apply it to the pipeline.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hello @raininglemons
As per analysis, you can Integrating these configurations with your pipeline depends on the pipeline tool you're using. If you're using a CI/CD tool like Jenkins, you can execute scripts or commands to apply these configurations as part of your pipeline workflow.
Also, you can set up a proxy server and routing all traffic from your pipelines through it is another option. You can then configure the proxy to allow traffic only to specific IP addresses
Best,
Venkat
Views
Replies
Total Likes
Hi,
Thanks for the reply, but I'm using the Adobe pipelines, so configuring the pipeline is outside my control.
Views
Replies
Total Likes
Hi @raininglemons ,
Routing egress traffic from AEM as a Cloud Service (AEMaaCS) pipelines through the same advanced network configuration used by AEM instances is not directly supported out of the box. AEMaaCS pipelines are designed to run in a CI/CD environment, which may not support the same network configurations as the managed AEM instances.
However, you have a few alternative approaches to manage and secure egress traffic from your AEMaaCS pipelines:
Adobe does not typically provide a fixed list of IP addresses for their cloud services due to the dynamic nature of cloud environments. However, you can:
This approach involves setting up your own proxy server and configuring your AEMaaCS pipelines to route their traffic through this proxy. Here’s a high-level overview of how to achieve this:
Set Up a Proxy Server:
Configure Proxy Server:
Update Pipeline Configuration:
pipeline:
environmentVariables:
HTTP_PROXY: http://your-proxy-server:port
HTTPS_PROXY: http://your-proxy-server:port
If your organization has advanced networking configurations set up with Adobe, you might be able to leverage these for your pipelines as well. This would typically involve:
While AEMaaCS pipelines do not natively support routing egress traffic through the same advanced network configuration as AEM instances, you can achieve controlled and secure egress traffic through:
Setting up a proxy server and configuring your pipelines to use it is often the most flexible and secure approach, allowing you to control and monitor all egress traffic effectively.
Views
Replies
Total Likes
Thanks ChatGPT, I've been following you, and this is considered spamming, I am reporting you.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies