August#

August 2#

The web interface now allows you to create instances from launch templates.
To track changes in the amount of data and the number of objects in the bucket, enable Monitoring for bucket parameters in the Information tab on the bucket page. Graphs of parameter changes are displayed in the Metrics tab. Alarms can be set for various events.

In addition, CloudWatch API methods now support metrics from the AWS/S3 namespace.

The Name tag is assigned correctly when an instance is created even if it was specified without going to the Tags step.

To work with K2 Cloud, you can use native rockitcloud provider based on AWS 4.14.0, which goes without Terraform resources not supported in K2 Cloud, but features K2 Cloud-specific functionality (e.g. st2 volume support).
Users can no longer make their own images and snapshots publicly available. This is done to avoid conflicts when using licensed software and minimize the risk of confidential data being cloned inadvertently.

When updating the privileges of an inactive user, the User not found error is no longer displayed.
When deleting a VPC with non-deleted subnets, the correct error message now appears.
Primary network interfaces now get different descriptions when instances are created at the same time.
An error no longer occurs if default DHCP options are assigned to the VPC again.
Allocating an IP address from a block of addresses owned by a user (BYOIP) does not result in an address allocation error when the desired address is not specified.
An inactive user cannot be assigned privileges.

When creating an image from objects in the object storage, you can specify descriptions for volume snapshots.
Using an SMBIOS reader utility, you can find out the BIOS serial name of the virtual machine.

All routes without a prefix in the route table get prefixes automatically.
customer_name is displayed correctly for virtual switches you create.
When you create a customer gateway with the same IP address as an existing gateway has, but with a different BGP ASN, a new gateway is created.

If Kubernetes cluster worker nodes are distributed across placement groups in different availability zones, then their total number can be more than 5, but no more than 5 in each zone.