February#

February 4#

Changes#

  • Application load balancers got the following features:

    • On the Targets tab on the target group page, you can find out the reason why the target is unavailable.

    • The IP addresses of the internal load balancer are accessible from anywhere in your infrastructure: from another VPC via a transit gateway, from the corporate network via VPNaaS or Direct Connect.

February 13#

Changes#

  • Metrics for Internet traffic monitoring are added. The new metrics allow you to control the volume of outgoing and incoming traffic through a specific Internet gateway or Elastic IP address. You can create alarms for Elastic IP and Internet gateways and configure notification distribution.

Fixed#

  • For a target to access an external network load balancer, you must add an enabling rule for the public IP address of the load balancer to the security group.

  • The minimum password length for the cloud web interface is increased from 8 to 12 characters.

  • The instance created from the launch template is deployed in the specified availability zone.

February 20#

API#

February 27#

Changes#

  • For private DNS zones, you can create resource records of the type CNAME, MX, NS, SRV, TXT, as well as A and CNAME wildcard records.

Fixed#

  • Requests to a private DNS zone are not redirected to public DNS servers. If the private DNS zone has the same name as the default internal VPC domain, then records of this private zone are used to resolve requests.