> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/reference-documentation/networking/third-party-services.md).

# Third-party services

When you host your software with Release, you can continue to integrate with third-party services as you usually would. In some cases, third-party services might ask you to allowlist (or whitelist) the IP addresses that your software will call out to their software from. Because Release automatically creates clusters and other networking infrastructure in your cloud account, you need to know how to find your main egress IP address.

You might need this to integrate with external services, including but not limited to the following:

* SendGrid
* Stripe
* Twilio
* Salesforce
* Office 365

## Finding your outgoing IP for AWS

When you create a cluster with Release and AWS, Release automatically sets up Kubernetes using EKS and a **NAT gateway**. A NAT gateway is the primary gate between the outside world and your clusters, so external requests from your software will appear to originate from this gateway.

To find your NAT gateway address, follow these steps (if you have Release clusters in multiple regions, repeat the steps for each region):

1. Log in to your AWS account.
2. Select the region your Release cluster runs in.
3. Navigate to the **VPC dashboard**.
4. Select **NAT gateways** on the left sidebar.
5. Identify the NAT gateway associated with your Release cluster and look for "Elastic IP Address".

This is the IP address you send to any third-party providers that need to allowlist your IP ranges.

![Get NAT IP address](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-c19e0e5b666b2b718d5e945a8be8f0d24ebec091%2Fnetworking-get-nat-ip.png?alt=media\&token=35d3dcfa-5b1a-42ef-b3e8-5e96831a7c06)

You can read more about how NAT gateways work in AWS [in their docs](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html).


---

# 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.release.com/reference-documentation/networking/third-party-services.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.