> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/connectors-and-secrets/manage-connectors/connector-ip-allowlist.md).

# Connector IP Allowlist

Configure outbound access to ensure communication with Apono

If your organization restricts outbound network access by IP address or port, you must configure your IP allowlist to enable uninterrupted communication between Apono connectors and the Apono cloud infrastructure.

An IP allowlist defines which destination IP addresses your network permits outbound traffic to reach.

{% hint style="info" %}
Configuring an IP allowlist is not required if either of the following use cases applies to your organization:

* Uses **domain-based allowlists**, with entries such as *api.apono.io* and *registry.apono.io*
* Allows **unrestricted outbound HTTPS traffic**
  {% endhint %}

***

### Network Access Requirements

To ensure consistent and reliable connector performance, the following endpoints and ports must be accessible from your environment.

{% hint style="danger" %}
All network configurations must comply with these requirements by **31 October 2025** to prevent disruption in connector functionality.
{% endhint %}

<table><thead><tr><th width="149.35546875">Domain</th><th width="279.3828125">Connection Details</th><th>Destination IP Addresses</th></tr></thead><tbody><tr><td>api.apono.io</td><td><ul><li><strong>Protocol</strong>: HTTPS</li><li><strong>Port</strong>: 443</li><li><strong>Source Port Range</strong>: 32768–60999</li></ul></td><td><ul><li>54.157.3.253</li><li>34.225.239.246</li><li>44.205.140.99</li><li>98.90.221.221 (New)</li><li>98.89.52.211 (New)</li><li>34.192.189.115 (New)</li></ul></td></tr><tr><td>registry.apono.io</td><td><ul><li><strong>Protocol</strong>: HTTPS</li><li><strong>Port</strong>: 443</li><li><strong>Source Port Range</strong>: 32768–60999</li></ul></td><td><ul><li>107.22.56.232</li><li>98.83.51.175</li><li>3.221.81.104</li><li>35.172.125.116 (New)</li><li>54.90.163.79 (New)</li><li>107.21.204.50 (New)</li></ul></td></tr></tbody></table>

***

### Support

For implementation support or questions regarding these requirements, contact **<support@apono.io>**.


---

# 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://docs.apono.io/docs/connectors-and-secrets/manage-connectors/connector-ip-allowlist.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.