Skip to main content
The cloud license runs EKB as a managed service hosted by Automation Anywhere. You subscribe, create projects, and use the product through the standard web experience—without operating the underlying infrastructure yourself.

​
Who cloud is for

Organizations that want to go live quickly, stay on continuously updated releases, and prefer Automation Anywhere to run and scale the platform in our secure cloud environment.

​
What you get (at a glance)

  • Fast onboarding — Sign in, create a project, and start with chat, knowledge base, agents, and workflows.
  • Managed operations — Patching, scaling, and service reliability handled by Automation Anywhere.
  • Enterprise security & compliance — See Security & Compliance for certifications and practices.

​
Regional hosting and static egress IP addresses

EKB cloud is hosted across four AWS regions. Use the frontend and app server URLs for the region where your tenant runs when your IT team configures HTTPS (port 443) allowlists or proxy exceptions. If your organization must allowlist traffic that EKB sends to your own systems (integrations, webhooks, private APIs, etc.), add the static egress IP for that region as a single host (typically /32 in CIDR notation)—or all four if you are unsure which region applies.

​
Summary (regions and egress IPs)

RegionAWS region & locationStatic egress IP (allowlist)
USUnited States — US East (N. Virginia) (us-east-1)13.248.244.227
EUEurope — London (eu-west-2)18.170.141.39
INIndia — Mumbai (ap-south-1)52.66.79.101
AUSAustralia — Sydney (ap-southeast-2)13.210.60.153

​
Frontend and app server URLs

Open a region to see the HTTPS endpoints for allowlists and proxy rules.

​
How to check that it works

  • People using EKB: Open EKB from a regular work computer, sign in, and try something normal (for example Chat or opening a project). If everything loads and responds, your network can reach EKB. If not, ask IT to allow HTTPS to the frontend and app server URLs for your region (see Frontend and app server URLs above).
  • EKB reaching your systems: After your team adds the static IPs above, run a small real test from EKB (such as an integration or connector you rely on). If it works, the allowlist is doing its job. Your IT or security team can double-check using their usual firewall or server logs if needed.
Simple ping tests are usually not a good check here—many companies block ping even when normal web traffic is fine. If something still does not work after IT updates the rules, contact support@automationanywhere.com with your company name and EKB link.