AWS · Infrastruttura · YoctoIT tech page

EC2

AWS compute: virtual machines for every workload, from microservices to in-memory databases — with Graviton processors for the best price/performance.

FOCUS · RIGHT-SIZINGInstances chosen on real numbers: paying the right amount is a continuous activity, not a one-off
YoctoIT material for clients and partners · AWS e i nomi dei servizi sono marchi di Amazon.com, Inc.
01 · What it is

Amazon EC2 & Graviton, made clear.

EC2 is the building block of the AWS cloud: hundreds of instance types (compute, memory, storage, GPU) in dozens of sizes, up in minutes and paid by use. With Graviton (AWS's custom ARM) performance per euro rises noticeably for compatible workloads.

600+
instance types available: the right size exists, it must be chosen
Graviton
up to ~40% better price/performance on compatible workloads (source: AWS)
99,99%
availability SLA for multi-AZ architectures
Icona ufficiale AWS — Amazon EC2 & Graviton
OFFICIAL AWS ICON · EC2
02 · How to use it well

The things that make the difference.

How it comes together

Auto Scaling Groupcapacity that follows the load
On-demand instances
Reserved / Savings Plans
Spot
the right mix cuts the bill
AMIs & Launch Templatesgolden images and repeatable configuration
Nitro Systemhardware virtualization: near bare-metal performance
AWS compute at a glance

Families for every job

M for general purpose, C for compute, R for memory, I for NVMe storage, G/P for GPUs: the choice affects costs and performance.

Graviton

AWS's ARM processors (now Graviton4): same services, less spend — the first thing we evaluate in an assessment.

Smart purchasing

On-demand for the unpredictable, Savings Plans for the stable, Spot for the recomputable: the mix is where you really save.

Nitro System

AWS's hardware hypervisor: minimal overhead, security in the silicon and tenant isolation.

03 · In depth

Families, Nitro and smart purchasing

Instances are chosen by family (M general purpose, C compute, R memory, I storage, G/P GPU) and generation: the suffix matters — 'g' is Graviton (ARM), 'i' Intel, 'a' AMD. Underneath it all is Nitro: a minimal hypervisor on dedicated hardware, freeing near bare-metal performance and isolating security. Purchasing is a strategy: on-demand for the unpredictable, Savings Plans/Reserved for the base, Spot (up to -90%) for the interruptible.

  • Nitro System — hypervisor on a dedicated card: minimal overhead, encryption and isolation in hardware
  • Graviton4 — 96-core ARM: up to 40% better price/performance on compatible workloads
  • Savings Plans — a flexible $/hour commitment across family and region: the discount without the rigidity of old RIs
  • Spot — unused capacity at -70/90%: batch and workers with managed interruption (2-minute notice)
  • Placement group — cluster, spread or partition: the topology for HPC or anti-affinity
  • EBS gp3 — IOPS and throughput independent of size: the right default, not gp2
04 · Numbers and lifecycle

The numbers that matter.

750+
the instance types in the catalog: the size exists, it must be chosen
-90%
the maximum Spot saving on interruptible workloads
2 min
the Spot interruption notice to handle
99,99%
the regional SLA for multi-AZ instances
The EC2 bill is designed: right-sizing with CloudWatch data, Savings Plans on the base and Spot on batch — we calculate the mix.
05 · Use cases

Where it really pays off.

Lift-and-shift

The first step of migration: the VM as it was, but elastic and replicable across zones.

Seasonal peaks

Capacity that switches on for the campaign or month-end and off afterwards: you pay for use, not for the peak.

Test environments

Entire environments created and destroyed on command: testing without dedicated iron.

Continuous right-sizing from our NOC: instances observed, resized and repurchased on the right plan — the cloud costs what it should.