Skip to Content
Cloud Engineering Academy

Glossary

Nearly 200 AWS and cloud terms in plain language, A to Z — each with its Microsoft/Azure equivalent where one exists and the module that teaches it.

Verified against official sources on 2026-11-17.

Short, plain-language definitions. Each entry gives the Azure / Microsoft equivalent where one exists (≈ means "similar, not identical") and the module where the topic is taught properly. For a service-by-service translation table, see Microsoft / Azure → AWS.

Jump to: A · B · C · D · E · F · G · H · I · K · L · M · N · O · P · Q · R · S · T · V · W · X · Z

A

Access key — A long-term key pair (access key ID + secret) belonging to an IAM user, used to sign API calls. Avoid them: they leak into Git and never expire on their own. Use roles and IAM Identity Center sign-in instead. Azure ≈ service principal client secret. → M0, M5

ACM (AWS Certificate Manager) — Issues and auto-renews TLS certificates for load balancers, CloudFront and API Gateway. Public certificates for those services are free. Azure ≈ App Service managed certificates / Key Vault certificates. → M5

ADOT (AWS Distro for OpenTelemetry) — AWS's supported distribution of OpenTelemetry SDKs and the collector, preconfigured to send traces to X-Ray and metrics to CloudWatch. The recommended way to instrument new .NET code. Azure ≈ Azure Monitor OpenTelemetry distro. → M11

ALB (Application Load Balancer) — A layer-7 (HTTP/HTTPS) load balancer that routes by path, host name or header to targets such as ECS tasks, EC2 instances, IP addresses or Lambda functions. Azure ≈ Application Gateway. → M2, M3

Amazon MQ — A managed message broker running Apache ActiveMQ or RabbitMQ. Used to lift-and-shift apps that speak JMS, AMQP, MQTT or STOMP. Azure ≈ Service Bus (AMQP) or self-hosted RabbitMQ; replaces IBM MQ-style brokers. → M8

AMI (Amazon Machine Image) — The template an EC2 instance boots from: operating system, installed software and settings. Azure ≈ VM image / Shared Image Gallery. → M1

API Gateway (Amazon API Gateway) — A managed front door for APIs. It offers REST APIs (feature-rich), HTTP APIs (cheaper, simpler) and WebSocket APIs, with throttling, authorizers and logging. Azure ≈ API Management. → M4

App Runner (AWS App Runner) — A "container in, URL out" hosting service. Closed to new customers since 2026-04-30; AWS recommends ECS Express Mode instead. Azure ≈ Container Apps / App Service for containers. → M3

AppConfig (AWS AppConfig) — Manages feature flags and dynamic configuration, with validation and gradual rollout that can roll back automatically on an alarm. Not for secrets. Azure ≈ App Configuration. → M3

Application Signals (CloudWatch Application Signals) — An application-performance view in CloudWatch that builds service maps, latency/error dashboards and SLOs from OpenTelemetry data. Azure ≈ Application Insights. → M11

ARN (Amazon Resource Name) — The globally unique ID of an AWS resource, in the form arn:partition:service:region:account-id:resource. Used in IAM policies to say exactly which resource a permission covers. Azure ≈ resource ID. → M1

At-least-once delivery — A guarantee that a message will be delivered, possibly more than once. SQS standard, SNS and EventBridge work this way, so consumers must be idempotent. → M8

Athena (Amazon Athena) — Serverless SQL over files in S3 (CSV, JSON, Parquet, Iceberg). You pay per data scanned, so columnar formats and partitions matter. Azure ≈ Synapse serverless SQL pool. → M7

Aurora (Amazon Aurora) — AWS's cloud-built relational database, compatible with PostgreSQL or MySQL. Storage is replicated six ways across three AZs; options include Serverless v2 and Global Database. Azure ≈ Azure Database for PostgreSQL (Flexible Server) / Azure SQL Hyperscale. → M6

Auto Scaling — Automatically adds or removes capacity (EC2 instances, ECS tasks, DynamoDB throughput, Aurora replicas) to follow demand, usually by tracking a target metric. Azure ≈ VM Scale Sets autoscale / App Service autoscale. → M12

Availability Zone (AZ) — One or more physically separate data centres inside a Region, with independent power and networking. Spreading across two or three AZs is how you survive a data-centre failure. Azure ≈ availability zone. → M1

AWS Backup — Central, policy-driven backup for RDS, DynamoDB, EBS, EFS, S3 and more, with vaults, cross-account/cross-Region copies and Vault Lock (WORM). Azure ≈ Azure Backup. → M12

B

Babelfish for Aurora PostgreSQL — A capability that lets Aurora PostgreSQL understand SQL Server's wire protocol (TDS) and much of T-SQL, so some SQL Server apps can connect with fewer code changes. Available and actively released as of 2026; test your workload, because coverage is not complete. Azure ≈ none. → M6, M13

