Beta VPC API change log

For all version dates

Reservation automatic attachment support is now generally available. See the VPC API change log.

Reservation automatic attachment support. Accounts that have been granted special approval to preview this feature can now automatically attach a reservation when creating an instance or creating a bare metal server. Additionally, when updating an instance or updating a bare metal server, you can change the reservation_affinity.policy to automatic for the instance or bare metal server to automatically attach to available reserved capacity.

When creating a reservation, you can now specify an affinity_policy of restricted to prevent the policy from being used for automatic attachments. Similarly, while a reservation's status is inactive, you can update a reservation to be restricted.

For more information, see Automatic attachments for reservations.

For version 2024-10-22 or later

Reservation affinity policy default is now generally available. See the VPC API change log.

Reservation affinity policy default. When using a version query parameter of 2024-10-22 or later, the reservation_affinity.policy defaults to automatic when creating a reservation. Similarly, when using a version query parameter of 2024-10-22 or later, the reservation_affinity.policy defaults to automatic when creating an instance or creating a bare metal server. The behavior remains unchanged when using a version query parameter of 2024-10-21 or earlier.

For all version dates

This release introduces the following updates for accounts that have been granted special approval to preview and use these features. Although usage of these features is restricted, changes to schemas (such as new properties) will be visible to all accounts.

NVIDIA Hopper HGX H100 instance profiles. When creating an instance, a new gx3d-160x1792x8h100 instance profile is available in select zones. This profile provides 8 NVIDIA H100 GPUs that are tuned for AI workloads, such as inferencing, fine tuning, and large-scale training. For details, see Accelerated profile family - Gen 3.

Cluster networks. Cluster networks provide high-bandwidth, low-latency networking for workloads such as AI training and large-scale simulations. You can now create cluster networks using a cluster network profile, which defines the cluster network performance characteristics and capabilities. The H100 cluster network profile is the first cluster network profile being introduced. It provides a specialized network that implements the RoCEv2 protocol to enable remote direct memory access for your workloads that are running on the gx3d-160x1792x8h100 instance profile.

When creating an instance using a supported cluster profile, you can specify the new cluster_network_attachments property to connect the virtual server instance to your cluster network. Alternatively, you can create cluster network attachments on an existing instance that is in a stopping or stopped state. Additionally, when creating an instance template you can specify cluster_network_attachments.

Instance profile schema changes. When retrieving and listing instance profiles, the response includes the following new properties:

• cluster_network_attachment_count specifies the number of cluster network attachments supported for that instance profile.
• supported_cluster_network_profiles indicates the cluster network profiles that are supported for that instance profile.

Learn about cluster networks, cluster network subnets, cluster network interfaces, and explore the new API methods.

This feature is now available for accounts that have been granted special approval to preview and use this feature. Although usage is restricted, changes to schemas (such as new properties) will be visible to all accounts. See the VPC API change log.

For all version dates

Automatic deletion policy for endpoint gateway bindings. Endpoint gateway bindings are automatically deleted when they are no longer needed. This policy is now reflected in the new endpoint_gateway_binding_auto_delete and endpoint_gateway_binding_auto_delete_timeout properties included when listing or retrieving a private service gateway, and may be configurable in the future.

Wildcard support for private path service gateway service_endpoints. When creating a private path service gateway, wildcard domains in the service_endpoints property are now supported, allowing you to specify service endpoints using patterns such as *.example.com.

Load balancer access modes. New properties are provided in responses to load balancer and load balancer profile methods, allowing you to view the access mode for load balancers. Possible values are private, private_path, and public. When listing and retrieving load balancer profiles, the access_modes property denotes the access modes supported by load balancers with this profile. When listing or retrieving load balancers, the access_mode property denotes the access mode for the load balancer.

For version 2024-09-17 or later

Private Path service gateways is now available for accounts with special approval to preview this feature. See the VPC API change log.

Support for beta API versions earlier than 2024-09-17 was removed on 5 November 2024.

Publishing or unpublishing changes for private path service gateways. When using a version query parameter of 2024-09-17 or later to update a private path service gateway, the published property is no longer supported. published is now read only and defaults to false when a private path service gateway is first created, indicating that access is restricted to the account that created this private path service gateway. New methods must be used to publish or unpublish a private path service gateway.

