Thanks for your response. So I creates the AMIs for migration from the EC2 environment and then launched them into a VPC, as per AWS instructions - all reported OK, but instances only appeared to be running under EC2 and not VPC - weird or what? Also EC2 still running after Aug 15 cutoff?
Hi, thanks for the response - My misunderstanding! Phew ....!
EC2 is Elastic Compute Cloud. The cut-off was for the EC2 classic. EC2 instances are and will be supported. The EC2 instances have been migrated to the VPC network which is a private cloud. However to know more into the scenario it would be best to reach out to AWS Premium Support- EC2 team to check on exactly how your console looks like.
You can go to services and into the VPC to check if there was any VPC launched in the region. Also, can you confirm if you have done the below steps ?
If you have no EC2-Classic resources for that account in that region. Additionally, you must terminate all non-VPC provisioned Elastic Load Balancers, Amazon RDS, Amazon Elasti-Cache, & Amazon Redshift resources in that region. After your account has been configured for a default VPC, all future resource launches, including instances launched via Auto Scaling, will be placed in your default VPC.
To request your existing account be setup with a default VPC, please go to Account and Billing -> Service: Account -> Category: Convert EC2 Classic to VPC and raise a request. We will review your request, your existing AWS services and EC2-Classic presence and guide you through the next steps.
Let me know if this helped. Also, please click Accept answer for both the answers if it helped you.
The issue and the scenario sounds a bit strange due to it not being visible in the VPC console or the Instances in the console. Are you sure the EC2 instances are not present and the EC2 Classic are still present despite you moving them ? Can you do the below ?
Use the EC2 Classic Resource Finder script to find all of the EC2-Classic resources in your account. You can run this directly in a single AWS account, or you can use the included multi-account-wrapper to run it against each account of an AWS Organization. The Resource Finder visits each AWS Region, looks for specific resources, and generates a set of CSV files.
This will show you if you ve got any Classic resources. Also, make sure you check the console correctly for any EC2 instances.
At the end, if there is still ambiguity, I would reach out to AWS Support and check for discrepancies on what they can see using the internal tools.
Hope this helps !!
EC2 to VPC Migration.Accepted Answerasked 2 months ago
Errors migrating EC2 classic instances to VPCasked 2 months ago
How can i be sure i'm using EC2-VPC and not EC2-Classic?asked a month ago
EC2 to VPC migration -> can't tell what service we need to migrateasked 4 days ago
How to migrate my "m1.small" reserved instances to "t3.small"?Accepted Answerasked 5 months ago
Change platform of EC2 instanceasked 6 months ago
EC2 Linux instance unresponsible/unreachableasked 4 months ago
Migration of EC2, EBS-Backed instances to VPC - IssuesAccepted Answerasked a month ago
Error with EC2 Classic migration to VPC - paravirtualasked a month ago
Disable EC2 Classic from my account and move to VPCasked 2 years ago