Bedrock (Amazon Bedrock) — A managed service for calling foundation models from several providers through one API, with Knowledge Bases (RAG) and Guardrails. Agents are built on Amazon Bedrock AgentCore (the older Bedrock Agents, now Agents Classic, closed to new customers on 2026-07-30). Azure ≈ Azure OpenAI / AI Foundry. → M16

Blue/green deployment — Run the new version ("green") next to the old ("blue"), shift traffic once it is healthy, and keep blue for instant rollback. Azure ≈ deployment slot swap. → M9

Bucket policy — A resource-based policy attached to an S3 bucket that says who may do what to it — for example, deny any request not using TLS. → M5

Budgets (AWS Budgets) — Alerts when actual or forecast spend crosses a threshold; can also trigger actions. Set one up before your first lab. Azure ≈ Cost Management budgets. → M0, M15

C

CDK (AWS Cloud Development Kit) — Define infrastructure in C# (or TypeScript, Python, Java, Go); the CDK turns it into a CloudFormation template and deploys it. Azure ≈ Bicep, but in real C#. → M10

Change set — A preview of what a CloudFormation stack update will add, modify or replace, reviewed before you run it. Azure ≈ what-if for ARM/Bicep. → M10

CIDR block — A way of writing an IP range, such as 10.0.0.0/16 (65,536 addresses). VPCs and subnets are sized with CIDR blocks; overlapping ranges cannot be connected later, so plan them centrally. Azure ≈ VNet address space. → M2

Circuit breaker — A resilience pattern: after repeated failures to a dependency, stop calling it for a while and fail fast. In .NET, use Polly / Microsoft.Extensions.Http.Resilience. → M4, M12

CloudFormation (AWS CloudFormation) — AWS's native infrastructure-as-code engine. You describe resources in JSON/YAML templates; CloudFormation creates them as a stack and tracks their state. Azure ≈ ARM templates. → M10

CloudFront (Amazon CloudFront) — AWS's content delivery network: caches content at edge locations and fronts websites and APIs, with WAF and Shield integration. Azure ≈ Front Door / Azure CDN. → M12

CloudHSM (AWS CloudHSM) — Dedicated, single-tenant hardware security modules in your VPC, for when regulation requires keys in an HSM you control. Azure ≈ Managed HSM / Dedicated HSM. → M5

CloudShell (AWS CloudShell) — A browser-based shell in the console with the AWS CLI already signed in as you. Azure ≈ Azure Cloud Shell. → M0

CloudTrail (AWS CloudTrail) — Records API calls made in your accounts: who, what, when, from where. The backbone of audit and incident investigation. Azure ≈ Activity Log (plus resource logs). → M5, M11

CloudWatch (Amazon CloudWatch) — AWS's monitoring service: metrics, alarms, dashboards, logs (CloudWatch Logs), Logs Insights queries, synthetic canaries and Application Signals. Azure ≈ Azure Monitor. → M11

CMK (customer managed key) — A KMS key you create and control: you write its key policy, enable rotation and can disable it. Contrast with AWS managed keys (created by a service for you). Banks normally require CMKs for sensitive data. Azure ≈ customer-managed key in Key Vault. → M5

CodeBuild (AWS CodeBuild) — Runs build and test commands in a fresh container per build, with an IAM role. Azure ≈ Azure Pipelines build job / hosted agent. → M9

CodeCommit (AWS CodeCommit) — AWS's managed Git hosting. Closed to new customers in 2024 but back in general availability since 2025-11-24. Most teams still use GitHub. Azure ≈ Azure Repos. → M9

CodeDeploy (AWS CodeDeploy) — Automates deployments to EC2, ECS and Lambda, including blue/green and canary traffic shifting with automatic rollback. Azure ≈ release pipeline deployment jobs. → M9

CodePipeline (AWS CodePipeline) — Orchestrates a release: source → build → test → approve → deploy. Azure ≈ multi-stage Azure Pipelines. → M9

Cognito (Amazon Cognito) — Customer identity: user pools handle sign-up, sign-in, MFA and issue OAuth 2.0/OIDC tokens; identity pools swap tokens for temporary AWS credentials. Azure ≈ Entra External ID / Azure AD B2C. → M4, M5

Cold start — The extra delay when Lambda (or a new container) must start a fresh execution environment and load your code before handling a request. For .NET, reduce it with SnapStart, Native AOT, smaller packages and less start-up work. Azure ≈ Functions Consumption cold start. → M3

Config (AWS Config) — Records the configuration history of your resources and evaluates them against rules (e.g. "all EBS volumes encrypted"). Detective, not preventive. Azure ≈ Azure Policy (audit) + Resource Graph change history. → M5, M15

Construct (CDK) — A reusable building block in CDK. L1 = raw CloudFormation resource, L2 = sensible defaults and helper methods, L3 = a whole pattern (e.g. load-balanced Fargate service). → M10

Control Tower (AWS Control Tower) — Sets up and governs a multi-account landing zone: log-archive and audit accounts, guardrails ("controls") and an account vending process. Azure ≈ Azure Landing Zones. → M15

