Clusters terminating with error AWS_INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET_FAILURE (CLIENT_ERROR)

Increase the size of your subnet to allow for more IP addresses or free up some of the IP addresses currently in use.

Written by Gihyeon Lee

Last published at: September 27th, 2024

Problem 

When submitting jobs, you encounter an error stating you do not have enough free addresses in your AWS subnet, preventing you from provisioning all-purpose or job clusters. 

run failed with error message Cluster '<cluster-id>' was terminated. Reason: AWS_INSUFFICIENT_FREE_ADDRESSES_IN_SUBNET_FAILURE (CLIENT_ERROR). Parameters: aws_api_error_code:InvalidParameterValue, aws_error_message:Not enough free addresses in subnet <subnet-name>.

Cause

The AWS subnet that the Compute Plane wants to use is too small to accommodate the required IP addresses, or the existing IP addresses are fully utilized. This affects all-purpose and job clusters as well as SQL Warehouse compute.

Solution

Either increase the size of your subnet to allow for more IP addresses or free up some of the IP addresses currently in use.

To increase the size of your AWS subnet, update the CIDR block associated with the subnet. For more information, please refer to the Updating CIDRs section of the Configure a customer-managed VPC documentation.

To free up some of the IP addresses currently in use, terminate unused instances or reconfigure existing resources to use fewer instances (IP addresses).