- 최신
- 최다 투표
- 가장 많은 댓글
Hi,
I understand you want to migrate your EC2 Classic to VPC and you had an output message of “checkIfVirtualizationTypeIsHVM” when it stopped on step 3. The output you got is caused by AMI virtualization type. Some instance types support both PV and HVM virtualization, while others support only one or the other. You will need to create an AMI for your instance, you can use this documentation to create one for Windows [1]. In addition I have provided a guided documentation on Migrate from EC2-Classic to a VPC with the Linux create AMI steps also inculded [2]. In the documentation there will also be guided steps on creating a VPC should you feel the need to create a new one.
[1] https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.html
[2] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/vpc-migrate.html
관련 콘텐츠
AWS 공식업데이트됨 2년 전
I have made the following progress:
created a VPC in my target region created a new AMI created a new security group that is visible in the VPC created Systems Manager configuration and (tried) to apply it to all my existing instances
However, I can't get the EC2 instance that I want to migrate to show up in the list of managed instances in the migration runbook, and it now fails at step 5, verifySecurityGroup. The security group that I want to use does show up in the VPC > Security Groups. When I run AWSSupport-TroubleshootManagedInstance on the migrating instance I get CheckVpcEndpoint failed.