Amazon Web Services

Technical definition

AWS is a portfolio of infrastructure and platform services delivered from geographically distributed Regions, each built from multiple physically and logically isolated Availability Zones. Compute, storage, database, networking, identity and monitoring services are provisioned and controlled through authenticated calls to a common set of web-service APIs, which are in turn exposed through a browser console, a command-line interface, software development kits and infrastructure-as-code tooling. Because AWS adds, changes and retires individual services and features on an ongoing basis, any claim about a specific service’s current behaviour, defaults or pricing should be checked against dated, service-specific AWS documentation rather than treated as fixed.

Operational relevance

Practitioners work with AWS wherever a workload’s compute, storage or networking is hosted on it. Day-to-day operational concerns include provisioning resources with least-privilege identity and access management, keeping test workloads bounded to an isolated account or project during validation, monitoring usage and cost, and confirming that a configuration change behaves as intended before it is relied upon. Because AWS is billed by consumption and some resource types remain reachable from the public internet by default, operational discipline around access scope and change validation is a correctness concern as well as a cost concern.

Architecture relationship

AWS sits at the infrastructure and platform layer beneath application architecture. Internally and externally, its services communicate using standard Internet Protocol addressing and routing; the RFC Series published by the RFC Editor is the authoritative reference for the underlying Internet standards that this networking relies on, although it does not describe AWS itself. Above this infrastructure layer, practitioners typically add identity and access control boundaries, orchestration or container tooling, and application code; the physical data centres and network backbone beneath a customer account are operated by AWS and are not directly observable from within that account.

Example

A bounded, low-risk way to become familiar with AWS is to create a dedicated, non-production account or an isolated project boundary within an existing account, provision a single storage resource and a single compute resource inside it, confirm through the console or a read-only describe or list operation that each resource has only the access it needs, and then remove both resources once the exercise is complete. Kept within an isolated boundary, with no production data or credentials involved, this exercise demonstrates provisioning, access review and clean-up without requiring any state-changing command against a shared or production environment.

Misunderstanding

A common misunderstanding is treating “AWS” as a single product with one consistent default configuration. In practice, AWS is a large portfolio of independently versioned services, and default behaviour, such as whether a newly created resource is reachable from outside its account, can differ between services and can change over time. A related misunderstanding is assuming that because a service reports as configured or enabled, it is therefore behaving as intended; specific default settings and current service behaviour should be confirmed against current, dated AWS documentation rather than assumed from general familiarity with the platform.

Related terms

• Cloud computing
• Infrastructure as a Service (IaaS)
• Region and Availability Zone
• Identity and Access Management (IAM)
• Virtual Private Cloud (VPC)
• Cloud service provider

Further reading

The RFC Series, maintained by the RFC Editor, is the authoritative reference for the Internet standards that underpin networking on AWS and on comparable platforms. For AWS-specific service behaviour, defaults, pricing and version history, consult AWS’s own current official documentation directly, since service details change frequently and individual service claims were not independently verified for this entry.

• RFC Editor, RFC Series