# Ensure there are no unused Elastic IP

- Source: https://support.icompaas.com/support/solutions/articles/a_17860230047959-ensure-there-are-no-unused-elastic-ip
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Utho Cloud](https://support.icompaas.com/support/solutions/c_1786022244474917) › [Utho Checks](https://support.icompaas.com/support/solutions/folders/utho-checks)
- Last updated: 2026-08-13
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

Elastic IPs are static public IP addresses that can be associated with cloud resources. An unused Elastic IP is a public IP address that is allocated but not currently associated with a required cloud resource. Unused Elastic IPs should be identified and released to avoid unnecessary resource usage and management overhead.

Rationale:

Regularly reviewing Elastic IPs helps identify public IP addresses that are no longer required. Releasing unused Elastic IPs keeps the environment clean and prevents unnecessary allocation of public IP resources.

Impact:

-   Releasing an Elastic IP permanently removes that IP allocation from the account.
    
-   Any application or resource still depending on the Elastic IP may lose connectivity.
    
-   Verify that the Elastic IP is not required before releasing it.
    

Default Value:

Elastic IPs can be allocated and associated with cloud resources in Utho. An Elastic IP remains allocated until it is released, even if it is no longer associated with a resource.

Pre-requisites:

-   A Utho account with permission to manage Elastic IPs.
    
-   Access to the Utho Console.
    
-   Permission to view, associate, disassociate, and release Elastic IPs.
    
-   Knowledge of which Elastic IPs are required by applications or cloud resources.
    

Remediation

Test Plan:

Using the Utho Console

1.  Sign in to the Utho Console using an account with appropriate permissions.
    
2.  Navigate to Network → Elastic IP.
    
3.  Review the list of allocated Elastic IPs.
    
4.  Review the Status or association information for each Elastic IP.
    
5.  Identify Elastic IPs that are not associated with any cloud resource.
    
6.  Verify that each unassociated Elastic IP is not required by any application or service.
    

7.  If an unused Elastic IP is found, follow the Implementation Steps to remediate the issue.
    

Using the Utho API

Retrieve the list of Elastic IPs using the Utho API.

  

curl -s \\

\-H "Authorization: Bearer $UTHO\_API\_TOKEN" \\

https://api.utho.com/v2/elastic-ip

  

Review the returned Elastic IP information and identify IPs that are not associated with any cloud resource.

Implementation Steps:

Using the Utho Console

1.  Sign in to the Utho Console using an account with appropriate permissions.
    
2.  Navigate to Network →VPC under select Elastic IP.
    

3.  Locate the Elastic IP that is not associated with any cloud resource.
    
4.  Verify that the Elastic IP is no longer required.
    
5.  Select the unused Elastic IP.
    

6.  Click Deallocate.
    

Using the Utho API

Use the Utho API to retrieve the Elastic IP and confirm that it is not associated with a cloud resource.

  

curl -s \\

\-H "Authorization: Bearer $UTHO\_API\_TOKEN" \\

https://api.utho.com/v2/elastic-ip/<elastic-ip-id\>

  

Release the unused Elastic IP using the documented Utho API release/delete operation.

  

curl -X DELETE \\

\-H "Authorization: Bearer $UTHO\_API\_TOKEN" \\

https://api.utho.com/v2/elastic-ip/<elastic-ip-id\>

  

Verify that the unused Elastic IP is no longer allocated.

Backout Plan:

1.  Sign in to the Utho Console using an account with appropriate permissions.
    
2.  Navigate to Network → Elastic IP.
    
3.  If the Elastic IP was released accidentally, verify whether the same IP address is still available for allocation.
    
4.  Allocate a new Elastic IP if the previous address is no longer available.
    
5.  Associate the Elastic IP with the required cloud resource.
    
6.  Update any application or DNS configuration that depends on the IP address.
    
7.  Verify that the required application or service is accessible.
    

Note: A released Elastic IP may not be recoverable. If the original IP is no longer available, a new Elastic IP must be allocated.

References:

-   [Utho Documentation](https://utho.com/docs/)
    
-   [Utho REST API Documentation](https://utho.com/rest-api/)
    
-   [Utho API](https://utho.com/api/)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.