Question
bcmglobal
IN
Last activity: 2 Oct 2025 22:45 EDT
On-Prem upgrade from 8.8.5 to 24.2. windows+tomcat+sql server
Hi All,
we are trying to upgrade our application from 8.8.5 to 24.2. Platform ,FW and Kafka configurations are done. we are trying to configure Search Service (using open search).
due to few restrictions on our client side, Infra team cannot give us open internet connectivity on the windows server we are trying to configure search service. we need to know the URLs needed for whitelisting to get the files from repositories SRS and Open Search
Pegasystems Inc.
GB
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
To configure the Search Service with OpenSearch for your Pega Platform 24.2 upgrade, especially with network restrictions, you'll need to whitelist specific URLs so your server can access the required files.
Based on Pega's documentation and common configurations, here are the URLs your infrastructure team will likely need to whitelist.
Required URLs for Whitelisting
For the installation and configuration of the Search and Reporting Service (SRS) and OpenSearch, your server will need access to two main sources: the official OpenSearch repository to get the search engine itself, and Pega's repositories for the SRS components and other static content.
OpenSearch Repository
Your server needs to download the OpenSearch distribution. These files are hosted on the official OpenSearch website.
| Service | URL | Purpose |
|---|---|---|
| OpenSearch | https://opensearch.org/ |
The primary source for downloading the OpenSearch distribution, plugins, and related tools. |
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
To configure the Search Service with OpenSearch for your Pega Platform 24.2 upgrade, especially with network restrictions, you'll need to whitelist specific URLs so your server can access the required files.
Based on Pega's documentation and common configurations, here are the URLs your infrastructure team will likely need to whitelist.
Required URLs for Whitelisting
For the installation and configuration of the Search and Reporting Service (SRS) and OpenSearch, your server will need access to two main sources: the official OpenSearch repository to get the search engine itself, and Pega's repositories for the SRS components and other static content.
OpenSearch Repository
Your server needs to download the OpenSearch distribution. These files are hosted on the official OpenSearch website.
| Service | URL | Purpose |
|---|---|---|
| OpenSearch | https://opensearch.org/ |
The primary source for downloading the OpenSearch distribution, plugins, and related tools. |
Pega Repositories
Pega hosts its own components, like the SRS Docker image and static content for the Constellation UI, in dedicated repositories.
| Service | URL | Purpose |
|---|---|---|
| Pega Docker Registry | docker.pega.com |
Pega uses a dedicated Docker registry for its images. You will need to pull the Search and Reporting Service image (platform-services/search-n-reporting-service) from here.
|
| Pega Static Content | https://release.constellation.pega.io/common |
This is Pega's Content Delivery Network (CDN) for common static resources used by the Constellation architecture in version 24.2.
|
Important Recommendation
While the URLs listed above are based on official Pega documentation, it is highly recommended to contact Pega Support to get a definitive and complete list tailored to your specific environment and licensing.
Here are some useful links to get you started:
- [External Search in your deployment](https://docs.pega.com/bundle/platform/page/platform/deployment/externalization-of-services/externalize-search-in-your-deployment.html)
- [Third-party externalized services FAQs](https://docs.pega.com/bundle/platform/page/platform/deployment/client-managed-cloud/third-party-externalized-services-faqs.html)
- https://docs.pega.com/bundle/platform/page/platform/deployment/external…
HCA Healthcare
US
don’t give that Windows server broad internet—stage the bits internally. For OpenSearch, allow just opensearch.org and artifacts.opensearch.org to download the Windows ZIP, or download on a jump box and copy it in; the official Windows install doc points to those artifacts. For Pega SRS, Pega distributes only container images; the standard pattern is pull the SRS image on a machine that has internet, push it to your private registry, and point Pega to that internal registry. Pega’s docs and Helm pages describe this flow and the SRS images (including the “-os” variant for OpenSearch). If your security team insists on allowlisting, the minimum external domains typically needed are: gcr.io (or your vendor-specific registry host used by Pega’s images), pegasystems.github.io and github.com (Helm charts, examples), plus opensearch.org and artifacts.opensearch.org (OpenSearch binaries). Net-net: preferred approach is zero external egress—mirror SRS images to your internal registry and copy the OpenSearch ZIP internally—then configure Pega’s SRS endpoint to that internal OpenSearch and your mirrored SRS image.