- Newest
- Most votes
- Most comments
EC2 instances are launched (so: created) and linked to subnets which are themselves assigned to an AZ. This is also true of EC2-attached services such as EBS and network interfaces (ENI). So during deployment you choose the subnet which selects the AZ for you.
For those reading along: You can't move an EC2 instance to a new AZ because it is (as you say) "scoped" to the AZ where it was originally launched. You can create a snapshot of the instance; create an AMI from that snapshot and then launch the AMI in another AZ - noting that it will then have new EBS volumes and a new ENI.
U can set the AZ to a new EC2 instance during deployment by selecting the VPC and Subnet in which AZ you want to launch the instance.
you should have subnets created in multiple Availability Zones, so that while creating EC2 instance you select the subnet according to your AZ which u want your EC2 instance to be placed.
EC2 instance will be placed in particular AZ based on the subnet u select.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
