> ## Documentation Index
> Fetch the complete documentation index at: https://ai-kb.automationanywhere.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> EKB cloud overview—AWS regions, static egress IPs, and frontend and app server URLs for firewall and proxy allowlists.

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](/general/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)

| Region  | AWS region & location                               | Static egress IP (allowlist) |
| :------ | :-------------------------------------------------- | :--------------------------- |
| **US**  | United States — US East (N. Virginia) (`us-east-1`) | `13.248.244.227`             |
| **EU**  | Europe — London (`eu-west-2`)                       | `18.170.141.39`              |
| **IN**  | India — Mumbai (`ap-south-1`)                       | `52.66.79.101`               |
| **AUS** | Australia — 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.

<AccordionGroup>
  <Accordion title="US — US East / N. Virginia (us-east-1)">
    * **Static egress IP:** `13.248.244.227`
    * **Frontend (web app):** [https://ai.automationanywhere.com](https://ai.automationanywhere.com)
    * **App server (API):** [https://ai-api.automationanywhere.com](https://ai-api.automationanywhere.com)
  </Accordion>

  <Accordion title="EU — London (eu-west-2)">
    * **Static egress IP:** `18.170.141.39`
    * **Frontend (web app):** [https://ai-eu.automationanywhere.com](https://ai-eu.automationanywhere.com)
    * **App server (API):** [https://ai-eu.automationanywhere.com/backend](https://ai-eu.automationanywhere.com/backend)
  </Accordion>

  <Accordion title="IN — Mumbai (ap-south-1)">
    * **Static egress IP:** `52.66.79.101`
    * **Frontend (web app):** [https://ai-in.automationanywhere.com](https://ai-in.automationanywhere.com)
    * **App server (API):** [https://ai-in.automationanywhere.com/backend](https://ai-in.automationanywhere.com/backend)
  </Accordion>

  <Accordion title="AUS — Sydney (ap-southeast-2)">
    * **Static egress IP:** `13.210.60.153`
    * **Frontend (web app):** [https://ai-au.automationanywhere.com](https://ai-au.automationanywhere.com)
    * **App server (API):** [https://ai-au.automationanywhere.com/backend](https://ai-au.automationanywhere.com/backend)
  </Accordion>
</AccordionGroup>

### 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](mailto:support@automationanywhere.com) with your company name and EKB link.