If the organization already has multiple instances running since Jan 2012, which of the below mentioned options should the organization implement while launching a T2 instance?
The organization must migrate to the EC2-VPC platform first before launching a T2 instance.
While launching a T2 instance the organization must create a new AWS account as this account does not have the EC2-VPC platform.
Create a VPC and launch a T2 instance as part of one of the subnets of that VPC.
While launching a T2 instance the organization must select EC2-VPC as the platform.
Explanations:
T2 instances can only be launched in EC2-VPC. However, if the organization has existing EC2-Classic instances, it does not necessarily have to migrate to EC2-VPC first; it can directly create a VPC and launch T2 instances within that VPC.
It is not necessary to create a new AWS account to launch T2 instances. The existing account can create a VPC and launch T2 instances as long as it has not been limited by any legacy configurations.
This is the correct approach. The organization should create a VPC and launch the T2 instance as part of one of the subnets within that VPC, which is required for T2 instances.
While launching a T2 instance, the organization must use the EC2-VPC platform, but this option is incomplete as it does not mention the necessity of creating a VPC to launch the instance. Simply selecting EC2-VPC without creating a VPC is not feasible.
I outline that the answer is:
Create a VPC and launch a T2 instance as part of one of the subnets of that VPC.
If memory serves me right, the answer is:
Create a VPC and launch a T2 instance as part of one of the subnets of that VPC.