HTTP status code changes for private path service gateway methods. When using a version query parameter of 2024-09-17 or later to permit or deny an endpoint gateway binding for a private path service gateway, revoke access to a private path service gateway for an account, or delete a private path service gateway, the response code is changed from 200 to 204 for successful operations. A response code of 200 will continue to be returned for these API requests when using a version query parameter of 2024-09-16 and earlier.

Private path service gateway property name change. When using a version query parameter of 2024-09-17 or later to create or update a private path service gateway, the endpoint_gateways_count property is renamed to endpoint_gateway_count. The endpoint_gateways_count property name will continue to be returned when using a version query parameter of 2024-09-16 and earlier.

This feature is now generally available. See "Block storage schema enhancements for adjustable capacity and IOPS" in the VPC API change log.

Support for beta API versions earlier than 2024-09-17 was removed on 5 November 2024.

Revised block storage capabilities. When making API requests using a version query parameter of 2024-09-17 or later, the volume profile unattached_capacity_update_supported property has been changed to adjustable_capacity_states, and the volume profile unattached_iops_update_supported property has been changed to adjustable_iops_states. This change applies when listing or retrieving a volume profile.

Similarly, when making API requests using a version query parameter of 2024-09-17 or later, the volume unattached_capacity_update_supported property has been changed to adjustable_capacity_states, and the volume unattached_iops_update_supported property has been changed to adjustable_iops_states. This change applies when creating or updating a volume, listing volumes, or retrieving a volume.

For all version dates

Reservations for bare metal servers is now generally available. See the VPC API change log.

Reservations for bare metal servers. Accounts that have been granted special approval to preview this feature can now purchase a capacity reservation for a specified bare metal server profile in a specified zone. Reservations provide resources for future deployments and cost savings over the life of the term within the availability zone of your choice.

When creating or updating a reservation, specify the capacity.total and committed_use.term properties to use for this reservation. Optionally specify the committed_use.expiration_policy property to apply when the committed use term expires (default: release). Specify the profile.name and profile.resource_type properties of the profile, and the zone property to use for this reservation. After you confirm the reservation is configured the way you want it, you must activate the reservation. The reservation cannot be deleted until the committed use term expires. To provision a bare metal server using a reservation's capacity, specify the reservation using the reservation_affinity.pool property when creating the bare metal server. You can also update a bare metal server that's been provisioned to associate it with a reservation.

When retrieving a bare metal server, the new reservation_affinity property indicates the reservation affinity policy in effect for the bare metal server. The new health_state property indicates the bare metal server's overall health state, while an accompanying health_reasons property indicates the reason for any unhealthy health states, such as a failed reservation.

For more information, see Provisioning reserved capacity for VPC.

For all version dates

Bare metal server reinitialization. You can now reinitialize a bare metal server. To reinitialize a bare metal server, specify the image to provision, one or more SSH public keys, and optionally specify user_data. Upon successful reinitialization, the bare metal server starts automatically and retains the same physical node, interfaces, IP addresses, and resource IDs it had before reinitialization.

To reinitialize a bare metal server, the server status must be stopped, or have failed a previous reinitialization. For more information, see Managing Bare Metal Servers for VPC.

This feature is now generally available. See the VPC API change log.

For all version dates

Firmware update for bare metal servers. You can now update firmware for a stopped bare metal server. This request updates server firmware if newer firmware is available and automatically starts the bare metal server after the firmware update is successfully completed. If you don't want the bare metal server to start after the firmware is updated, set the auto_start property value to false in the request.

When listing and retrieving a bare metal server, the response includes the new firmware property, which in turn has an update property that indicates the type of update available (none, optional, or required). For more information, see Managing Bare Metal Servers for VPC.

This feature is now generally available. See the VPC API change log.

For all version dates

Generic operating system custom images and network bootable bare metal servers. Accounts that have been granted special approval to preview this feature can now create a generic operating system custom image, which is an image containing an operating system that is not specifically defined in IBM Cloud VPC. Such approved accounts can also use a specific new stock image to create a bare metal server that will network boot an image using iPXE.

To facilitate these features, two new immutable operating system properties, user_data_format and allow_user_image_creation, and one new immutable image property, user_data_format, are provided. The operating system property user_data_format (possible values cloud_init, esxi_kickstart, ipxe) populates the image user_data_format property, which specifies how user_data is interpreted and used when creating a virtual server instance or creating a bare metal server. The operating system property allow_user_image_creation indicates whether an operating system may be used to create a custom image.

