5 ms·
EC2 vs EC2-classic. I got badly burned (mentally) because I had to learn about creating EC2 instances using the company AWS account created before 2014, but the
by rikroots 6y ago
EC2 vs EC2-classic. I got badly burned (mentally) because I had to learn about creating EC2 instances using the company AWS account created before 2014, but then needed to create instances on a client account created in 2014.
Also: classic vs application load balancers - especially the health checks. That one drove me nuts for weeks!
AWS never seems to "deprecate" anything, but they do enjoy adding services which are very similar to other services but guaranteed to trip people (ie: me) up when it comes to the buried-in-the-documentation details.
- jto1218 6y agothe main thing here though is the older things you’re moving away from in those cases are still around. AWS didn’t remove classic load balancers and force you onto application load balancers.
- rikroots 6y agoAgreed. But they did deprecate EC2-Classic. "The EC2-Classic platform was introduced in the original release of Amazon EC2. If you created your AWS account after 2013-12-04, it does not support EC2-Classic." https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-classic-platform.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-clas...
- zwily 6y agoYeah but this is the customer-friendly way to deprecate - let existing users keep using the old method indefinitely, new users have to use the new way.
- calcifer 6y ago> after 2013-12-04 That was 4 years after VPC was launched. So yes, while they do deprecate stuff on the rarest of occasions, they still give you much, much more time than GCP ever did. Also, EC2-Classic is still available if you reach out to your TAM with a really good reason.