Cloud version: 13.2-CROC1

API changes

The latest update brings support for new API method:

This method allows to move a stopped instance to or from a placement group.

aws --endpoint-url https://api.cloud.croc.ru \
    ec2 modify-instance-placement \
    --instance <instance_id> \
    --group-name <new_placement_group>

In the example above instance with instance_id will be moved (or added) to Placement group new_placement_group.

aws --endpoint-url https://api.cloud.croc.ru \
    ec2 modify-instance-placement
    --instance <instance_id> \
    --group-name ""

In the example above instance with instance_id will be removed from current Placement group.

Behaviour changes

From now on it is not allowed to run instances in AZ (Availability zone) different from Subnet’s or Virtual Switch’s AZ. All newly-created instances and attached to them Subnets and/or Virtual Switches must be in the same AZ.

All existing configurations will perform without any interruption, but they will be considered legacy.

We highly recommend to stop using such topologies. If you need Instances in different AZs, you should create a Subnet in that AZs and run Instances in them. All Instances inside one VPC automatically have IP connectivity regardless of their AZ placement.