December#

December 1#

Beta testing of backup service is completed. Backups are now charged per each GiB stored.

Together with the backup copies, information about the instance configuration is now saved, such as type, placement, network settings, etc. When an instance is created from a recovery point, you don’t have to set these parameters again, just confirm their selection.
Tags can be assigned to an Auto Scaling group (ASG). When adding ASG tags, you can also select a checkbox to assign them to instances, which will be automatically created in this group.
An Elastic IP address can be allocated directly in the dialog box where it is assigned to an instance.
Resource details can be copied to the clipboard from the resource table by clicking the copy icon next to the desired parameter field.
In the Routes tab on the route table page, you can sort the resources by network and gateway.
A high-availability VPN connection can also be created with a customer gateway that supports transport mode for VPN (ipsec.legacy type).

The saved backup metadata can be viewed using the GetRecoveryPointRestoreMetadata method.

Together with the network interface ID, its private IP address (if any) is displayed.
PaaS service backups are deleted with the project.
Possible dependencies are taken into account when PostgreSQL extensions are selected.
The bug has been fixed that could cause traffic loss between availability zones when a VPC has multiple route tables and a VPN connection is attached to the VPN gateway in this VPC.
In the web interface, you can create a bucket with the name starting with an uppercase letter.