Cost Explorer — Charts and filters your AWS spend by service, account, tag and time. Azure ≈ Cost analysis. → M15

D

Data Firehose (Amazon Data Firehose) — Loads streaming data into S3, Redshift, OpenSearch and others in batches, optionally converting to Parquet. Formerly Kinesis Data Firehose. Azure ≈ Event Hubs Capture. → M7

Data lake — A central store (on AWS, usually S3) holding raw and processed data in open formats, catalogued so many tools can query it. Azure ≈ ADLS Gen2. → M7

Detective (Amazon Detective) — Builds a graph of activity from CloudTrail, VPC Flow Logs and GuardDuty to help investigate security findings. Azure ≈ Sentinel investigation graph. → M5

Direct Connect (AWS Direct Connect) — A private, dedicated network circuit between your data centre and AWS. Azure ≈ ExpressRoute. → M2

DLQ (dead-letter queue) — A side queue where messages go after failing processing a set number of times, so one bad "poison" message doesn't block the rest. You inspect and redrive them later. Azure ≈ Service Bus dead-letter sub-queue. → M8

DMS (AWS Database Migration Service) — Copies data between databases, including ongoing change data capture (CDC), e.g. on-prem SQL Server → RDS or → S3. Azure ≈ Azure Database Migration Service. → M6, M13

DMS Schema Conversion / AWS SCT — Tools that convert schema and code (e.g. SQL Server → PostgreSQL). DMS Schema Conversion is the managed web version; the desktop AWS Schema Conversion Tool remains available for sources and features the managed one doesn't cover. → M6, M13

Drift — When real infrastructure no longer matches its IaC definition because someone changed it by hand. CloudFormation has drift detection; Terraform shows drift in terraform plan. → M10

DynamoDB (Amazon DynamoDB) — A serverless key-value and document database with single-digit-millisecond reads at any scale. You design tables around access patterns (partition key + sort key). Azure ≈ Cosmos DB (NoSQL API) / Table Storage. → M6

DynamoDB Streams — An ordered change log of item-level writes to a DynamoDB table, which can trigger Lambda. Azure ≈ Cosmos DB change feed. → M6, M8

E

EBS (Amazon Elastic Block Store) — Network-attached disks for EC2 instances, living in one AZ. Azure ≈ Managed Disks. → M1

EC2 (Amazon Elastic Compute Cloud) — Virtual servers (Linux or Windows) you control fully, including the OS. Azure ≈ Virtual Machines. → M1, M3

ECR (Amazon Elastic Container Registry) — A private Docker/OCI image registry with vulnerability scanning and lifecycle rules. Azure ≈ Azure Container Registry. → M3

ECS (Amazon Elastic Container Service) — AWS's own container orchestrator. Simpler than Kubernetes; runs containers on Fargate (serverless) or on EC2 instances you manage. Azure ≈ Container Apps (roughly). → M3

ECS Express Mode — An ECS capability that, from a container image and two IAM roles, creates a Fargate service, ALB, auto scaling and a URL in one step — at no extra charge beyond those resources. AWS's recommended replacement for App Runner. Azure ≈ Container Apps quick create. → M3

ECS service — Keeps a desired number of copies of a task running, replaces failed ones, registers them with a load balancer and handles rolling or blue/green deployments. Azure ≈ a Container App with min replicas. → M3

ECS task / task definition — A task definition is the blueprint (images, CPU, memory, ports, env vars, secrets, IAM roles); a task is one running copy. The task role is what your code uses to call AWS; the execution role is what ECS uses to pull images and fetch secrets. → M3

Edge location — A CloudFront / Route 53 point of presence close to users, used for caching and DNS — not for running your servers. → M1

EFS (Amazon Elastic File System) — A managed NFS file system that many Linux instances or containers can mount at once. Azure ≈ Azure Files (NFS). → M6

EKS (Amazon Elastic Kubernetes Service) — Managed Kubernetes. Choose it when your organisation already standardises on Kubernetes. Azure ≈ AKS. → M3

Elastic Beanstalk (AWS Elastic Beanstalk) — A platform service: upload a .NET app (Windows/IIS or Linux) and it provisions EC2, load balancer and scaling, with managed platform updates. Still current and receiving .NET platform updates in 2026. Azure ≈ App Service. → M3

Elastic IP — A static public IPv4 address you own in your account. Charged hourly (as are all public IPv4 addresses), so release unused ones. → M2

ElastiCache (Amazon ElastiCache) — Managed in-memory caching with Valkey, Redis OSS or Memcached, including a serverless option. Azure ≈ Azure Cache for Redis / Azure Managed Redis. → M6

ELB (Elastic Load Balancing) — The family name for AWS load balancers: ALB (HTTP), NLB (TCP/UDP/TLS) and Gateway Load Balancer (for network appliances). → M2

EMF (Embedded Metric Format) — A JSON log format that CloudWatch automatically turns into metrics — write a log line, get a metric, no extra API call. Powertools for AWS Lambda (.NET) uses it. → M11