For more information, see Importing and validating custom images into VPC.

Images that are used to create virtual server instances or to create instance templates must have a user_data_format value of cloud_init.

For all version dates

Private path network load balancer. Accounts that have been granted special approval to preview this feature can now create a private path network load balancer to enable and manage private connectivity for consumers of a hosted service. When creating a load balancer, you can specify the new is_private_path property value as true to create a private path network load balancer.

Load balancer and load balancer profile properties. The private path load network balancer feature introduces a new load balancer profile network-private-path, along with the following new load balancer and load balancer profile properties:

• source_ip_session_persistence_supported indicates whether a load balancer supports source IP session persistence. Source IP session persistence is not supported by private path network load balancer.
• availability indicates the availability of a load balancer. Load balancers with subnet availability remain available if at least one of its subnets is in a zone that's available. Load balancers with region availability remain available if at least one zone in the region is available. Private path network load balancers have region availability. Other load balancers have subnet availability.

The value for load balancer profiles properties route_mode_supported, security_groups_supported, udp_supported, and logging_supported is set to false for private path load balancers. Additionally, private path load balancers do not support setting or updating the dns property, because a private path network load balancers are accessed using endpoint gateways where DNS is configured.

Private path service gateway. Accounts that have been granted special approval to preview this feature can now create private path service gateways. Creating, updating, and deleting private path service gateways allows you to configure and manage access to private path services. Private path service gateways also have two sub-resources:

• Account policies provide per-account access policies that supersede the private path service gateway's default access policy. You can create, update, and delete policies to permit, deny, or manually review requests from any account. You can also revoke current and future access for an account. For more information, see About account policies.

• Endpoint gateway bindings represent each request to access to the private path service gateway. The associated account policy is applied to all pending endpoint gateway bindings. If an associated account policy doesn't exist, the private path service gateway's default_access_policy is used. If the resulting policy is review, you will be able to explicitly approve or deny the request, and optionally set a new policy for future requests from the account.

Learn about creating private path service gateways, and explore the new API methods.

For all version dates

This release introduces the following updates for accounts that have been granted special approval to preview these features:

Confidential computing capabilities. On select instance profiles, you can now enable Intel® Software Guard Extensions. When creating or updating an instance or when creating or updating an instance template, you can specify the new confidential_compute_modes property value (disabled or sgx) to use for a virtual server instance. The new confidential_compute_modes instance profile property indicates which profiles will support which modes. If you do not specify the confidential_compute_modes property when creating an instance or instance template, the default confidential compute mode from the profile will be used.

Secure boot capabilities. When creating or updating an instance or when creating or updating an instance template, you can set the new enable_secure_boot property to true to enable secure boot on the virtual server instance. The new secure_boot_modes instance profile property indicates the secure boot modes supported by the profile. If you do not specify the enable_secure_boot property when creating an instance or instance template, the default secure boot mode from the profile will be used. To use secure boot, the image must support secure boot or the instance will fail to boot.

To update the enable_secure_boot and confidential_compute_mode properties, the virtual server instance status must be stopping or stopped.

For all version dates

New IBM® Cloud Block Storage for Virtual Private Cloud profile. For accounts that have been granted special approval to preview this feature a new defined_performance family is introduced for data and boot volumes. The defined_performance volume profile family contains the sdp profile, which provides similar functionality to the custom volume profile. The new profile introduces the ability to make capacity increases and IOPS changes to volumes, even when they're not attached to a virtual server instance. The properties unattached_capacity_update_supported and unattached_iops_update_supported properties have been added to all volumes and volume profiles so you can make use of these capabilities in your automation. For more information, see About Block Storage for VPC and Viewing available IOPS profiles.

For version 2023-08-08 or later

This feature is now generally available. See About file share replication.

Support for beta API versions earlier than 2023-08-08 was removed on 22 September 2023.

This release introduced the following behavior changes for users with accounts that have access to file shares.

Fail over to replica share. When making API requests using a version query parameter of 2023-08-08 or later, the default value for the fallback_policy property has been changed to fail, and the replication relationship between the shares is broken.

Retrieve source share information for a replica share. When making API requests using a version query parameter of 2023-08-08 or later, requests to retrieve the source file share for a replica file share now return a more concise source share reference, instead of a share.

For version 2023-07-11 or later

This feature is now generally available. See the VPC API change log.

