By using AWS re:Post, you agree to the Terms of Use

EC2 to VPC migration -> can't tell what service we need to migrate



regarding the dismissal of non-VPC instances, we keep getting the notice about resources running on EC2 and don't get what service is the 'culprit'.

We have:

  • 1 EC2 instance (the name being vpc-XXX so I assume is ok)
  • 1 RDS instance (the name being vpc-XXX so I assume is ok)

In addition to that we also have:

  • 1 S3 instance
  • 3 Elastic ip
  • Security Groups
  • some volumes
  • subnet masks
  • key pairs

Is it possible that one of said services triggers the notice? Is there a way to 'filter' them and tell for sure what resource we need to migrate?

Any help would be greatly apreciated.

Thank you


1 Answer

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.

profile picture
answered 12 days ago
profile picture
reviewed 12 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions