Learn how Palo Alto Networks is Transforming Platform Engineering with AI Agents. Register here

Attend a Live Product Tour to see Sedai in action.

Register now
More
Close
AWS

t2.large

EC2 Instance

Burstable performance instance with 2 vCPUs and 8 GiB memory. Higher memory allocation for more demanding applications.

Coming Soon...

icon
Pricing of
t2.large

N/A

On Demand

N/A

Spot

N/A

1 Yr Reserved

N/A

3 Yr Reserved

Pricing Model
Price (USD)
% Discount vs On Demand
sedai

Let us help you choose the right instance

Schedule a meeting
icon
Spot Pricing Details for
t2.large

Here's the latest prices for this instance across this region:

Availability Zone Current Spot Price (USD)
Frequency of Interruptions: n/a

Frequency of interruption represents the rate at which Spot has reclaimed capacity during the trailing month. They are in ranges of < 5%, 5-10%, 10-15%, 15-20% and >20%.

Last Updated On: December 17, 2024
icon
Compute features of
t2.large
FeatureSpecification
icon
Storage features of
t2.large
FeatureSpecification
icon
Networking features of
t2.large
FeatureSpecification
icon
Operating Systems Supported by
t2.large
Operating SystemSupported
icon
Security features of
t2.large
FeatureSupported
icon
General Information about
t2.large
FeatureSpecification
icon
Benchmark Test Results for
t2.large
CPU Encryption Speed Benchmarks

Cloud Mercato tested CPU performance using a range of encryption speed tests:

Encryption Algorithm Speed (1024 Block Size, 3 threads)
AES-128 CBC N/A
AES-256 CBC N/A
MD5 N/A
SHA256 N/A
SHA512 N/A
I/O Performance

Cloud Mercato's tested the I/O performance of this instance using a 100GB General Purpose SSD. Below are the results:

Read Write
Max 3156 3110
Average 3096 3093
Deviation 9.97 5.53
Min 3090 3088

I/O rate testing is conducted with local and block storages attached to the instance. Cloud Mercato uses the well-known open-source tool FIO. To express IOPS the following parametersare used: 4K block, random access, no filesystem (except for write access with root volume and avoidance of cache and buffer.

icon
Community Insights for
t2.large
AI-summarized insights
filter icon
Filter by:
All

the T series is more suitable for non-performance-verified test environments

19-03-2025
benchmarking

the T series is more suitable for non-performance-verified test environments

19-03-2025
benchmarking

T2 is a burstable instance type If you run out of CPU credits, CPU is throttled and performance degrades

19-06-2024
cpu_credits, benchmarking

I think the discrepancies can be attributed to the choice of the t-style instances. They are generally over committed.

2023-09-10 00:00:00
benchmarking

Aren\'t \'t\' instances burst instances? They need to be under constant load for a long time before their burst credits for CPU, memory, network and EBS run out, after which they fall back on their baseline performance.

2023-09-10 00:00:00
memory_usage, benchmarking

I think the discrepancies can be attributed to the choice of the t-style instances. They are generally over committed.

2023-09-10 00:00:00
benchmarking

Aren\'t \'t\' instances burst instances? They need to be under constant load for a long time before their burst credits for CPU, memory, network and EBS run out, after which they fall back on their baseline performance.

2023-09-10 00:00:00
memory_usage, benchmarking

Thank you for this article. We have T instances for EC2 and RDS and we are expecting some very strange performance behavior. Do you have plan to test RDS?

2025-10-03 00:00:00
benchmarking

This is super well documented by aws themselves and if you understood how they work before creating the article then you probably would not have written it. Please do research before writing scare articles just for clicks. That’s just lame brother.

2025-10-03 00:00:00

Thank you for this article. We have T instances for EC2 and RDS and we are expecting some very strange performance behavior. Do you have plan to test RDS?

2025-10-03 00:00:00
benchmarking

This is super well documented by aws themselves and if you understood how they work before creating the article then you probably would not have written it. Please do research before writing scare articles just for clicks. That’s just lame brother.

2025-10-03 00:00:00

I think the discrepancies can be attributed to the choice of the t-style instances. They are generally over committed.

2023-09-10 00:00:00
benchmarking

Aren\'t \'t\' instances burst instances? They need to be under constant load for a long time before their burst credits for CPU, memory, network and EBS run out, after which they fall back on their baseline performance.

2023-09-10 00:00:00
memory_usage, benchmarking

T2 instances do not have Unlimited mode turned on by default. Without Unlimited mode turned on, once the CPU credits have been exhausted, the server goes into a shallow resource usage state. Its CPU performance and network performance are lessened considerably until the CPU credits have accumulated again. We've seen this first hand on quite a few occasions now, even causing production outages.

2025-10-03 00:00:00
cpu_credits, benchmarking

Thank you for this article. We have T instances for EC2 and RDS and we are expecting some very strange performance behavior. Do you have plan to test RDS?

2025-10-03 00:00:00
benchmarking

This is super well documented by aws themselves and if you understood how they work before creating the article then you probably would not have written it. Please do research before writing scare articles just for clicks. That’s just lame brother.

2025-10-03 00:00:00

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

2022-07-23 00:00:00
memory_usage, benchmarking

I remember there is a thread talking about whether aws over-sell their cpus. If I can not get consistent 100% cpu usage then it is. But whatever it its, the \"40%\" and \"60%\" in the video still strange and can not be clearly explained.

2019-08-04 00:00:00
benchmarking

But it\'s a fact that the hardware specs for e.g. `t2.large` and `m4.large` are either exactly or roughly the same. That means even if you burst on a `t2` you will get the same performance as on `m4`.

2019-06-04 00:00:00
benchmarking

Could you explain how can t2 get 60% higher than m4? From t2 instance document, the \"bursting\" is from baseline to 100%, not higher. Just now I launched a t2.medium and a m4.large, made a test using sysbench in ubuntu, they gave almost the same performance.

2016-12-12 00:00:00
benchmarking

I have made cpu benchmarks and m4.large result was same with t2.large burst..

2019-06-04 00:00:00
benchmarking

But with t2.large, you can only use 60% of a single vcpu, average 30% for each of the two vcpus. Even considering the \"cpu credits\", t2.large seems far weak than m4.large.

2016-11-12 00:00:00
cpu_credits, benchmarking

This is false information. Instance retirement event is just host maintenance event. NOT THE replacement process.

2025-02-26 00:00:00

So, there is no specific date to end support for older instance type, they are retired gradually and we are only notified through scheduled events?

2024-10-03 00:00:00

For detailed information on the process and implications of instance retirement, please refer to the following resource: [Understanding Instance Retirement on AWS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-retirement.html). Additional [Scheduled events for your instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html)

2024-10-05 00:00:00

That's a great news! Thank you for the link

2024-10-03 00:00:00
Load More
Similar Instances to
t2.large

Consider these:

Feedback

We value your input! If you have any feedback or suggestions about this t4g.nano instance information page, please let us know.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.