Envelope encryption — Encrypt data with a fresh data key, then encrypt that data key with a KMS key and store it next to the data. KMS only ever handles the small key, so large data stays fast to encrypt. Azure ≈ Key Vault wrap/unwrap key. → M5

EventBridge (Amazon EventBridge) — A serverless event bus. Services and apps publish events; rules match on content and route to targets (Lambda, SQS, Step Functions, APIs). Includes archive/replay, schema registry, Pipes and Scheduler. Azure ≈ Event Grid. → M8

EventBridge Pipes — Point-to-point connection from a source (SQS, Kinesis, DynamoDB Streams…) to a target, with optional filtering and enrichment, without writing glue code. → M8

EventBridge Scheduler — Runs one-off or recurring schedules (cron/rate) that invoke targets with retries and a DLQ. Azure ≈ timer-triggered Functions / Logic Apps recurrence. → M3

Eventual consistency — Copies of data converge "shortly", so a read right after a write may see old data. Default for DynamoDB reads (strongly consistent reads are optional) and for cross-Region replication. → M6

Exactly-once processing — The effect of a message is applied once even if it is delivered twice. Achieved with SQS FIFO deduplication, Step Functions Standard, or — most often — idempotent consumers. → M8

F

Fargate (AWS Fargate) — Serverless compute for containers: you specify CPU and memory per task; AWS runs it without you managing servers. Works with ECS and EKS. Azure ≈ Container Apps / Container Instances compute. → M3

FIFO queue — An SQS queue type that preserves order within a message group and removes duplicates within a 5-minute deduplication window. Lower throughput than standard queues. Azure ≈ Service Bus sessions. → M8

FIS (AWS Fault Injection Service) — Runs controlled chaos experiments: stop instances, add latency, throttle APIs — with stop conditions. Azure ≈ Chaos Studio. → M12

Flow Logs (VPC Flow Logs) — Records accepted and rejected network traffic metadata for a VPC, subnet or network interface. Azure ≈ NSG / VNet flow logs. → M2

FSx for Windows File Server (Amazon FSx) — Managed Windows SMB file shares joined to Active Directory. Azure ≈ Azure Files (SMB). → M13

G

Gateway endpoint — A free VPC endpoint type, for S3 and DynamoDB only, added as a route so private subnets can reach those services without a NAT Gateway. Azure ≈ service endpoint. → M2

Glue (AWS Glue) — Serverless data integration: Spark/Python ETL jobs, crawlers that discover schemas, Glue Studio visual editor and Data Quality rules. Azure ≈ Data Factory + mapping data flows. → M7

Glue Data Catalog — A central metadata store (databases, tables, schemas, partitions) used by Athena, Redshift Spectrum, EMR and Lake Formation. Azure ≈ Purview catalog / Synapse lake database metadata. → M7

Global tables (DynamoDB) — A DynamoDB table replicated to several Regions, each accepting writes. → M12

GuardDuty (Amazon GuardDuty) — Managed threat detection that analyses CloudTrail, VPC Flow Logs, DNS logs and more for signs of compromise (e.g. credential misuse, crypto-mining). Azure ≈ Defender for Cloud threat protection. → M5

H

Health check — A probe that decides whether a target is healthy: ALB target-group checks, ECS container health checks, Route 53 health checks. Separate liveness (restart me) from readiness (send me traffic). Azure ≈ App Service health check / Application Gateway probes. → M3

Hosted zone — A Route 53 container for DNS records of one domain; public zones answer the internet, private zones answer only inside chosen VPCs. Azure ≈ Azure DNS zone / private DNS zone. → M2

I

IaC (infrastructure as code) — Defining infrastructure in version-controlled files that a tool deploys repeatably. On AWS: CloudFormation, CDK, Terraform. → M10

IAM (AWS Identity and Access Management) — Decides who (principal) can do what (action) to which resource (ARN) under which conditions. Every AWS API call is evaluated by IAM. Azure ≈ Azure RBAC (but policy-document based). → M5

IAM Access Analyzer — Finds resources shared outside your account or organisation, validates policies and can generate least-privilege policies from CloudTrail activity. → M5

IAM group — A collection of IAM users that share policies. Rarely needed once people sign in through IAM Identity Center. Azure ≈ security group used for role assignment. → M5

IAM Identity Center (AWS IAM Identity Center) — Workforce single sign-on across all accounts in your organisation. Connect it to Entra ID or AD, then give people permission sets per account. Azure ≈ Entra ID sign-in to subscriptions. → M0, M5

IAM policy — A JSON document of Effect / Action / Resource / Condition statements. Identity-based policies attach to users/roles; resource-based policies attach to resources (bucket, key, queue). Azure ≈ role definition + assignment. → M5

IAM role — An identity with permissions but no password or long-term keys. Something trusted assumes it and gets temporary credentials — an EC2 instance, an ECS task, a Lambda function, a person via SSO, or GitHub Actions via OIDC. Azure ≈ managed identity. → M5

