AWS EC2

Technical Definition

AWS EC2 is a compute service within Amazon Web Services that provisions virtual machine instances on shared physical hosts, using hypervisor-based virtualisation to isolate each instance from others on the same underlying hardware. An instance is defined by an instance type (a fixed combination of virtual CPU, memory and network capacity), a machine image supplying the operating system and initial software, one or more attached storage volumes, and a network configuration inside a Virtual Private Cloud (VPC). Instances are controlled through the AWS API, command-line tools or the AWS Management Console, and can be started, stopped, resized or terminated independently of the physical hardware beneath them. Exact instance family names, generations, hypervisor implementation details and pricing structures change over time; this entry does not assert current values for those details and they should be confirmed against AWS’s own current documentation before being relied upon in a specific design.

Operational Relevance

Practitioners use AWS EC2 as the general-purpose compute layer beneath many other systems: application servers, batch processing nodes, self-managed databases and infrastructure for container orchestration platforms commonly run on EC2 instances. Its operational relevance sits in three areas:

• Capacity control — instances can be scaled up, scaled down or replaced without procuring new physical hardware.
• Cost and lifecycle management — instances are billed for the time they run, so stopping unused instances and selecting an appropriate instance type materially affects operating cost.
• Shared responsibility — AWS operates and secures the underlying physical infrastructure and hypervisor layer, while the account owner is responsible for the guest operating system, application configuration, network exposure and the identity permissions attached to each instance.

Architecture Relationship

EC2 does not operate in isolation; it is one component inside a wider AWS account architecture. Instances are launched inside a VPC subnet, so their network reachability depends on route tables, security groups and network access control lists configured separately from EC2 itself. Storage is normally provided by Elastic Block Store (EBS) volumes or instance-local storage rather than by EC2 directly. Identity and Access Management (IAM) roles attached to an instance determine what AWS APIs the software running on that instance may call, which makes IAM configuration a material part of an instance’s effective security boundary. Load balancers, auto scaling groups and container platforms are commonly layered above EC2 to manage groups of instances collectively rather than individually, and this layering is usually where operational complexity accumulates.

Example

A team running a stateless web application might place several EC2 instances of the same instance type in a private subnet, attach them to an Auto Scaling group so the number of running instances adjusts with demand, and route incoming traffic to them through a load balancer rather than exposing each instance directly to the internet. The instances read configuration and secrets through a dedicated IAM role rather than from long-lived credentials stored on the instance itself.

Misunderstanding

A common misunderstanding is treating an EC2 instance as equivalent to a fully managed service: EC2 provisions the virtual machine, but the account owner remains responsible for operating system patching, application-level security configuration and monitoring, unless those responsibilities are explicitly delegated to another managed service layered on top. Another frequent error is assuming that stopping an instance removes all associated cost; attached EBS volumes and reserved capacity commitments can continue to accrue charges even while an instance is stopped, and this should be confirmed against current AWS billing documentation rather than assumed.

Related Terms

• Amazon Machine Image (AMI) — the template used to launch an EC2 instance.
• Elastic Block Store (EBS) — the block storage volumes commonly attached to EC2 instances.
• Virtual Private Cloud (VPC) — the network environment in which EC2 instances are placed.
• Auto Scaling group — a mechanism for managing the number of running EC2 instances automatically.
• Identity and Access Management (IAM) role — the mechanism controlling what an EC2 instance’s software is permitted to do.

Further Reading

Readers evaluating an EC2-based design should confirm current instance types, pricing and API behaviour directly against AWS’s own published service documentation before relying on specific figures, since AWS revises these details on an ongoing basis. Organisations without direct access to current AWS documentation at the time of review should treat instance-family and pricing specifics in this entry as indicative only and escalate to a reviewer with access to current AWS sources before using them for procurement or capacity decisions.