What is the difference between AWS VPC and Classic?

We’re testing out our stack on an AWS VPC instance, but I’m curious about the benefits. I originally chose this only because we couldn’t get a T2 instance with Classic. I read Cloud66’s blog post on switching from Classic to VPC, but I think you guys have a much larger operation going on than we do.

So, I guess my questions are:

1) Is there a reason anything less than c3 instances aren’t available in AWS Classic?

2) Is a VPC going to be an issue down the road, seeing as having a subnet might be overkill for the moment?

Thanks in advance.

Thanks for getting in touch with us about this. AWS VPC allows you to have a logically-isolated section of AWS, so that you can launch resources (eg. servers) over your own virtual network. This can be useful for creating multi-tiered web applications, with subnets for each part of your application. You can read more about the features and benefits.

Amazon seem to be pushing people towards using VPC, so I believe we will see newer instance types/features only available there. This is the case with the T2 instance. VPC allows you to use more advanced features, such as Identity and Access Management (IAM) and others, so it can be useful. However, you do not have to use these features if you don’t want to.

From the Cloud 66 point of view, there is no difference for us if you use VPC or EC2, but we do recommend that you use VPC for the aforementioned reasons. We’re planning on adding features such as supporting subnets for different parts of your stack, among other things, so this would ensure maximum flexibility for the future.

I hope this clears up your questions. Please let us know if there’s anything else we can help with.

You must be logged in to answer this question