3 ms·

I have several production services running right now on AWS t2 instances, which were released in 2016. For a service that isn't performance-critical, it's perfe

I have several production services running right now on AWS t2 instances, which were released in 2016. For a service that isn't performance-critical, it's perfectly fine (and a significant cost savings) to run on decade-old hardware. ECC vs non-ECC is also pretty irrelevant on a box with < 64GB of memory

atherton94027 2mo ago
A t2 instance is virtualized, AWS keeps its servers for 5 years (see their 10k https://www.sec.gov/ix?doc=/Archives/edgar/data/1018724/000101872425000004/amzn-20241231.htm https://www.sec.gov/ix?doc=/Archives/edgar/data/1018724/0001... ), so your t2 does get moved around regularly to newer servers. And no, ECC is relevant with less than 64 gigs of ram, there's a reason it's been a standard on servers since the 90s