Hi @AndZyk ,
Thank you for reaching out. We understand how important it is to have the correct network configuration in place, especially when your team relies on Adobe Stock in Photoshop for daily work.
We do not recommend using IP addresses to allow or block access to Adobe services. Our services are hosted across multiple servers and regions, and IP addresses can change frequently, sometimes within hours.
They also vary by geographic location, so an IP-based setup that works today may stop working without notice. This is outlined on our Network Endpoints helpx page.
Instead, we recommend that your IT provider allowlists the following domains over port 443 to enable Adobe Stock in Photoshop:
Adobe Stock services:
- stock.adobe.com
- stock.adobe.io
- *.astockcdn.net
- slp-statics.astockcdn.net
- *.ftcdn.net (includes as.ftcdn.net, as1.ftcdn.net, as2.ftcdn.net, t3.ftcdn.net, t4.ftcdn.net, s.ftcdn.net, v.ftcdn.net)
- firefly-st.adobe.io (for AI-powered Stock features)
Authentication (also required):
- ims-na1.adobelogin.com
- adobeid-na1.services.adobe.com
- auth.services.adobe.com
General Creative Cloud services (Photoshop dependencies):
- cc-api-assets.adobe.io
- cc-api-storage.adobe.io
- assets.adobe.com
- *.adobecc.com
- *.adobecces.com
Before applying these changes, please note the following:
-
Your network proxy must support Secure WebSocket (WSS) over HTTPS and allow headers prefixed with Sec-WebSocket*, which are required for adobe.io connections.
-
Our endpoint list is updated regularly. A downloadable allowlist file with a timestamp is available on the Network Endpoints page. We recommend saving it and checking for updates whenever the “Last updated” date changes.
-
If your organization maintains its own certificate store, please ensure it is updated with the latest Amazon Root CAs (https://www.amazontrust.com/repository/), as some of our services are hosted on AWS infrastructure.
-
As a best practice, validate the configuration with a small group of users first to confirm that Stock previews, licensing, and downloads work as expected before rolling it out broadly.
If your IT provider prefers a simpler approach, the Network Endpoints page also includes top-level wildcard domains (such as *.adobe.com, *.adobe.io, *.ftcdn.net, and others)that cover most Adobe services in a single step.
If you experience any issues after applying these changes, please feel free to follow up here or share additional details so we can assist with troubleshooting. For the most current and complete list of required domains, please refer to Network Endpoints helpx document.
We hope this helps, and we’re happy to assist further if needed. And thank you for taking the time to get this right for your organization.
Thanks,
^BS
AdChoices