Sanne Raymaekers 7fd150b938 cloud/awscloud: specify subnets when creating secure instance ... For non-default VPCs, AWS needs the subnets it can launch the instance in, otherwise it will try to launch the instance in the default VPC, even if the supplied security groups are attached to a non-default VPC. Furthermore there can only be 1 subnet specified per availability zone, so query the subnets in the VPC of the host (as the instance needs to be launched in the same network), and pick 1 of the VPC's subnets per AZ.		2024-02-14 13:45:52 +01:00
..
awscloud.go	cloud/awscloud: add ec2metadata client	2024-02-14 09:54:11 +01:00
secure-instance.go	cloud/awscloud: specify subnets when creating secure instance	2024-02-14 13:45:52 +01:00