t1.micro

If you have these servers types already, we would recommend that you upgrade them to the newer T2 instance types. It is quite common for these more modern generation server instances to be cheaper.

You can count t2 as upgrade of t1. In general t2 offer faster access to memory and disk compared to t1.

AWS regularly gets better hardware over the years. T1, T2, T3, T4 correspond to these hardware updates; you\'re never better off using an older one. Use the most recent generation; they\'re faster and either cheaper or the same price.

The general idea behind this is instead of provisioning one large server for peak load, you have a larger number of smaller servers that scale up and down automatically to meet load. You put your servers behind an application load balancer. This also gives you redundancy, in case something goes wrong with one server. 54 t2.nano is an odd recommendation. Maybe it\'s optimal but it\'s not intuitive. It also means each server has very little RAM, which might not work for the application. t instances can also run out of CPU credits, so I wouldn\'t use them behind a load balancer.

I should clarify, "single t1.micro".

Back when I worked at AWS and t1s were still the big thing, we had a policy of telling customers to never run a production site on a t1.micro .

There\'s a different physical hardware underneath too. For example t2 uses \"Up to 3.3 GHz Intel Xeon Scalable processor (Haswell E5-2676 v3 or Broadwell E5-2686 v4)\", while t3 uses \"Up to 3.1 GHz Intel Xeon Scalable processor (Skylake 8175M or Cascade Lake 8259CL)\" and t3a \"AMD EPYC 7000 series processors (AMD EPYC 7571) with an all core turbo clock speed of 2.5 GHz\" you can find the full details at or search for the tech specs.

t1.micro is still available.

You\'re right. But T1 instances are no longer available. They are replaced by t2 and other members of the T family.

The link you have in your post is exactly the link I shared in my question. I do not see any mention of t1 in that link and that is why I asked this question.

You can count t2 as upgrade of t1. In general t2 offer faster access to memory and disk compared to t1.

AWS regularly gets better hardware over the years. T1, T2, T3, T4 correspond to these hardware updates; you\'re never better off using an older one. Use the most recent generation; they\'re faster and either cheaper or the same price.

When I try to create a new EC2 instance, there are many instance types to select from: t1.micro, t2.nano, t2.micro, etc. To understand the differences between t1, t2, t3, etc. I go to but the documentation here has no mention of T1. What are the differences between t1 and t2 instances?

I should clarify, "single t1.micro".

Back when I worked at AWS and t1s were still the big thing, we had a policy of telling customers to never run a production site on a t1.micro .

Like all hosting within Amazon, the individual instances are completely unreliable. You need to make sure that you can recreate your nodes from scratch at any point.

Storage is only EBS, which means you have to pay $0.10/GB per month above the cost of the instance time.

With appropriate caching strategies, these machines are more than capable of running a low traffic website. Using Apache Bench, I was able to get 1000 rpm out of the front page of this blog.

CPU time is very limited. CPU bursts can only be very brief and it appears that you are penalized when you exceed your quota.

I should clarify, "single t1.micro". Some customers just really refused to do any autoscaling config at all, so best we could do is show them how to backup and restore. But it's true that t1s really were very inconsistent in performance compared to the other families.

t1.micro is still available.

It's perfectly safe to run a production site on a t1.micro, as long as you follow good principles regarding monitoring and autoscaling.

Back when I worked at AWS and t1s were still the big thing, we had a policy of telling customers to never run a production site on a t1.micro .

Did any of you consider the fact that a t1.micro, m1.small etc can be 32 bit architecture and that a large instance is 64 bit arc ? Will it not cause any problems ? As of now, I think we will have to do everything again (create a new large instance and install all the application again) ? Is it not the case when there is a change in architecture ?

That just bit me in the a**. Last time I will choose 32 bit for anything. Now we have a server that needs more memory that 4gb and the 32 bit architecture can\'t handle it. If fact in the Amazon Control Panel in EC2 there is no option to launch to a large type, it only goes up to medium.

You\'re right. But T1 instances are no longer available. They are replaced by t2 and other members of the T family.

The link you have in your post is exactly the link I shared in my question. I do not see any mention of t1 in that link and that is why I asked this question.

There\'s a different physical hardware underneath too. For example t2 uses \"Up to 3.3 GHz Intel Xeon Scalable processor (Haswell E5-2676 v3 or Broadwell E5-2686 v4)\", while t3 uses \"Up to 3.1 GHz Intel Xeon Scalable processor (Skylake 8175M or Cascade Lake 8259CL)\" and t3a \"AMD EPYC 7000 series processors (AMD EPYC 7571) with an all core turbo clock speed of 2.5 GHz\" you can find the full details at or search for the tech specs.

You can count t2 as upgrade of t1. In general t2 offer faster access to memory and disk compared to t1.

AWS regularly gets better hardware over the years. T1, T2, T3, T4 correspond to these hardware updates; you\'re never better off using an older one. Use the most recent generation; they\'re faster and either cheaper or the same price.

When I try to create a new EC2 instance, there are many instance types to select from: t1.micro, t2.nano, t2.micro, etc. To understand the differences between t1, t2, t3, etc. I go to but the documentation here has no mention of T1. What are the differences between t1 and t2 instances?

I forgot to say, our current setup is an old desktop machine running an Intel i7 quadcore CPU @3.073Ghz, with 24Gb or Ram. It’s happily supporting our 20 vms (normally 10 running at any one time).