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

m3.medium

EC2 Instance

Previous generation general-purpose instance with 1 vCPU and 3.75 GiB memory. SSD-backed for better performance than M1 instances.

Coming Soon...

icon
Pricing of
m3.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
m3.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
m3.medium
FeatureSpecification
icon
Storage features of
m3.medium
FeatureSpecification
icon
Networking features of
m3.medium
FeatureSpecification
icon
Operating Systems Supported by
m3.medium
Operating SystemSupported
icon
Security features of
m3.medium
FeatureSupported
icon
General Information about
m3.medium
FeatureSpecification
icon
Benchmark Test Results for
m3.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 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 30046 Average
Average Deviation 0
Deviation 30046 N/A
Min N/A N/A

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

For longer sessions, more data traffic, or higher numbers of concurrent users, I'd consider the M3.

2015-05-31 00:00:00

A t2.medium is roughly 4x as powerful in all regards as a micro, and a m3.medium has similar RAM and bandwidth but less peak CPU. The instance storage will be a few times faster than a large EBS GP2 (SSD) volume on the m3.medium, of course.

2016-06-01 00:00:00
memory_usage, benchmarking

Also, you can further reduce costs with a higher number of low configuration machines, like m3.medium instead of higher configuration core/task nodes.

You can use a master node (m3.large or m4.large or even m3.medium) and at-least 2 core/task nodes (m4.xlarge or m3.xlarge or c4.2xlarge).

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk.

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk. It’s not hard to see why almost half of EC2 workloads [are on “m” instances].

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk. It’s not hard to see why almost half of EC2 workloads [are on “m” instances].

Load More
Similar Instances to
m3.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.