Support for beta API versions earlier than 2023-07-11 was removed on 25 August 2023.

Data encryption in transit for file shares. For users with accounts that have access to file shares, you can now enable secure end-to-end encryption of your data in transit between the file share and the authorized client.

When creating a mount target for a file share with a virtual network interface, you can now specify a transit_encryption property value of none (default) or user_managed, which encrypts the data in transit by using IPsec with an instance identity certificate. For more information, see Encryption in transit and Instance identity certificates in the Beta VPC Instance Metadata API change log.

File share access control modes. For users with accounts that have access to file shares, you can now control the way a share is accessed when creating and updating a file share. Specifying access_control_mode property value security_group now allows the use of security groups to manage which resources can access the file share. By using security groups, access can now be restricted to specific clients. When you specify access_control_mode property value vpc, all clients in each mount target's VPC will continue to have access to this share.

The default value of access_control_mode depends on the version query parameter date and the profile selected. When making API requests with a version query parameter of 2023-07-11 or later, the default is security_group. For requests that are using a version query parameter of 2023-07-10 or earlier, the default is vpc. File shares must be based on the dp2 profile to use the security_group value.

When creating a mount target for a file share with access_control_mode set to security_group, you must also create a virtual network interface by using the virtual_network_interface property. For more information, see About virtual network interfaces and Mount target access modes. You must use an access_control_mode of security_group to enable Data encryption in transit for file shares.

For all version dates

Image lifecycle management property name changes. For accounts that have been granted special approval to preview the image lifecycle management feature, the deprecated_at and obsoleted_at properties for images requests have been renamed deprecation_at and obsolescence_at, respectively. Original property names deprecated_at and obsoleted_at will continue to be supported until the feature becomes generally available. Requests that specify the original and revised property names simultaneously will be rejected.

This feature is now generally available. Support for property names deprecated_at and obsoleted_at has been removed. See the VPC API change log.

For all version dates

Enforcement of file shares beta API requests. Starting with API version 2023-05-30, all requests made for shares methods must include the maturity=beta query parameter. Requests that omit the maturity=beta query parameter will be regarded as requests against the VPC GA API, which does not yet support shares. As a result, those requests will fail.

For version 2023-05-30 or later

This feature is now generally available. See the VPC API change log.

Support for beta API beta versions earlier than 2023-05-30 was removed on 14 July 2023, and the targets property was removed.

This release introduced the following features for users with accounts that have access to file shares.

File shares property and request path name changes. When making API requests using a version query parameter of 2023-05-30 or later, the shares targets property has been changed to mount_targets. This change applies when creating, updating, listing, and retrieving a file share, and when listing all mount targets for a file share.

The name change also applies to the method paths: Requests using a version query parameter of 2023-05-30 or later must use /shares/{share_id}/mount_targets (instead of /shares/{share_id}/targets) in the request URL. This change applies when creating, updating, listing, retrieving, and deleting share mount targets.

For all version dates

Revised file share profiles. For users with accounts that have access to file shares, a new dp2 profile is now available when creating and updating a file share. Profiles in the existing custom and tiered families have been deprecated and will remain available only to accounts that have already provisioned file shares with those profiles. The deprecated profiles also will not be included in the upcoming general availability release for file shares.

The dp2 profile belongs to a new defined_performance file share profile family, which provides similar functionality to the deprecated custom file share profile family. While existing file shares using profiles in the custom and tiered families will continue to work, you are encouraged to update all your file shares to the new dp2 profile in preparation for general availability of the file share service. Bulk migration of existing file shares is not supported. For more information, see dp2 file storage profile.

IOPS and size configuration for file share profiles. New file share properties size and iops are also provided in the API responses when retrieving a file share profile. The size property shows the permitted capacity range (in gigabytes) for a share with the profile. The iops property shows the permitted IOPS range for a share with the profile. The maximum IO operations each client that accesses the file can perform is 48,000 IOPS. When multiple clients access the file share, the share can handle a maximum of 96,000 IO operations per second.

This API feature was released to production on 2023-04-11, but this announcement was not included at the time.

This feature is now generally available. See the VPC API change log.

Image lifecycle management. Accounts that have been granted special approval to preview this feature can now deprecate or obsolete custom images directly. Alternatively, you can schedule transition at a later date by specifying the deprecated_at or obsoleted_at properties when creating or updating an image. If you need to revert a status change, you can transition deprecated or obsolete images back to available. For more information, see Managing custom images.

