October#

October 4#

The number of users and databases that can be added via the PaaS web interface is limited only by the capacity of a certain DBMS. Users and databases are created in separated tabs on the DB page.
Verification of user rights has become more detailed and now includes not only the rights to the service, but also to certain actions.
You can now perform actions on a database cluster even when users and databases are being updated.
Full billing reports provide additional information about consumed resources, e.g. vCPU and RAM for a certain instance, size of individual volumes and images, etc.
Alarm History now contains records about activities which failed when alarm was triggered.
When a password is set for an account, it is additionally checked whether it contains a Latin letter in upper case.

The network interfaces and availability zone set in a launch template are used only for creating individual instances. When instances are created for Auto Scaling Group, they are ignored.
Security groups for database and Kubernetes clusters are displayed as a sorted list in the Information tab.

The resources necessary for Kubernetes clusters are prepared and maintained by the system user system@<customer>.
Activity log registers all API calls to Kubernetes clusters, including system requests for creation, change and deletion of resources that the above services require to operate.

The resources necessary for Auto Scaling Groups are prepared and maintained by the system user system@<customer>.
Activity log registers all API calls to Auto Scaling Groups, including system requests for creation, change and deletion of resources that the above services require to operate.

The GetTrailStatus method helps check when logs were exported to the bucket using parameters LatestDeliveryTime and LatestDeliveryError.