---
title: "Optionally Obtaining an Elastic IP Address for the CTERA Portal Instance"
slug: "optionally-obtaining-an-elastic-ip-address-for-the-ctera-portal-instance-4"
tags: ["8.2", "Portal"]
updated: 2025-06-29T06:03:14Z
published: 2025-06-29T06:03:14Z
canonical: "kb.ctera.com/optionally-obtaining-an-elastic-ip-address-for-the-ctera-portal-instance-4"
---

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

# Optionally Obtaining an Elastic IP Address for the CTERA Portal Instance

Before changing the elastic IP address for the portal server instance you must wait until all the portal services, such as Nomad and Consul, have loaded. Loading the portal services take at least 5 minutes.

If you changed the elastic IP address after the installation but before the full deployment of portal services like Nomad and Consul, run `portal-manage.sh resetdb` **before** initializing the portal or joining it to an existing portal cluster.

**To obtain an elastic IP address for the instance:**

1. In the AWS Management Console select **Services**.
2. Under **Compute**, select **EC2**.
3. In the navigation pane, click **Network & Security > Elastic IPs**.  

The **Elastic IPs** screen is displayed.
4. Click **Allocate new address**.  

The **Allocate new address** window is displayed.
5. Click **Allocate**.  

An elastic IP address is displayed.
6. Click the new IP address and under **Actions** click **Associate address**.  

The **Associate address** screen is displayed.
7. Select your CTERA Portal instance, to associate the elastic IP address with the instance and the **Private IP**.
8. Click **Associate**.
9. Verify that you assigned the elastic IP address successfully, by browsing to your CTERA Portal instance at `https://ElasticIPAddress/admin`  

Where *ElasticIPAddress* is the elastic IP address you assigned to the CTERA Portal instance.