deprecated custom images remain usable, while obsolete images cannot be used to provision instances or bare metal servers.

This feature is now generally available. See the VPC API change log.

For all version dates

Exporting custom images. Accounts that have been granted special approval to preview this feature can now export custom images to an authorized IBM Cloud Object Storage bucket. Specify the target storage_bucket to export the image to. The image will be exported as qcow2 unless you specify another value using the format property.

For more information, see Exporting a custom image to IBM Cloud Object Storage, or start using the new export jobs methods.

This feature is now generally available. See the VPC API change log.

For all version dates

Backup for VPC. Backup policy jobs are now generally available. The following updates have been made for listing backup policy jobs and retrieving a backup policy job since the beta release:

• The source_volume property has been replaced by the source property.
• The target_snapshot property has been replaced by the target_snapshots array property.

See the VPC API change log.

Instance provision by volume. Accounts that have been granted special approval to preview this feature can now reuse an existing boot volume to provision a virtual server instance by specifying the existing volume's id or crn sub-property of the boot_volume_attachment property. The specified volume must be unattached and must have an operating system with the same architecture as the instance profile. Volumes now include an attachment_state property and an expanded operating_system property you can use to view a volume's eligibility. You can also use the new list volumes filters to list volumes that have specific attachment_state, operating_system, and encryption_type values.

By default, a boot volume attached to a virtual server instance is deleted when the instance is deleted. To preserve the boot volume when deleting a virtual server instance, change the delete_volume_on_instance_delete property to false by updating the boot volume attachment. See Creating virtual server instances, Creating VPC resources with CLI and API for more information.

This feature is now generally available. Since the beta release, by default, only a boot volume created as part of provisioning a virtual server instance will be deleted when the instance is deleted. See the VPC API change log.

For all version dates

Sharing images across an enterprise account. Accounts that have been granted special approval to preview this feature can now use a catalog to share custom images with users in other accounts within the same enterprise. When you create an image, a new catalog_offering property includes a published sub-property that is set to false by default. When the custom image is imported to a catalog the published sub-property is set to true, indicating that the image is added to a catalog offering version and is managed from a catalog. If you are authorized to the catalog offering version, you can provision virtual server instances using that custom image by specifying its catalog_offering.version.crn. To use the custom image associated with the latest version in the offering, specify catalog_offering.offering.crn instead. The image may not be deleted from your IBM Virtual Private Cloud while it is managed from a catalog.

For more information, see the tutorial Onboarding a virtual server image for VPC and the Import offering method in the Catalog Management API.

This feature is now generally available. The catalog_offering.published property in the beta API definition has been renamed to catalog_offering.managed. See the VPC API change log.

For all version dates

File storage cross-account encryption. Accounts that have been granted special approval to preview this feature can now use cross-account customer-managed encryption keys (CRKs) when creating a file share with customer-managed encryption. With this feature, the CRK account owner invites you and sets the IAM delegated policy to the CRKs. Afterward, specify your IAM token to create a file share with an encryption_key CRN from the CRK account. For more information, see Creating file shares with customer-managed encryption.

This feature is now generally available. See the VPC API change log.

For all version dates

Client VPN for VPC. Client-to-site connectivity is now generally available. See the VPC API change log.

The following updates have been made since the 24 August 2021 beta release:

• You can use IBM Cloud Secrets Manager for server authentication when creating a VPN server
• You can specify a VPN server when adding a target to a security group
• You can update a VPN server to be highly available, or detach a subnet to downgrade to a stand-alone deployment

For all version dates

File storage adjustable IOPS. Accounts that have been granted special approval to preview this feature can now update the IOPS of an existing file share. For a file share using a custom profile, specify the iops property. For a file share using a profile in the tiered profile family, specify another tier within the tiered family, which will set the iops based on the share's size.

You can also change a share between the tiered and custom profile families so long as the requested iops and size are supported by the requested profile. For more information about file share profiles, see File Storage for VPC profiles. For more information about adjusting IOPS with a profile, or changing between tiered and custom profiles, see Adjusting file share IOPS.

This feature is now generally available. See the VPC API change log.

For all version dates

AMD support for instances and dedicated hosts. Accounts that have been granted special approval to preview this feature can select new profiles for dedicated hosts and instances. When provisioning or managing an instance or dedicated host, use the new vcpu_manufacturer property to choose between profiles from different processor manufacturers.

