> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/cloud-application/network-security-consideration.md).

# Network Security Considerations

Which AWS regions and CIDR ranges ENERCALC's cloud EC2 instances use for configuring your security systems.

## What are ENERCALC's cloud IP addresses for use in our security systems?

We don't have a list of fixed IP address ranges for cloud instances (which are AWS EC2 instances). Fortunately, AWS publishes a list of CIDR ranges for each region and service.

We use Dizzion Frame (formerly Nutanix Frame) as our desktop as a service platform, but using their domains/IP range is probably not ideal. The AWS instances that users log into when accessing our cloud apps are on our AWS account. These IP address ranges are visible in several ways, including via [https://ip-ranges.amazonaws.com/ip-`ranges.json`](https://ip-ranges.amazonaws.com/ip-ranges.json)

​

If you query that json using "us-east-1", "us-east-2", "us-west-1", "us-west-2", the story from AWS is that you'll find a CIDR that matches the IPs our EC2 instances will use. You can filter the list down by looking only for entries with Service : EC2.

Our cloud service uses EC2 instances in these US-based regions: us-east-1 (Virginia), us-west-1 (California), us-west-2 (Oregon), us-east-2 (Ohio). If your use extends outside the US, we also use AWS Frankfurt, Mumbai, and Tokyo. All data is stored in AWS US data centers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://enercalc.com/docs/sel-faq/using-the-software/cloud-application/network-security-consideration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