IAM user — A long-lived identity in one account with a password and/or access keys. Avoid for people and workloads; keep only for rare break-glass or legacy cases. Azure ≈ a cloud-only user. → M5

Iceberg (Apache Iceberg) — An open table format on top of Parquet files that adds ACID transactions, schema evolution, time travel and safe updates/deletes to a data lake. Supported by Athena, Glue, EMR and Redshift. Azure ≈ Delta Lake tables. → M7

Idempotency — Doing the same operation twice has the same effect as doing it once. Essential for payments: retries and duplicate messages must not move money twice. Implement with idempotency keys and conditional writes. → M4, M8

IGW (internet gateway) — Attaches to a VPC and lets resources with public IPs in public subnets reach the internet and be reached. Azure ≈ default internet routing of a VNet. → M2

Inspector (Amazon Inspector) — Continuously scans EC2 instances, ECR images and Lambda functions for known vulnerabilities (CVEs) and network exposure. Azure ≈ Defender vulnerability management. → M5

Instance profile — The wrapper that hands an IAM role to an EC2 instance, so code on the instance gets temporary credentials automatically. Azure ≈ system-assigned managed identity on a VM. → M5

Interface endpoint — A VPC endpoint powered by PrivateLink: a private IP in your subnet that reaches an AWS service (or a partner's service) without the internet. Billed per hour per AZ plus data. Azure ≈ Private Endpoint. → M2

K

Key policy — The resource policy on a KMS key. Every key must have one, and IAM permissions only work if the key policy allows the account to delegate to IAM. A common cause of AccessDeniedException. → M5

Kinesis Data Streams (Amazon Kinesis Data Streams) — An ordered, replayable stream split into shards; many consumers can read the same data independently. Azure ≈ Event Hubs. → M7, M8

Kiro — AWS's agentic IDE and CLI for spec-driven development; the successor to Amazon Q Developer's IDE plugins. Azure ≈ GitHub Copilot (agent mode). → M16

KMS (AWS Key Management Service) — Creates and controls encryption keys inside HSM-backed infrastructure; keys never leave KMS. Most AWS services encrypt with KMS keys, and every use is logged in CloudTrail. Azure ≈ Key Vault keys. → M5

L

Lake Formation (AWS Lake Formation) — Adds fine-grained permissions (database, table, column, row, tag-based) on top of the Glue Data Catalog, enforced for Athena, Redshift Spectrum, EMR and Glue. Azure ≈ Purview data policies / Synapse column- and row-level security. → M7

Lambda (AWS Lambda) — Runs your function in response to events without servers. .NET uses the managed dotnet10 runtime (or a container/custom runtime). Max 15 minutes per invocation; billed per request and per millisecond × memory. Azure ≈ Azure Functions. → M3

Lambda authorizer — A Lambda function API Gateway calls to decide whether a request is allowed (e.g. validate a custom token) and return an IAM policy. → M4

Lambda layer — A zip of libraries or data shared by several functions. Less useful in .NET (NuGet packages are bundled), but used for extensions. → M3

Landing zone — A pre-configured, secure multi-account AWS environment (accounts, networking, logging, guardrails) that new workloads move into. → M15

Least privilege — Grant only the permissions needed, for only as long as needed. In AWS: specific actions, specific ARNs, conditions, and short-lived role credentials. → M5

Lifecycle policy — Rules that move or delete objects automatically: S3 objects to cheaper storage classes, or old untagged images out of ECR. Azure ≈ Blob lifecycle management. → M6

Long polling — An SQS receive call that waits up to 20 seconds for messages instead of returning empty immediately, cutting cost and empty responses. → M8

M

Macie (Amazon Macie) — Discovers and classifies sensitive data (PII, credentials, financial data) in S3 buckets. Azure ≈ Purview data classification. → M5

Managed Microsoft AD (AWS Directory Service for Microsoft AD) — A real Microsoft Active Directory run by AWS across two AZs; can trust your on-prem AD. Needed for FSx for Windows, domain-joined EC2 and Windows auth to RDS SQL Server. Azure ≈ Entra Domain Services. → M13

Managed policy — An IAM policy that exists as its own object and can be attached to many identities. AWS managed policies are written by AWS (often too broad); customer managed ones are yours. → M5

MFA (multi-factor authentication) — A second factor (authenticator app, FIDO2 security key) on top of a password. Mandatory for the root user and all humans. → M0

MGN (AWS Application Migration Service) — Replicates servers block-by-block into AWS and launches them as EC2 instances for rehost migrations. Azure ≈ Azure Migrate server migration. → M13

MSK (Amazon Managed Streaming for Apache Kafka) — Managed Apache Kafka clusters (provisioned) or MSK Serverless (no broker sizing; available and expanding to more Regions in 2026). Azure ≈ Event Hubs Kafka endpoint / Confluent on Azure. → M7, M8

Multi-AZ — Running a resource with a synchronous standby (RDS) or spread across AZs (ECS, ALB) so it survives an AZ failure. Azure ≈ zone-redundant deployment. → M12

N

NACL (network ACL) — A stateless allow/deny list applied at the subnet boundary; return traffic must be allowed explicitly. Usually left fairly open, with security groups doing the fine-grained work. Azure ≈ NSG on a subnet (but stateless). → M2

NAT Gateway — Lets resources in private subnets start outbound connections to the internet without being reachable from it. Charged per hour and per GB — a frequent bill surprise. Azure ≈ NAT Gateway. → M2

Native AOT — Compiling .NET ahead of time to a native binary: faster start and smaller memory, but no runtime code generation and stricter trimming rules. Useful against Lambda cold starts. → M3

Network Firewall (AWS Network Firewall) — Managed stateful firewall with IPS and domain filtering, typically in a central inspection VPC. Azure ≈ Azure Firewall. → M2

NLB (Network Load Balancer) — A layer-4 load balancer for TCP/UDP/TLS with very high throughput, static IPs per AZ and client IP preservation. Azure ≈ Azure Load Balancer. → M2

O

Object Lock (S3 Object Lock) — Write-once-read-many protection for S3 objects for a retention period or legal hold. Compliance mode can't be shortened by anyone. Azure ≈ immutable blob storage. → M5

OIDC federation — Letting an external identity provider (GitHub Actions, Entra ID, Cognito) exchange its token for temporary AWS role credentials, so no AWS keys are stored. Azure ≈ workload identity federation. → M9

OpenTelemetry (OTel) — The vendor-neutral standard for traces, metrics and logs. On AWS use it via ADOT; it replaces the X-Ray SDKs (in maintenance mode since 2026-02-25). Azure ≈ Azure Monitor OpenTelemetry. → M11

Organizations (AWS Organizations) — Groups AWS accounts under a management account, with OUs, consolidated billing and organisation-wide policies (SCPs, RCPs, tag and backup policies). Azure ≈ management groups + tenant. → M15

OU (organizational unit) — A folder of accounts inside Organizations (e.g. Security, Workloads-Prod, Sandbox) to which policies attach. Azure ≈ management group. → M15

Outbox pattern — Save the business change and an "event to publish" row in the same database transaction, then publish from the outbox table separately. Avoids losing or inventing events when there is no distributed transaction (no DTC on AWS). → M8

P

Parameter Store (AWS Systems Manager Parameter Store) — Hierarchical key/value storage for configuration and simple secrets (SecureString, encrypted with KMS). Standard tier is free; no built-in rotation. Azure ≈ App Configuration / Key Vault secrets. → M3

Parquet (Apache Parquet) — A compressed, columnar file format. Queries read only needed columns, so Athena scans (and bills) far less than with CSV. → M7

Partition key — The attribute DynamoDB hashes to decide where an item lives (and, in data lakes, the folder-style column such as date=2026-11-17 that lets queries skip files). A poor choice causes "hot" partitions. → M6, M7

Permission boundary — An IAM policy that caps the maximum permissions an IAM user or role can ever have, whatever other policies say. Used to let teams create roles safely. → M5

Permission set — In IAM Identity Center, a template of policies that becomes a role in each account a person or group is assigned to. → M5

Pilot light — A DR strategy where the core (data replication, minimal infrastructure) runs in the recovery Region and the rest is scaled up during a disaster. → M12

PrivateLink (AWS PrivateLink) — Technology for reaching a service privately through interface endpoints in your VPC, without internet, peering or NAT. Also lets you publish your own service to other accounts. Azure ≈ Private Link. → M2

Private subnet — A subnet with no route to an internet gateway; resources there are unreachable from the internet. Databases and app tasks belong here. → M2

Provisioned concurrency — Lambda execution environments kept initialised and ready, removing cold starts for that capacity — billed even when idle. Azure ≈ Functions Premium pre-warmed instances. → M3

Public subnet — A subnet whose route table sends internet traffic to an internet gateway. Put only load balancers, NAT Gateways and bastion-like endpoints here. → M2

Q

Q Developer (Amazon Q Developer) — AWS's AI coding assistant. New sign-ups blocked since 2026-05-15; IDE plugins reach end of support on 2027-04-30. Kiro is the successor; Q in the AWS console continues. → M16

Quick Sight (Amazon Quick Sight) — AWS's BI dashboards service, formerly QuickSight, now part of the Amazon Quick suite (⚠ VERIFY current branding). Azure ≈ Power BI. → M7

R

RCP (resource control policy) — An Organizations policy that caps what can be done to resources in member accounts (e.g. "S3 buckets can only be accessed by principals in our organisation"), whoever is asking. Complements SCPs. → M5, M15

RDS (Amazon Relational Database Service) — Managed SQL Server, PostgreSQL, MySQL, MariaDB, Oracle and Db2: AWS handles provisioning, patching, backups, Multi-AZ failover. You lose OS and sysadmin access. Azure ≈ Azure SQL Managed Instance / Azure Database for PostgreSQL. → M6

RDS Proxy — A managed connection pool in front of RDS/Aurora that absorbs connection storms (e.g. from Lambda) and speeds up failover. → M6

Read replica — An asynchronously updated, read-only copy of a database for scaling reads or DR. Reads may lag slightly. Azure ≈ readable secondary / geo-replica. → M6

Redshift (Amazon Redshift) — A columnar data warehouse (provisioned or Serverless) for large analytical SQL. Azure ≈ Synapse dedicated SQL pool. → M7

Region — A geographic area (e.g. eu-west-2 London) containing several AZs. Data stays in the Region you choose unless you copy it out. Azure ≈ region. → M1

Resource-based policy — A policy attached to a resource (S3 bucket, KMS key, SQS queue, Lambda function) naming who may access it — including other accounts. → M5

Rotation (secret / key rotation) — Replacing a credential or key on a schedule. Secrets Manager rotates secrets via a Lambda function (managed for RDS); KMS rotates key material automatically while keeping old versions for decryption. → M5

Route 53 (Amazon Route 53) — AWS's DNS service with health checks and routing policies (failover, weighted, latency, geolocation). Azure ≈ Azure DNS + Traffic Manager. → M2

Route table — Rules in a VPC deciding where traffic from a subnet goes (local, internet gateway, NAT, Transit Gateway, endpoint). A subnet is "public" or "private" only because of its route table. Azure ≈ user-defined routes. → M2

RPO (recovery point objective) — How much data you can afford to lose, measured in time (e.g. "at most 5 minutes of transactions"). Drives backup and replication design. → M12

RTO (recovery time objective) — How long the service may be down before it must be restored (e.g. "back within 1 hour"). Drives the DR strategy and cost. → M12

S

S3 (Amazon Simple Storage Service) — Object storage: files ("objects") in buckets, addressed by key, designed for eleven nines of durability. Basis of data lakes, backups and static sites. Azure ≈ Blob Storage. → M1, M7

S3 Block Public Access — Account- and bucket-level switches that override any policy or ACL making data public. On by default for new buckets; keep it on. → M5

S3 storage classes — Price/access trade-offs: Standard, Intelligent-Tiering, Standard-IA, One Zone-IA, Glacier Instant/Flexible/Deep Archive. Azure ≈ hot/cool/cold/archive tiers. → M6

Saga pattern — Managing a business transaction across services as a sequence of local steps, each with a compensating step to undo it on failure. Orchestrated (e.g. Step Functions) or choreographed (events). → M8

SAM (AWS Serverless Application Model) — A shorthand template format and CLI for serverless apps, including local testing (sam local). → M3

Savings Plans — A commitment to spend a fixed amount per hour on compute for 1 or 3 years in exchange for lower prices. Azure ≈ Azure savings plan / reservations. → M15

SCP (service control policy) — An Organizations policy that caps what principals in member accounts can do (e.g. deny leaving approved Regions, deny disabling CloudTrail). It grants nothing; it only limits. → M5, M15

Secrets Manager (AWS Secrets Manager) — Stores, encrypts (KMS), versions, replicates and rotates secrets like database passwords and API keys; apps fetch them at runtime. Charged per secret per month. Azure ≈ Key Vault secrets. → M3, M5

Security group (SG) — A stateful virtual firewall on a network interface; allow rules only. Rules can reference other security groups (e.g. "DB accepts 1433 only from the app SG"). Azure ≈ NSG / application security group. → M2

Security Hub (AWS Security Hub) — Aggregates and correlates security findings across GuardDuty, Inspector, Macie and posture checks, with risk prioritisation. The original posture-checking service was renamed Security Hub CSPM when the new unified Security Hub went GA (2025-12). Azure ≈ Defender for Cloud. → M5

Session Manager (Systems Manager Session Manager) — Shell/RDP-style access to instances through the SSM agent, with no inbound ports, no bastion and full session logging. Azure ≈ Azure Bastion. → M2

Shared Responsibility Model — AWS secures the cloud (hardware, facilities, managed-service internals); you secure what you put in it (data, IAM, configuration, code). → M1, M5

Shield (AWS Shield) — DDoS protection. Standard is automatic and free; Advanced adds tailored protection, cost protection and a response team, for a fee. Azure ≈ DDoS Protection. → M5

SigV4 (Signature Version 4) — How every AWS API request is signed with your credentials so AWS can verify who sent it and that it wasn't altered. The SDK does it for you. → M4

SnapStart (Lambda SnapStart) — Lambda snapshots your initialised function and restores from it on cold start, cutting start-up time. Supported for .NET 8 and later managed runtimes. → M3

SNS (Amazon Simple Notification Service) — Pub/sub: publish once to a topic, and it pushes copies to all subscribers (SQS, Lambda, HTTPS, email, SMS), with filter policies. Azure ≈ Service Bus topics / Event Grid. → M8

Spot Instances — Spare EC2 capacity at a large discount that AWS can reclaim with a two-minute warning. Fine for batch, never for the only copy of a payment service. → M15

SQS (Amazon Simple Queue Service) — A fully managed message queue. Producers send; consumers poll, process and delete. Standard (at-least-once, best-effort order) or FIFO. Azure ≈ Service Bus queues / Storage queues; replaces MSMQ. → M8

Stack (CloudFormation stack) — A set of resources created, updated and deleted together from one template. StackSets deploy the same stack to many accounts and Regions. → M10

Step Functions (AWS Step Functions) — Serverless workflow orchestration as a state machine: retries, error handling, parallel branches, human approval, direct calls to 200+ services. Standard (long, exactly-once steps) or Express (short, high-volume). Azure ≈ Durable Functions / Logic Apps. → M8

STS (AWS Security Token Service) — Issues temporary credentials when a role is assumed (AssumeRole, AssumeRoleWithWebIdentity). GetCallerIdentity tells you "who am I?" — your first debugging command. → M5

Subnet — A slice of a VPC's IP range inside one AZ. Public, private or isolated depending on its route table. Azure ≈ subnet (but Azure subnets span zones). → M2

Systems Manager (AWS Systems Manager) — Operations toolbox: Session Manager, Patch Manager, Run Command, Parameter Store, inventory and automation runbooks. Azure ≈ Azure Automation + Update Manager + Arc. → M11

T

Tag — A key/value label on a resource (CostCentre=Payments, Environment=prod). Used for cost allocation, automation and attribute-based access control. Azure ≈ tags. → M15

Target group — The set of targets (tasks, instances, IPs, Lambda) a load balancer forwards to, with its own health check. → M2

Terraform — HashiCorp's multi-cloud IaC tool (HCL language, BSL licence; OpenTofu is the open-source fork). Uses the aws provider to manage AWS. → M10

Terraform state — The JSON file where Terraform records which real resources it manages. Store it remotely (S3, encrypted, versioned, with locking), restrict access — it can contain secrets — and never edit it by hand. → M10

Throttling — Rejecting requests above a rate limit (HTTP 429 or ThrottlingException). AWS APIs throttle you; you throttle clients with API Gateway or WAF. Retry with exponential backoff and jitter. → M4

Transfer Family (AWS Transfer Family) — Managed SFTP, FTPS, FTP and AS2 endpoints storing files directly in S3 or EFS. Azure ≈ Blob Storage SFTP. → M4, M7

Transit Gateway (AWS Transit Gateway) — A regional network hub connecting many VPCs and on-prem networks with central routing. Azure ≈ Virtual WAN hub. → M2

Trust policy — The resource policy on an IAM role saying who may assume it (a service, another account, an OIDC provider). Permissions policies say what the role can do once assumed. → M5

TTL (DynamoDB time to live) — A per-item expiry timestamp after which DynamoDB deletes the item automatically, at no cost. Handy for idempotency records. → M6

V

Valkey — An open-source, Redis-compatible in-memory data store (Linux Foundation). ElastiCache and MemoryDB offer it, typically cheaper than Redis OSS. → M6

Visibility timeout (SQS) — After a consumer receives a message, SQS hides it from others for this long (default 30 s, up to 12 h). If not deleted in time, it reappears and is processed again — set it longer than your processing time. Azure ≈ Service Bus peek-lock duration. → M8

VPC (Amazon Virtual Private Cloud) — Your private, isolated network in a Region, with your IP range, subnets, route tables and gateways. Azure ≈ Virtual Network (VNet). → M2

VPC endpoint — Private connectivity from a VPC to AWS services: gateway endpoints (S3, DynamoDB; free) or interface endpoints (most services; PrivateLink; hourly). Endpoint policies can restrict which resources are reachable. → M2

VPC Link — Lets API Gateway reach private resources (ALB/NLB, Cloud Map services) inside your VPC. → M4

VPC peering — A private, non-transitive connection between two VPCs. For many VPCs, use Transit Gateway. Azure ≈ VNet peering. → M2

W

WAF (AWS WAF) — A web application firewall for CloudFront, ALB, API Gateway REST APIs, Cognito and more: managed rule groups (OWASP-style), rate-based rules, geo and IP rules, bot control. Azure ≈ Azure WAF. → M4, M5

Warm standby — A DR strategy with a scaled-down but fully working copy of production running in another Region, scaled up on failover. Lower RTO than pilot light, higher cost. → M12

Well-Architected Framework — AWS's six-pillar design guidance (operational excellence, security, reliability, performance efficiency, cost optimisation, sustainability), with lenses such as the Financial Services Industry Lens. Azure ≈ Azure Well-Architected Framework. → M1, M12

X

X-Ray (AWS X-Ray) — Distributed tracing: follow one request across API Gateway, Lambda, ECS and databases, with a service map. Send data with OpenTelemetry (ADOT); the X-Ray SDKs and daemon are in maintenance mode until end of support on 2027-02-25. Azure ≈ Application Insights distributed tracing. → M11

Z

Zero trust — Never trust a request because of where it comes from on the network; authenticate and authorise every request (identity, device, context). On AWS: IAM everywhere, private endpoints, SigV4, mTLS, Verified Access. → M5

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page