This feature is now generally available. See the VPC API change log.

For all version dates

Backup for VPC. Accounts with special approval to preview this feature can now create up to four plans for backup policies. You can now also update and delete existing plans, and add backup plans to existing policies. You can use one of the new deletion_trigger sub-properties to specify a custom backup deletion policy. For more information, see Managing backup policies.

Backup policies now also include information about backup policy jobs. A backup policy job is automatically created each time a backup has to be created or deleted to meet the backup policy's settings. For more information, see Backup for VPC.

The backup API is now generally available, with the exception of the backup jobs API, which remains in beta. See the Change log.

The backup jobs API is now generally available. See the VPC API change log

For all version dates

File share replication. Accounts that have been granted special approval to preview this feature can now set up replication between a file share in one zone and a replica file share in another zone in the same region. Using replication is a good way to recover from an incident at your primary site, if data becomes inaccessible or an applications fails.

• When creating a new file share, you can now configure replication by specifying the new replica_share property. To create a replica for an existing file share, create a new share and specify the existing file share as source_share, along with the replication schedule, using the replication_cron_spec property.
• You can now retrieve the source file share for a replica file share. Returned information also includes the replication schedule, role, status, and status reasons.
• You can now split the source file from a replica share, which removes the replication relationship between a source share and its replica share, resulting in two independent read-write file shares. This action cannot be reversed. For more information, see Remove the replication relationship.
• You can now fail over to the replica file share, which reverses the replication relationship. You can optionally specify split for the fallback_policy to trigger a split if the failover operation fails or times out. For more information, see Replication failover.

File storage native tagging. Accounts that have been granted special approval to preview this feature can now specify user_tags when creating a new file share or updating an existing file share. Adding user tags to a file share helps you organize your resources. For details, see Add user tags to a file share.

This feature is now generally available. See the VPC API change log.

For all version dates

VPN client-to-site servers update. You can now update the subnets for a VPN server after the VPN is provisioned. For example, you can upgrade a stand-alone VPN server (one subnet) to a High Availability (HA) VPN server (two subnets in different zones). You can also detach a subnet to downgrade an HA VPN server to a stand-alone deployment, or change an attached subnet after your VPN server is provisioned. For more information, see Upgrading to an HA VPN server.

For all version dates

Backup for VPC. Accounts that have been granted special approval to preview this feature can now create backup policies to automatically back up block storage volumes. Use the new backup service APIs to create, list, and manage backup policies. Backup policies control which source volumes are selected for backup by matching user tags in the volume with tags defined in the backup policy. For this beta release, a backup policy contains one backup plan in which a deletion_trigger specifies the maximum number of days to keep each backup after creation. For more information, see About Backup for VPC.

For all version dates

Concurrent update protection. To prevent multiple clients from unknowingly overwriting each other's updates, select API methods support entity-tags and conditional requests.

This feature is now generally available. See the VPC API change log.

For all version dates

Customer-managed encryption for file shares. Accounts that have been granted special approval to preview this feature can now use customer-managed encryption, also called Bring Your Own Key (BYOK), to create a file share that is encrypted using your root key. Specify the new encryption_key property and crn sub-property of the root key that you either imported to IBM Cloud or created in Key Protect or Hyper Protect Crypto Services (HPCS). For more information, see Creating file shares with customer-managed encryption.

You can also use the API to rotate the root keys that are protecting your file shares. See Key rotation for VPC resources for details.

Supplemental user/group IDs for file shares. Accounts that have been granted special approval to preview this feature can now access supplemental user/group IDs for file shares. When a process runs on Unix/Linux, the operating system identifies a user with a user ID (UID) and/or group with a group ID (GID). These IDs determine which system resources a user or group can access. When you create a file share, you can specify the new initial_owner property and specify a uid, gid, or both sub-properties to control access to the share. For more information, see Adding supplemental IDs when you create a file share from the API.

For all version dates

VPN client-to-site servers. Until now, the Virtual Private Network (VPN) for VPC service supported only site-to-site connectivity, which connects your on-premises network to the IBM Cloud. This beta release adds client-to-site connectivity, which allows remote devices to securely connect to the VPC network using an OpenVPN software client. This solution is useful for telecommuters who want to connect to the IBM Cloud from a remote location, such as a home office. For more information, see About VPN servers (client-to-site) or check out the new API methods.

