BYOIP for IPv4 and Public IPv6 address ranges are beta features that are available for evaluation and testing purposes to select customers. Access is restricted to allowlisted accounts.

Creating public address ranges

You can create a public address range by defining its size and optionally, specifying a VPC to associate with it in any availability zone within the account. Addresses can be allocated from IBM-managed IP pools or from a custom authorized CIDR if you want to use your own publicly routable IP range.You can also create public IPv6 address ranges from an IBM-provided IPv6 authorized CIDR and bind them to a VNI. For IPv6 instructions, see Creating IPv6 public address ranges and binding to a VNI.

If the VPC is deleted while it is bound to a public address range, the address range continues to exist and can be bound later to a different VPC in any availability zone.

You can create public address ranges with the console, CLI, API, and Terraform.

Before you begin

Make sure to review planning considerations for public address ranges.

Creating public address ranges in the console

To create public address ranges in the IBM Cloud console, follow these steps:

From the IBM Cloud console, select the Navigation menu , then click Infrastructure > Network > Public address ranges. The Public address ranges for VPC page is displayed.
Click Create to go to the provisioning page.
In the Location section, indicate the region where you want the public address range created.
In the Details section, complete the following information:
- Size: Select the size (number of IPs) of the address range. You can choose from 1, 2, 4, 8, or 16 IPs to include in the block.
  
  After you create a public address range, you can't change its size.
- Name: Optional: Enter a name for the public address range, such as my-public-address-range.
- Resource group: Select a resource group for the public address range.
  
  After you create a public address range, you can't change the resource group.
- Tags: Optional: Add tags to help you organize and find your resources. You can always add more tags later. For more information, see Working with tags.
- BYOIP (IPv4) Beta Public address source: Select one of the following:
  - IBM CIDRs: Select from IBM-managed IP address pools. Then, select the size (number of IPs) of the address range. You can choose from 1, 2, 4, 8, or 16 IPs to include in the block.
    
    After you create a public address range, you can't change its size.
  - Custom authorized CIDRs: From the Authorized CIDR list, select the custom authorized CIDR that you want to allocate addresses from. The available CIDR blocks are limited to valid, unallocated ranges within the selected custom authorized CIDR.
    
    When you select a custom authorized CIDR, you allocate addresses from your own IP range instead of IBM-managed pools. If no authorized CIDRs exist in the menu, you can enter IPs from an authorized CIDR. The new CIDR becomes available immediately for selection.
    
    For more information, see Provisioning a custom authorized CIDR.
  For zonal authorized CIDRs, only CIDRs associated with the selected zone are available.
Optional: If you want to bind your public address range to an existing VPC, toggle the Bind switch to On. Then, select the VPC and availability zone that you want to bind to.

You can bind a public address range to any VPC in a single availability zone that already exists in your account. You can also bind the address range to a VPC later. For more information, see Binding a public address range.
Click Create. The public address range is requested for use.

On the Public address ranges for VPC page, your address range is displayed in the table. It takes a few minutes for the status of the public address range to change from Updating to Stable. When in Stable status, the address range is ready for use.

Creating public address ranges from the CLI

To create public address ranges from the command line, follow these steps:

Set up your CLI environment.
Log in to your CLI environment. After you enter the password, the system prompts which account and region that you want to use:
```
ibmcloud login --sso
```
Run the following command:
```
ibmcloud is public-address-range-create --ipv4-address-count IPV4_ADDRESS_COUNT [--name NAME] [--vpc VPC --zone ZONE] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]
```
BYOIP (IPv4) Beta
```
ibmcloud is public-address-range-create (--ipv4-address-count IPV4_ADDRESS_COUNT | --cidr CIDR) [--name NAME] [--vpc VPC --zone ZONE] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]
```
IPv6 Beta
```
ibmcloud is public-address-range-create (--ipv4-address-count IPV4_ADDRESS_COUNT | --cidr CIDR | (--authorized-cidr AUTHORIZED_CIDR --network-prefix-length NETWORK_PREFIX_LENGTH)) [--name NAME] [--vpc VPC --zone ZONE | --vni VNI] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]
```
Where:

--ipv4-address-count

The total number of public IPv4 addresses required. Must be a power of 2.BYOIP (IPv4) Beta Mutually exclusive with --cidr.IPv6 Beta Mutually exclusive with --authorized-cidr.

BYOIP (IPv4) Beta --cidr : The public IPv4 range for this public address range expressed in CIDR format. Must be an unallocated block within a custom authorized CIDR in your account. Mutually exclusive with --ipv4-address-count.

IPv6 Beta --cidr : The public IPv4 or IPv6 range for this public address range, expressed in CIDR format. Must be an unallocated block within an authorized CIDR in your account. Mutually exclusive with --ipv4-address-count and --authorized-cidr.

--authorized-cidr

The ID or name of the authorized CIDR to allocate the IPv6 public address range from. Required together with --network-prefix-length. Mutually exclusive with --cidr and --ipv4-address-count.

--network-prefix-length

