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

t4g.medium

EC2 Instance

ARM-based burstable performance instance with 2 vCPUs and 4 GiB memory. Balanced resources for applications with variable CPU usage.

Coming Soon...

icon
Pricing of
t4g.medium

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
t4g.medium

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
t4g.medium
FeatureSpecification
icon
Storage features of
t4g.medium
FeatureSpecification
icon
Networking features of
t4g.medium
FeatureSpecification
icon
Operating Systems Supported by
t4g.medium
Operating SystemSupported
icon
Security features of
t4g.medium
FeatureSupported
icon
General Information about
t4g.medium
FeatureSpecification
icon
Benchmark Test Results for
t4g.medium
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 387.0MB
AES-256 CBC 287.4MB
MD5 768.0MB
SHA256 2.8GB
SHA512 722.2MB
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 3099 3099
Average 3097 3094
Deviation 3.36 4.42
Min 3089 3083

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
t4g.medium
AI-summarized insights
filter icon
Filter by:
All

Amazon EC2 T4g instances are powered by Arm-based custom built AWS Graviton2 processors and deliver up to 40% better price performance over T3 instances for a broad set of burstable general purpose workloads.

28-10-2024
benchmarking, graviton, cost_savings

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

It\'s the same for t4g.

2023-09-10 00:00:00
benchmarking

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

Thank you ! Do you know if it\'s optimized for ECS ?

2021-07-22 00:00:00

Do you know how it compares to t3a?Edit: nvm: $0.0336/h for t4g.medium vs $0.0376/h t3a.medium in aws-east north virginia for on demand. Sucks not available in aws-southeast-1 yet, I would switch just for the performance bump over t*a instance.

2020-09-15 00:00:00
benchmarking

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

The instance type was changed in the order of t4g.medium → m6g.medium → t4g.medium. After changing the instance type, the first number of CPU credits recorded was approximately 12. As a result, no CPU credits were lost.

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

General purpose workloads with moderate CPU, memory, and network utilization.Save up to 40% over T3 instance pricing

2025-10-03 00:00:00
memory_usage

I started one EC2 of m6g.medium. I changed the instance type of that EC2 to t4g.medium. I think that when you change the instance type, the count starts from 0.

2025-10-03 00:00:00
benchmarking

T4g instances feature the same credits system, AWS Nitro System, and Burstable mode as T3 instances.

2025-10-03 00:00:00
benchmarking

AWS re:Invent 2020: Reduce cost with Amazon EC2’s next-generation T4g and T3 instance types

2021-05-02 00:00:00
cost_savings

Thank you. I was nearly clueless.

2022-12-01 00:00:00

Ok. I\'ll check.

2021-07-22 00:00:00

Here is a documentation page that you can add to your answer with more details on AMI, included ECS optimized Amazon Linux 2 : docs.aws.amazon.com/fr_fr/AmazonECS/latest/developerguide/… Unfortunately arm64 AMI for Amazon Linux 2 is not available in all regions.

2021-07-22 00:00:00
development

Thank you ! Do you know if it\'s optimized for ECS ?

2021-07-22 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

It\'s the same for t4g.

2023-09-10 00:00:00
benchmarking

So that would mean Unlimited is not a setting available for T4g (ARM instance) and therefore _may_ explain inconsistent behavior in the ARM instance.

2023-09-10 00:00:00
benchmarking

Specifications and performance for Amazon EC2 - t4g.medium

2025-10-03 00:00:00
benchmarking

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

The next-generation T4g instances, powered by AWS Graviton2, enable up to 40% higher performance than T3 for times when you need performance as well as 20% lower cost.

2021-05-02 00:00:00
benchmarking, graviton, cost_savings

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

It\'s the same for t4g.

2023-09-10 00:00:00
benchmarking

So that would mean Unlimited is not a setting available for T4g (ARM instance) and therefore _may_ explain inconsistent behavior in the ARM instance.

2023-09-10 00:00:00
benchmarking

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Ok. I\'ll check.

2021-07-22 00:00:00

Thank you. I was nearly clueless.

2022-12-01 00:00:00

Here is a documentation page that you can add to your answer with more details on AMI, included ECS optimized Amazon Linux 2 : docs.aws.amazon.com/fr_fr/AmazonECS/latest/developerguide/… Unfortunately arm64 AMI for Amazon Linux 2 is not available in all regions.

2021-07-22 00:00:00
development

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Thank you ! Do you know if it\'s optimized for ECS ?

2021-07-22 00:00:00

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

In my experience, t4.large offers slightly higher performance than t3.large and is also more cost-effective.

2023-12-15 00:00:00
benchmarking, cost_savings

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

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

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

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

It\'s the same for t4g.

2023-09-10 00:00:00
benchmarking

So that would mean Unlimited is not a setting available for T4g (ARM instance) and therefore _may_ explain inconsistent behavior in the ARM instance.

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 key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

In my experience, t4.large offers slightly higher performance than t3.large and is also more cost-effective.

2023-12-15 00:00:00
benchmarking, cost_savings

I think the key thing to understand here is that with little to no traffic, it absolutely will not make a difference and thus you should go with the cheapest (in this case t4g) option available.

2023-10-23 00:00:00
cost_savings

Additionally, t4g is an ARM-based processor, and it may not support some of the programs or scripts that you already have.

2023-12-15 00:00:00
memory_usage, graviton

I ran the popular Geekbench 5 benchmark against t3.medium, t3a.medium and t4g.medium

21/2/2023

We ran the tests for T3.medium vs T3.small vs T4g.medium vs T4g.small AWS RDS PostgreSQL instances and found out that all of them were very similar when it came to the speed of write/read operations when you're performing an operation that is supposed to take a short time ~ 1-5 seconds.

Load More
Similar Instances to
t4g.medium

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.