This feature is now generally available. See the VPC API change log.

For all API version dates

File storage for VPC. Accounts that have been granted special approval to preview this feature can now increase file share size in gigabyte increments up to 32 TB (depending on the file share's profile). The increase takes effect immediately. For more information, see Expanding file share capacity. You can also specify the maximum input/output operations per second (IOPS) when creating a file share, within the range available for its size. For more information, see Custom IOPS profile.

This feature is now generally available. See the VPC API change log.

For all version dates

Beta VPC instance metadata API. Accounts that have been granted special approval to preview this feature can now preview the new beta IBM Cloud® Virtual Private Cloud (VPC) Instance Metadata API. This API provides access to VPC instance metadata, including instance initialization data, network interfaces, volume attachments, public SSH keys, and placement groups. Use the VPC create instance or VPC update instance methods to enable or disable the metadata service endpoint for a particular instance. For more information, see About VPC Instance Metadata.

For all API version dates

GPU instances. Accounts that have been granted special approval to preview this feature can now view new instance profiles, which include GPUs attached to the instance. These attached GPUs allow for accelerated computing to run workloads with more powerful compute capabilities.

The following API methods have been enhanced:

• List instances returns a new gpu property with four additional sub-properties: count, manufacturer, model, and memory
• Retrieve an instance profile returns four new properties: gpu_count, gpu_manufacturer, gpu_model, and gpu_memory

For more information, see Managing GPUs.

This feature is now generally available. See the VPC API change log.

For all version dates

Bare metal servers for VPC. Accounts that have been granted special approval to preview this feature can now create bare metal servers to host VMware clusters in IBM Cloud VPC. You can set up VMware management applications and create VMware virtual machines on the bare metal servers. As bare metal servers are integrated with the VPC platform, you can take advantage of the network and security capabilities of IBM Cloud VPC. For more information, see About Bare Metal Servers for VPC (beta) or dive into the new API methods.

This feature is now generally available. See the VPC API change log.

For all version dates

Placement groups. Placement groups for IBM Cloud® Virtual Private Cloud are logical groupings of virtual server instances that can be configured to reduce the risk of correlated failures inherent in your physical environment, such as networking issues, power loss, or hardware failure. Define a placement group strategy for high-availability workloads, such as for host or power spread. For more information, see About placement groups or dive into the new API methods.

This feature is now generally available. See the VPC API change log.

For all version dates

File storage for VPC. Accounts that have been granted special approval to preview this feature can now create NFS-based file shares in a zone in your region. Share file storage over multiple virtual service instances within the same zone across multiple VPCs. Learn about creating file shares and mount targets, and explore the new API methods.

This feature is now generally available. See the VPC API change log.

For all version dates

Instance resize. You can now resize an instance by providing the profile property in the API method PATCH /instances/{id} (Update an instance). For more information, see Resizing a virtual server instance.

This feature is now generally available. See the VPC API change log.

For all version dates

Bring your own license. You can now bring your own license (BYOL) for custom images that you create and import to IBM Cloud VPC. When you import a custom image, you can choose from new byol Red Hat Enterprise Linux (RHEL) and Windows operating systems.

A new dedicated_host_only property has been added to operating system resources. Any instance with a boot volume created from an image with operating_system.dedicated_host_only set to true must be placed on a dedicated host (or into a dedicated host group). Since Windows BYOL images have dedicated_host_only set to true, they must be placed on a dedicated host (or into a dedicated host group). There are no restrictions on placing instances using RHEL BYOL images.

Every operation that returns an OperatingSystem resource now includes a dedicated_host_only property.

This feature is now generally available. See the VPC API change log.

For all version dates

Instance resize. Accounts that have been granted special approval to preview this feature can now resize an instance by providing the profile property in the API method PATCH /instances/{id} (Update an instance). For more information, see Resizing a virtual server instance.

This feature is now generally available. See the VPC API change log.

For all version dates

Block storage snapshots. Accounts that have been granted special approval to preview this feature can now create and use snapshots and explore the new snapshots API methods.

This feature is now generally available. See the VPC API change log.

Virtual server instance console. Accounts that have been granted special approval to preview this feature can now access instances by connecting to a VNC or serial console. Learn about accessing virtual server instances by using VNC or serial consoles, and explore the new instance console API methods:

• Create a console access token for an instance
• Retrieve the console WebSocket for an instance

This feature is now generally available. See the VPC API change log.