The network prefix length for this public address range. Required when --authorized-cidr is specified. Supported values: 64–128.

--name

A name for the public address range. Names beginning with ibm- are reserved for provider-managed resources and are not allowed.

--vpc

The VPC to bind this public address range to. Requires --zone.IPv6 Beta Not valid for IPv6 public address ranges. Use --vni instead.

--zone

The zone where this public address range resides. Requires --vpc.IPv6 Beta Not valid for IPv6 public address ranges.

IPv6 Beta --vni : The ID or name of the virtual network interface to bind this public address range to at creation. Mutually exclusive with --vpc and --zone.

--resource-group-id

ID of the resource group. Mutually exclusive with --resource-group-name.

--resource-group-name

Name of the resource group. Mutually exclusive with --resource-group-id.

--output

The output format, only JSON is supported. One of: JSON.

-q, --quiet

Suppress verbose output.

Command examples

Create a public address range named public-address-range-1 with an address count of 8:

ibmcloud is public-address-range-create --name public-address-range-1 --ipv4-address-count 8

Create a public address range that is named public-address-range-2 with an address count of 4 and a resource group named Default:

ibmcloud is public-address-range-create --name public-address-range-2 --ipv4-address-count 4 --resource-group-name Default

Create a public address range named public-address-range-3 with an address count of 8, bound to VPC cli-test-vpc in zone us-south-1 with resource group ID 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3:

ibmcloud is public-address-range-create --name public-address-range-3 --ipv4-address-count 8 --vpc cli-test-vpc --zone us-south-1 --resource-group-id 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3

BYOIP (IPv4) BetaCreate a public address range from a custom authorized CIDR, bound to a VPC and zone:

ibmcloud is public-address-range-create --name public-address-range-3 --cidr 46.16.186.112/28 --vpc cli-test-vpc --zone us-south-2 --resource-group-name Default

Create an unbound public address range from a custom authorized CIDR:

ibmcloud is public-address-range-create --name public-address-range-4 --cidr 46.16.186.128/28 --resource-group-name Default

IPv6 BetaCreate an IPv6 public address range with a prefix length of /112 from an authorized CIDR, and bind it to a VNI:

ibmcloud is public-address-range-create --name my-ipv6-par --authorized-cidr r006-81222eee-b3e0-4dc3-b429-aee9e5c0abf2 --network-prefix-length 112 --vni 02h7-c26bbb47-fd16-4d4b-bb3a-f620f592b84c

Create an unbound IPv6 public address range (bind to a VNI later):

ibmcloud is public-address-range-create --name my-ipv6-par-unbound --authorized-cidr r006-81222eee-b3e0-4dc3-b429-aee9e5c0abf2 --network-prefix-length 112

Creating public address ranges with the API

Before you begin, set up your API environment.

Select one of the following options:

Create a public address range from IBM-managed IPs, bound to a VPC:

curl -sX POST \
"$vpc_api_endpoint/v1/public_address_ranges?version=$api_version&generation=2" \
-H "Authorization: Bearer $iam_token" \
-H "Content-Type: application/json" \
-d '{
      "ipv4_address_count": 8,
      "name": "my-public-address-range",
      "target": {
         "vpc": {
            "id": "r006-4727d842-f94f-4a2d-824a-9bc9b02c523b"
         },
         "zone": {
            "name": "us-south-1"
         }
      }
   }'

Create an unbound public address range from IBM-managed IPs:

curl -sX POST \
"$vpc_api_endpoint/v1/public_address_ranges?version=$api_version&generation=2" \
-H "Authorization: Bearer $iam_token" \
-H "Content-Type: application/json" \
-d '{
      "ipv4_address_count": 8,
      "name": "my-public-address-range"
   }'

BYOIP (IPv4) Beta

Create a public address range from a custom authorized CIDR (requires is.public-address-range.authorized-cidr.operate IAM action on the authorized CIDR):

curl -sX POST \
"$vpc_api_endpoint/v1/public_address_ranges?version=$api_version&generation=2" \
-H "Authorization: Bearer $iam_token" \
-H "Content-Type: application/json" \
-d '{
      "cidr": "192.168.3.192/28",
      "name": "my-par-from-cidr"
   }'

IPv6 Beta

Create an IPv6 public address range from an authorized CIDR, bound to a VNI:

curl -sX POST \
"$vpc_api_endpoint/v1/public_address_ranges?version=$api_version&generation=2" \
-H "Authorization: Bearer $iam_token" \
-H "Content-Type: application/json" \
-d '{
      "name": "my-ipv6-par",
      "authorized_cidr": { "id": "'$authorized_cidr_id'" },
      "network_prefix_length": 112,
      "target": {
         "virtual_network_interface": { "id": "'$vni_id'" }
      }
   }'

If you need to change the size of the address range or the resource group, you must delete and recreate the address range.

Creating public address ranges

Creating public address ranges

Before you begin

Creating public address ranges in the console

Creating public address ranges from the CLI

Command examples

Creating public address ranges with the API

Next steps