Amazon Q Business & Q Developer

🎓 Build AI Skills with Google
Learn practical AI skills and earn a Google Certificate. No experience required – learn at your own pace.
Start the Google AI Essentials Learning Path →

Amazon Q Business Overview

  • Amazon Q Business is a fully managed generative AI assistant for enterprises that can answer questions, provide summaries, generate content, and take actions based on enterprise data.
  • Connects to 40+ enterprise data sources (S3, SharePoint, Confluence, Slack, Salesforce, Google Drive, Gmail, Jira, ServiceNow, databases, and more).
  • Provides secure, accurate answers grounded in company data with citations and source attribution.
  • Respects existing access controls and permissions — users only see answers from data they’re authorized to access (ACL-aware).
  • Previously known as “Amazon Q for Business” — rebranded as Amazon Q Business (GA April 2024).

Key Features

  • Enterprise Search — natural language search across all connected data sources with ranked results.
  • Conversational AI — multi-turn conversations with context retention.
  • Content Generation — draft emails, reports, summaries, blog posts based on enterprise data.
  • Document Summarization — summarize long documents, meeting transcripts, and reports.
  • Actions & Plugins — perform tasks like creating Jira tickets, sending emails, updating Salesforce records.
  • Custom Plugins — build custom actions using OpenAPI schemas.
  • Amazon Q Apps — no-code app builder for creating lightweight gen-AI applications from natural language descriptions.
  • Data Insights — ask questions about structured data (databases, spreadsheets) with auto-generated visualizations.

Data Sources & Connectors

  • AWS Sources: S3, RDS, Aurora, Redshift, DynamoDB, WorkDocs
  • Collaboration: Slack, Microsoft Teams, Confluence, SharePoint Online, Google Drive
  • Productivity: Gmail, Outlook, OneDrive, Box, Dropbox
  • CRM/ITSM: Salesforce, ServiceNow, Zendesk
  • Development: Jira, GitHub, GitLab
  • Databases: PostgreSQL, MySQL, SQL Server, Oracle
  • Custom: Web Crawler, Custom connectors via API
  • Supports incremental sync — only indexes changed content.
  • 40+ pre-built connectors available.

Security & Access Control

  • ACL-aware retrieval — respects source system permissions (if a user can’t access a SharePoint doc, Q won’t use it in answers).
  • IAM Identity Center integration — SSO with corporate identity providers (Okta, Azure AD, Ping).
  • Encryption — data encrypted at rest (KMS, customer-managed keys supported) and in transit (TLS 1.2+).
  • VPC support — keep data connector traffic within VPC.
  • Admin controls — block specific topics, configure response behavior, set global/topic-level guardrails.
  • Audit logging — CloudTrail integration for all API calls.
  • Data retention — configurable conversation history retention.

Amazon Q Apps

  • No-code app builder — create gen-AI powered apps by describing them in natural language.
  • Apps can include: text generation, file upload, data queries, and custom actions.
  • App library — share apps across the organization.
  • Built on top of Q Business data and permissions.
  • Example apps: Meeting summarizer, FAQ generator, onboarding assistant, report builder.

Amazon Q Developer

  • Separate product from Q Business — focused on software development assistance.
  • Code generation — inline code suggestions in IDEs (VS Code, JetBrains, Visual Studio).
  • Code transformation — automated Java version upgrades (Java 8/11 → 17), .NET upgrades.
  • Chat — answer questions about AWS services, your codebase, and best practices.
  • /dev agent — implement features from natural language descriptions across multiple files.
  • /review — automated code review with security scanning.
  • AWS Console integration — troubleshoot errors, explain resources, generate CLI commands.
  • Customization — connect to private repositories for organization-specific suggestions.
  • Operational investigations — diagnose and resolve operational issues in AWS.

Amazon Q Business vs Amazon Bedrock

Feature Amazon Q Business Amazon Bedrock
Purpose Turnkey enterprise AI assistant Build custom gen-AI applications
Target User Business users, IT admins Developers, ML engineers
Customization Configure connectors, guardrails, plugins Full control: model selection, fine-tuning, agents, RAG
Data Integration 40+ pre-built connectors, automatic indexing Knowledge Bases (S3, web, custom), manual setup
Access Control ACL-aware (respects source permissions) IAM-based, manual implementation
Coding Required No (configuration only) Yes (API integration)
Use When Enterprise search, Q&A on company docs Custom AI apps, chatbots, content pipelines

Pricing

  • Q Business Lite — $3/user/month (search, Q&A, summaries).
  • Q Business Pro — $20/user/month (Lite features + plugins, actions, Q Apps, admin controls).
  • Q Developer Free Tier — limited code suggestions per month.
  • Q Developer Pro — $19/user/month (unlimited suggestions, /dev agent, code transformation).
  • Index pricing — based on document count and storage.

AWS Certification Exam Practice Questions

  1. A company wants employees to ask questions about internal policies, HR documents, and project wikis stored across SharePoint and Confluence. The solution must respect existing document permissions. Which service is most appropriate?
    1. Amazon Bedrock with Knowledge Bases
    2. Amazon Q Business
    3. Amazon Kendra
    4. Amazon Lex with Lambda
  2. A development team needs AI-assisted code reviews and the ability to automatically upgrade their Java 8 applications to Java 17. Which service provides this?
    1. Amazon Q Business
    2. Amazon CodeWhisperer
    3. Amazon Q Developer
    4. Amazon Bedrock Agents
  3. An organization using Amazon Q Business wants non-technical employees to create simple AI-powered apps (like a meeting summarizer) without writing code. Which feature enables this?
    1. Custom plugins
    2. Bedrock Flows
    3. Amazon Q Apps
    4. Bedrock Studio
  4. A security team needs to ensure that when employees use the company’s AI assistant, a junior analyst cannot receive answers from executive-level strategy documents they don’t have access to in SharePoint. How does Q Business handle this?
    1. Guardrails block the content category
    2. Admin manually configures document-level permissions
    3. ACL-aware retrieval automatically respects source system permissions
    4. IAM policies restrict Q Business API calls
  5. A company is choosing between Amazon Q Business and Amazon Bedrock Knowledge Bases for their internal document Q&A system. They have 40,000 employees, documents in 8 different systems, and no ML engineering team. Which should they choose?
    1. Bedrock Knowledge Bases (more flexible)
    2. Amazon Q Business (turnkey, 40+ connectors, no code needed)
    3. Amazon Kendra (purpose-built search)
    4. Custom RAG solution on EC2

Related Posts

References

Amazon Q Business User Guide

Amazon Q Developer User Guide

Amazon Q Business Product Page

Amazon Q Developer Product Page

Amazon Bedrock – Foundation Models & Generative AI

Amazon Bedrock – Fully Managed Foundation Models & Gen AI

Amazon Bedrock Overview

  • Amazon Bedrock is a fully managed service that provides access to high-performing foundation models (FMs) from leading AI companies through a single, unified API.
  • was announced at AWS re:Invent 2022 and became generally available in September 2023.
  • enables building and scaling generative AI applications without managing any infrastructure (serverless).
  • offers a broad set of capabilities including model access, customization (fine-tuning, continued pre-training), RAG with Knowledge Bases, Agents, Guardrails, and model evaluation.
  • ensures data privacy — your data is not shared with model providers and is not used to improve or train the base models.
  • supports multiple inference modes: on-demand, batch (50% cheaper), and provisioned throughput for consistent performance.
  • integrates with AWS services you already use — IAM, CloudWatch, CloudTrail, VPC, Lambda, S3, Step Functions, and more.
  • as of 2026, the model catalog spans 18+ providers and over 110 individually addressable model variants including language, reasoning, image, video, speech, and embedding models.
  • supports OpenAI-compatible API endpoints (2026) including Responses API and Chat Completions API for simplified migration from existing OpenAI-based applications.
Amazon Bedrock Architecture
Your Application
↓ Bedrock API ↓
Foundation Models
Claude, Nova, Llama, Mistral
Knowledge Bases
RAG → Vector Store
Agents
Tool Use, Multi-step
Guardrails
Filters, PII, Grounding
Fine-tuning
Model Evaluation
Prompt Flows
AgentCore
Fully managed • No infrastructure • Your data never leaves your account

📖 Deep Dive Guides: Bedrock vs SageMaker | RAG Architecture | Prompt Engineering | Responsible AI | AI Services Decision Guide

Supported Foundation Models

Amazon Bedrock provides access to a diverse selection of foundation models from multiple leading AI providers, allowing customers to choose the best model for their specific use case.

Model Providers Comparison

Provider Models Strengths Key Use Cases
Anthropic Claude Opus 4, Claude Sonnet 4/4.5, Claude Haiku 3.5 Advanced reasoning, coding, long context (200K–1M tokens), agentic tasks Complex analysis, code generation, enterprise workflows
Amazon Nova Micro, Lite, Pro, Premier, Nova 2 Lite/Pro, Nova Canvas, Nova Reel, Nova Sonic Best price-performance, multimodal (text, image, video, speech), fast inference Cost-efficient workloads, content generation, RAG, agentic apps
Meta Llama 3.3 70B, Llama 3.2 (11B/90B), Llama 3.1 (8B/70B/405B) Open-weight, strong reasoning, multilingual General-purpose, fine-tuning, on-device deployment
Mistral AI Mistral Large, Mistral Small, Mixtral Efficiency, multilingual, code generation European language tasks, coding, cost-optimized inference
Cohere Command R, Command R+ Enterprise search, RAG-optimized, multilingual Enterprise search, document processing, RAG applications
AI21 Labs Jamba 1.5 (Large/Mini), Jamba-Instruct Long context (256K), efficient architecture (SSM+Transformer hybrid) Document summarization, Q&A, long-form content
Stability AI Stable Diffusion XL, SDXL variants, image editing models High-quality image generation and editing Creative content, marketing visuals, design prototyping
OpenAI GPT models (added 2025–2026) Broad capabilities, coding, reasoning General-purpose AI, migration from OpenAI direct
DeepSeek DeepSeek-R1 Advanced reasoning, open-weight Math, science, complex reasoning tasks

Amazon Nova Foundation Models

  • Amazon Nova Micro — Text-only model optimized for speed (200+ tokens/sec) and lowest cost. 128K context. Ideal for summarization, translation, classification, and chat.
  • Amazon Nova Lite — Low-cost multimodal model (text, images, video input → text output). Best for document analysis, visual Q&A, and RAG.
  • Amazon Nova Pro — Balanced multimodal model offering strong accuracy, speed, and cost. Suitable for a wide range of complex tasks.
  • Amazon Nova Premier — Most capable model for complex reasoning, agentic workflows, and teacher model for distillation.
  • Amazon Nova Canvas — Image generation model with professional-grade outputs and customization controls.
  • Amazon Nova Reel — Video generation model supporting multi-shot videos up to 2 minutes with motion control.
  • Amazon Nova Sonic — Speech-to-speech model for conversational AI with natural turn-taking and expressivity.

Amazon Nova 2 (December 2025)

  • Nova 2 Lite and Nova 2 Pro — Next-generation models with significantly improved capabilities.
  • Support extended thinking with step-by-step reasoning and task decomposition.
  • Include three thinking intensity levels (low, medium, high) for controlling the balance of speed, intelligence, and cost.
  • Process up to 1M tokens of context, enabling analysis of extensive codebases, long documents, and videos.
  • Built-in tools: code interpreter, web grounding, and remote MCP tool support.
  • Nova 2 Sonic — Next-generation speech-to-speech model with expressive voices, native expressivity in multiple languages, natural turn-taking, and interruption handling.

Key Features

Model Access & Inference

  • Provides a unified API to access all foundation models — no need to manage separate integrations per provider.
  • Supports four families of runtime APIs:
    • Invoke family — InvokeModel (synchronous), InvokeModelWithResponseStream (streaming), InvokeModelWithBidirectionalStream (full-duplex), AsyncInvoke (long-running, output to S3).
    • Converse family — Model-agnostic interface for multi-turn conversations (Converse and ConverseStream).
    • OpenAI-compatible family — ChatCompletions and Responses API for migration from OpenAI-based apps.
    • Messages family — Anthropic Messages interface on the bedrock-mantle endpoint.
  • Supports cross-region inference with routing tiers: In-Region, Geo, and Global for optimized latency and availability.
  • Models can be swapped without rewriting application code thanks to the unified Converse API.

Model Customization

  • Fine-tuning — Supervised fine-tuning using labeled prompt-response pairs to improve model performance for specific use cases. Supports iterative fine-tuning for systematic refinement.
  • Continued Pre-training — Feed domain-specific unlabeled data to adapt a model’s knowledge to your industry (e.g., finance, healthcare, legal).
  • Reinforcement Fine-tuning (RFT) — Uses reinforcement learning from human or AI feedback (RLHF/RLAIF) to align model behavior with desired outcomes. Available for Nova, OpenAI GPT OSS, and Qwen models.
  • Model Distillation — Use a larger “teacher” model (e.g., Nova Premier) to create a smaller, more cost-effective “student” model with comparable accuracy.
  • Custom Model Import — Bring your own fine-tuned models (including open-weight models like DeepSeek-R1) into Bedrock for managed inference.
  • Creates a private copy of the model — your data is never shared with model providers.
  • Supports on-demand inference for custom models (no need to provision throughput for fine-tuned Amazon Nova models).

Knowledge Bases (RAG)

  • Provides fully managed Retrieval Augmented Generation (RAG) to ground model responses in your proprietary data.
  • Connects to data sources including Amazon S3, Confluence, SharePoint, Salesforce, and web crawlers.
  • Automatically handles document chunking, embedding generation, and vector storage.
  • Supports vector databases: Amazon OpenSearch Serverless, Amazon Aurora PostgreSQL, Pinecone, Redis Enterprise, and MongoDB Atlas.
  • Amazon Bedrock Managed Knowledge Base (2026) — Abstracts storage, retrieval, embeddings, and re-ranking into a single managed primitive. No need to choose or configure a vector database.
  • Supports hybrid search combining semantic (vector) and keyword (lexical) retrieval for improved accuracy.
  • Includes metadata filtering and access controls for multi-tenant scenarios.
  • Available in 22+ AWS Regions.

Agents

  • Bedrock Agents enable building AI applications that can plan and execute multi-step tasks autonomously.
  • Agents break down user requests, call APIs, access knowledge bases, and maintain conversation context.
  • Support action groups — define allowed actions via OpenAPI schemas or Lambda functions.
  • Include built-in capabilities: code interpreter, web search, and user confirmation for sensitive actions.
  • Amazon Bedrock AgentCore (2026) — A dedicated runtime for production-grade AI agents with:
    • AgentCore Runtime — Serverless scaling and session isolation.
    • AgentCore Memory — Conversation context and long-term preference storage.
    • AgentCore Identity — Secure multi-IDP authentication.
    • AgentCore Harness — Testing, evaluation, and continuous optimization.
    • AgentCore Observability — Monitoring and debugging agent behavior.
    • Guardrails Integration — Real-time evaluation of agent actions for safety.
  • Integrated with AWS Step Functions for complex orchestration workflows.

Guardrails

  • Amazon Bedrock Guardrails provides configurable safety controls to filter harmful content and enforce responsible AI policies.
  • Works with any foundation model on Bedrock and external models via the standalone ApplyGuardrail API (model-agnostic).
  • Key safeguards include:
    • Content Filters — Block harmful content across categories: Hate, Insults, Sexual, Violence, Misconduct. Supports both text and images (88% blocking accuracy).
    • Denied Topics — Define topics the model should refuse to discuss.
    • Word Filters — Block specific words or phrases.
    • Sensitive Information Filters (PII) — Detect and redact/block personally identifiable information with Block or Mask modes.
    • Contextual Grounding — Detect hallucinations by checking response relevance to source data.
    • Automated Reasoning Checks — Logic-based validation of model outputs.
    • Prompt Attack Detection — Identify and block prompt injection attempts.
    • Code Domain Protection (2025) — Filter harmful content in code elements including comments, variables, and string literals.
  • Supports IAM policy-based enforcement for organization-wide guardrail application.
  • Scalable: up to 50 calls/second via ApplyGuardrail API, 200 TUPS for content filters.

Model Evaluation

  • Amazon Bedrock Evaluations helps compare and select the best foundation model for your use case.
  • Supports automatic evaluation with predefined metrics: accuracy, robustness, toxicity, semantic similarity, and faithfulness.
  • Supports human evaluation with custom workflows for subjective quality assessment.
  • Can evaluate custom (fine-tuned) models against base models to validate improvements.
  • Evaluates RAG systems end-to-end — retrieval relevance, answer faithfulness, and response quality.
  • Model-agnostic: evaluate models running on Bedrock, other clouds, or on-premises (provide data in required format).
  • Supports LLM-as-a-judge evaluation pattern for automated scoring at scale.

Pricing Model

  • Amazon Bedrock offers flexible pricing options to match different workload requirements and budgets.
  • On-Demand Inference — Pay-per-use based on tokens processed (input and output). No commitments. Three tiers available:
    • Flex — Best-effort capacity at standard pricing.
    • Priority — Higher priority access during peak demand.
    • Standard — Guaranteed capacity with highest priority.
  • Batch Inference — Process large volumes of data asynchronously at 50% of on-demand pricing. Ideal for non-time-sensitive workloads like bulk classification, summarization, or embeddings.
  • Provisioned Throughput (Reserved Capacity) — Reserve a fixed number of tokens-per-minute for 1 month or 3 months. Provides consistent, predictable performance. Billed monthly at a fixed rate per 1K tokens-per-minute.
  • Cross-Region Inference — Automatically routes requests to optimize for availability and latency across regions. Pricing varies by routing tier.
  • Knowledge Bases, Agents, and Guardrails have additional per-request pricing components.
  • Model customization (fine-tuning, continued pre-training) is charged based on tokens processed during training.
  • No upfront costs for on-demand; Bedrock spend can count toward AWS Enterprise Discount Programs (EDP).

Security & Data Privacy

  • Data Privacy
    • Your data is NOT used to train or improve the base foundation models.
    • Your data is NOT shared with any model providers.
    • Inputs and outputs are not stored by Amazon Bedrock (unless you opt-in to logging).
    • Custom model training creates a private copy exclusively for your use.
  • Encryption
    • All data encrypted in transit (TLS) — only encrypted connections to the service are allowed.
    • All data encrypted at rest using AWS KMS (customer-managed keys supported).
    • Model artifacts and training data are encrypted with KMS CMKs.
  • Network Security
    • AWS PrivateLink — Establish private VPC endpoints to access Bedrock without traversing the public internet.
    • VPC endpoint policies for fine-grained access control.
    • No public IP addresses required for VPC instances communicating with Bedrock.
  • Access Control
    • AWS IAM for authentication and authorization.
    • Resource-based and identity-based policies.
    • AWS CloudTrail for complete API audit logging.
    • Service Control Policies (SCPs) for organizational governance.
  • Compliance
    • SOC 1/2/3, ISO 27001, HIPAA eligible, PCI DSS, FedRAMP.
    • Available in AWS GovCloud (US) regions and AWS Top Secret cloud.

Integration with AWS Services

  • AWS Lambda — Invoke Bedrock models from serverless functions for event-driven AI applications.
  • Amazon S3 — Store training data, Knowledge Base source documents, and async inference outputs.
  • AWS Step Functions — Orchestrate multi-step generative AI workflows with direct Bedrock integration (InvokeModel and fine-tuning actions).
  • Amazon CloudWatch — Monitor model invocation metrics, latency, token usage, and set alarms.
  • AWS CloudTrail — Audit all Bedrock API calls for security and compliance.
  • Amazon EventBridge — Trigger workflows based on Bedrock events (e.g., fine-tuning job completion).
  • AWS IAM — Fine-grained access control for models, knowledge bases, agents, and guardrails.
  • Amazon OpenSearch Serverless — Vector database backend for Knowledge Bases.
  • Amazon Kendra — Enterprise search integration for RAG scenarios.
  • AWS PrivateLink / VPC — Private network connectivity to Bedrock.
  • Amazon SageMaker Unified Studio — Access Bedrock models within the unified SageMaker development environment.
  • Amazon Connect — Build AI-powered contact center experiences with Bedrock models.
  • Amazon Lex — Enhanced conversational AI bots powered by Bedrock foundation models.

Amazon Bedrock vs Amazon SageMaker AI

Criteria Amazon Bedrock Amazon SageMaker AI
Primary Purpose Use pre-trained foundation models for inference and generative AI apps Build, train, and deploy custom ML models from scratch
Infrastructure Fully serverless — no infrastructure to manage Managed but requires selecting instance types, scaling config
Model Access Multi-provider FM marketplace (18+ providers) JumpStart for pre-trained models + bring your own
Customization Fine-tuning, continued pre-training, RFT, distillation Full training pipeline control, any framework, any architecture
Best For Generative AI applications, RAG, agents, content generation Custom ML (tabular, time-series, computer vision), proprietary architectures
Skill Level Developers and application builders Data scientists and ML engineers
Pricing Pay-per-token (input/output) Pay-per-instance-hour (training & inference)
Orchestration Built-in Agents, AgentCore, Knowledge Bases MLOps pipelines, model registry, feature store
Safety Controls Built-in Guardrails with content filtering, PII detection Model Cards, Bias detection (Clarify), monitoring

When to Use Each

  • Choose Bedrock when:
    • You need to use pre-trained foundation models for inference.
    • You want the fastest path to production with no infrastructure management.
    • Your use case is generative AI — chatbots, content generation, summarization, RAG, agents.
    • You want to compare and switch between models from different providers.
    • Your team consists of application developers rather than ML specialists.
  • Choose SageMaker AI when:
    • You need to train custom models from scratch with proprietary architectures.
    • Your workload involves traditional ML (classification, regression, forecasting) on structured data.
    • You need complete control over the training pipeline, hyperparameters, and infrastructure.
    • Your token volume is high and predictable (cost-effective at scale with reserved instances).
    • Compliance requires complete VPC data isolation with self-hosted model endpoints.
    • AI/ML is your core product and you need full MLOps lifecycle management.
  • Use Both — Most mature AWS AI deployments use Bedrock for generative AI and agentic applications while leveraging SageMaker AI for custom model training and specialized ML workloads.

AWS Certification Exam Relevance

Certification Bedrock Topics Tested Weight
AWS Certified AI Practitioner (AIF-C01) Core Bedrock service, model selection, Knowledge Bases/RAG, Agents, Guardrails, responsible AI, fine-tuning concepts, pricing High — Bedrock is central to this exam
AWS Solutions Architect Associate (SAA-C03) When to use Bedrock vs SageMaker, integration patterns, security (VPC, encryption), serverless architecture Medium — appears in ML/AI service selection questions
AWS Solutions Architect Professional (SAP-C02) Architecture patterns with Bedrock, multi-account governance, data privacy, cross-region inference, cost optimization Medium — complex scenario questions involving AI workloads

Key Exam Tips

  • AIF-C01: If a question asks for a way to use foundation models with no infrastructure, no deployment overhead, and access to multiple model providers — the answer is almost always Bedrock.
  • AIF-C01: RAG with Knowledge Bases is the standard approach for grounding model responses in enterprise data without fine-tuning.
  • AIF-C01: Guardrails is the answer for content filtering, PII protection, and responsible AI enforcement.
  • SAA-C03: Bedrock = serverless foundation models; SageMaker AI = custom model training and deployment.
  • SAP-C02: For enterprise scenarios requiring data privacy, remember: Bedrock data is never used for training, and VPC endpoints provide private connectivity.

Amazon Bedrock Practice Questions

  1. A company wants to build a customer-facing chatbot that answers questions using information from their internal knowledge base stored in Amazon S3. The solution must be serverless, ground responses in actual company data, and prevent hallucinations. Which combination of Amazon Bedrock features should they use?
    1. Amazon Bedrock with fine-tuning on company documents
    2. Amazon Bedrock Knowledge Bases with Guardrails contextual grounding checks
    3. Amazon SageMaker AI with a custom-trained LLM
    4. Amazon Kendra with Amazon Lex
    Show Answer

    Answer: b – Bedrock Knowledge Bases provides managed RAG that grounds responses in company data from S3. Guardrails with contextual grounding checks validate that responses are faithful to the retrieved source data, helping prevent hallucinations. Fine-tuning teaches style/behavior but doesn’t ground in specific documents. SageMaker requires infrastructure management. Kendra + Lex doesn’t provide generative AI responses.

  2. A financial services company needs to deploy a generative AI application that processes sensitive customer data. They require that: (1) data is never shared with model providers, (2) all traffic stays within their private network, and (3) all data is encrypted with their own keys. Which Amazon Bedrock security features address these requirements?
    1. IAM policies and CloudTrail logging
    2. AWS PrivateLink VPC endpoints, AWS KMS customer-managed keys, and Bedrock’s data privacy guarantee
    3. Security groups and NACLs
    4. AWS Shield and AWS WAF
    Show Answer

    Answer: b – Amazon Bedrock guarantees that customer data is never shared with model providers or used to train base models. AWS PrivateLink provides private VPC connectivity without internet exposure. AWS KMS with customer-managed keys provides encryption at rest and in transit with customer control. These three features together satisfy all stated requirements.

  3. A startup needs to build a generative AI application quickly and wants to evaluate multiple foundation models before selecting one for production. They have application developers but no ML engineers. Which AWS service is most appropriate?
    1. Amazon SageMaker AI with JumpStart
    2. Amazon Bedrock with Model Evaluation
    3. Amazon Comprehend
    4. AWS Deep Learning AMIs on EC2
    Show Answer

    Answer: b – Amazon Bedrock provides serverless access to multiple foundation models through a unified API, requires no ML expertise or infrastructure management, and includes built-in Model Evaluation to compare models using automatic and human evaluation metrics. SageMaker JumpStart provides pre-trained models but requires more ML expertise and infrastructure decisions.

  4. An enterprise wants to ensure their generative AI application blocks harmful content, detects prompt injection attacks, and redacts PII from both inputs and outputs. The solution must work across different foundation models and be enforced organization-wide via IAM policies. Which service should they use?
    1. Amazon Comprehend for PII detection with custom Lambda filters
    2. Amazon Bedrock Guardrails with IAM policy-based enforcement
    3. AWS WAF with custom rules
    4. Amazon Macie for sensitive data discovery
    Show Answer

    Answer: b – Amazon Bedrock Guardrails provides all the required capabilities: content filtering (harmful content blocking), prompt attack detection, and sensitive information filters with PII redaction (Block or Mask modes). It works with any model via the ApplyGuardrail API and supports IAM policy-based enforcement to apply guardrails organization-wide across all model inference calls.

  5. A company has a large volume of product descriptions (5 million items) that need to be classified into categories using a foundation model. The task is not time-sensitive and they want to minimize costs. Which Amazon Bedrock inference option should they choose?
    1. On-demand inference with Standard tier
    2. Provisioned throughput with 3-month commitment
    3. Batch inference
    4. Cross-region inference with Global routing
    Show Answer

    Answer: c – Batch inference is ideal for large-volume, non-time-sensitive workloads and is priced at 50% of on-demand pricing, making it the most cost-effective option. Provisioned throughput is for consistent, predictable workloads requiring low latency. On-demand Standard tier is more expensive. Cross-region inference optimizes availability, not cost.

Frequently Asked Questions

What is Amazon Bedrock?

Amazon Bedrock is a fully managed service that provides access to foundation models from leading AI companies (Anthropic, Meta, Mistral, Amazon, and others) through a single API. It offers fine-tuning, RAG with Knowledge Bases, Agents, and Guardrails without managing infrastructure.

How does Bedrock differ from SageMaker?

Bedrock is for accessing and customizing pre-built foundation models without ML expertise. SageMaker is for building, training, and deploying custom ML models from scratch. Use Bedrock for generative AI applications; use SageMaker when you need full control over the model training pipeline.

Does AWS use my data to train Bedrock models?

No. AWS does not use any customer inputs or outputs to train or improve Amazon Bedrock foundation models. Your data remains private and is encrypted in transit and at rest.

References

AWS WAF vs Shield vs Firewall Manager

AWS WAF vs Shield vs Firewall Manager

  • AWS provides three complementary security services for protecting web applications and AWS resources from attacks.
  • WAF filters web traffic at Layer 7, Shield protects against DDoS attacks at Layer 3/4, and Firewall Manager centrally manages security policies across accounts.
  • These services work together — Shield protects the infrastructure, WAF filters application-layer attacks, and Firewall Manager enforces policies at scale.

WAF vs Shield vs Firewall Manager Comparison

Feature AWS WAF AWS Shield AWS Firewall Manager
Purpose Web application firewall (Layer 7) DDoS protection (Layer 3/4/7) Central security policy management
Protection Layer Layer 7 (HTTP/HTTPS) Standard: L3/4; Advanced: L3/4/7 Manages WAF, Shield, SG, Network Firewall, Route 53 DNS Firewall
Attacks Blocked SQL injection, XSS, bot traffic, rate limiting, geo blocking SYN flood, UDP reflection, volumetric attacks Policy violations across accounts
Scope Per resource (CloudFront, ALB, API Gateway, AppSync, Cognito, App Runner, Verified Access) Per resource (Standard) or account-wide (Advanced) AWS Organization-wide
Pricing Per web ACL + per rule + per million requests Standard: Free; Advanced: $3,000/month + data transfer Per policy per region + per resource
Automatic Rules must be configured Standard: automatic; Advanced: automatic + DRT team Auto-applies policies to new resources
Managed Rules AWS + Marketplace (Fortinet, F5, Imperva) N/A (automatic detection) Enforces WAF rule groups across accounts
Cost Protection No Advanced: credits for scaling costs during DDoS No
Response Team No Advanced: 24/7 Shield Response Team (SRT) No
Prerequisite None Standard: automatic; Advanced: subscription AWS Organizations + WAF/Shield Advanced

AWS WAF (Web Application Firewall)

  • Layer 7 firewall that filters HTTP/HTTPS requests based on configurable rules.
  • Web ACLs contain rules that inspect requests (headers, body, URI, query strings, IP).
  • Rule types:
    • Rate-based rules – block IPs exceeding request threshold (per 5-min window)
    • IP set rules – allow/block specific IP ranges
    • Geo match – allow/block by country
    • String/regex match – inspect request components
    • SQL injection / XSS detection – built-in detection statements
    • Size constraints – block oversized requests
  • Managed Rule Groups:
    • AWS Managed Rules – Core Rule Set, Known Bad Inputs, SQL/Linux/Windows/PHP, Bot Control, Account Takeover Prevention, Account Creation Fraud Prevention
    • Marketplace rules – Fortinet, F5, Imperva, Trend Micro
  • Bot Control – identify and manage bot traffic (common bots, targeted bots, AI scrapers).
  • Account Takeover Prevention (ATP) – detect credential stuffing on login pages.
  • Account Creation Fraud Prevention (ACFP) – prevent fake account creation.
  • CAPTCHA and Challenge – silent browser challenges or visible CAPTCHA.
  • Applies to: CloudFront, ALB, API Gateway, AppSync, Cognito User Pools, App Runner, Verified Access.
  • Best for: Protecting web applications from SQL injection, XSS, bot abuse, brute force, and application-layer attacks.

AWS Shield

  • DDoS protection service – defends against volumetric, protocol, and application-layer attacks.
  • Shield Standard (free, automatic):
    • Automatically protects ALL AWS customers at no extra cost
    • Protects against common Layer 3/4 DDoS attacks (SYN/UDP floods, reflection attacks)
    • Applied to CloudFront, Route 53, and Global Accelerator automatically
  • Shield Advanced ($3,000/month):
    • Enhanced detection for EC2, ELB, CloudFront, Global Accelerator, Route 53
    • DDoS cost protection – credits for Auto Scaling, CloudFront, ELB scaling costs during attacks
    • Shield Response Team (SRT) – 24/7 expert team to assist during attacks
    • Advanced metrics and reporting – real-time visibility into attacks
    • Automatic application-layer mitigation – creates WAF rules automatically during L7 attacks
    • Health-based detection – uses Route 53 health checks for faster detection
    • Proactive engagement – SRT contacts you when health checks trigger
    • Protection applies to all resources in the account (and org with Firewall Manager)
  • Best for: High-profile applications needing DDoS protection guarantees, SLA credits, and 24/7 expert support.

AWS Firewall Manager

  • Central security policy management across AWS Organizations accounts and resources.
  • Manages policies for:
    • AWS WAF – deploy WAF rules across all accounts/resources
    • AWS Shield Advanced – enable protection organization-wide
    • Security Groups – audit and enforce SG rules
    • AWS Network Firewall – deploy firewall rules across VPCs
    • Route 53 Resolver DNS Firewall – enforce DNS filtering
    • Third-party firewalls – Palo Alto, Fortigate via Marketplace
  • Auto-remediation – automatically applies policies to new resources/accounts as they’re created.
  • Compliance dashboard – view which resources are non-compliant across the organization.
  • Prerequisites: AWS Organizations, AWS Config enabled in all accounts.
  • Best for: Multi-account organizations needing consistent security policies, compliance auditing, and automatic enforcement.

How They Work Together

  • Shield Standard (always on) protects infrastructure from volumetric L3/4 DDoS.
  • Shield Advanced adds L7 protection and automatically creates WAF rules during application-layer attacks.
  • WAF handles ongoing application-layer threats (bots, injections, rate limiting).
  • Firewall Manager ensures WAF + Shield Advanced policies are consistently deployed across all accounts and resources.
  • Typical stack: Firewall Manager → Shield Advanced → WAF → Application.

When to Choose Which

  • Every application gets Shield Standard – it’s free and automatic.
  • Add WAF when – you need to filter application-layer traffic (SQL injection, bot management, rate limiting, geo-blocking).
  • Add Shield Advanced when – you need DDoS cost protection, 24/7 SRT support, enhanced detection, and SLA guarantees for business-critical applications.
  • Add Firewall Manager when – you manage multiple AWS accounts and need consistent security policies automatically applied across the organization.

AWS Certification Exam Practice Questions

  1. A company experiences a sudden spike in traffic that appears to be a DDoS attack targeting their ALB. They want AWS experts to help mitigate the attack in real-time. Which service provides this?
    1. AWS WAF with rate-based rules
    2. AWS Shield Advanced (Shield Response Team)
    3. AWS Firewall Manager
    4. AWS Network Firewall
  2. An e-commerce site needs to block SQL injection attacks and limit login attempts to 100 per IP per 5 minutes. Which service provides these capabilities?
    1. AWS Shield Advanced
    2. Security Groups
    3. AWS WAF (SQL injection rule + rate-based rule)
    4. Network ACLs
  3. A large enterprise with 50 AWS accounts needs to ensure every ALB in every account has the same WAF rules applied, including new ALBs created in the future. Which service automates this?
    1. AWS WAF with central web ACL
    2. AWS Shield Advanced
    3. AWS Config Rules
    4. AWS Firewall Manager
  4. After a DDoS attack, a company’s CloudFront and Auto Scaling costs spiked significantly due to the attack traffic. Which service provides credits for these scaling costs?
    1. AWS WAF
    2. AWS Shield Advanced (DDoS cost protection)
    3. AWS Firewall Manager
    4. AWS Trusted Advisor
  5. A company wants to detect and block AI web scrapers from crawling their content while allowing legitimate search engine bots. Which WAF feature addresses this?
    1. Rate-based rules
    2. Geo match rules
    3. AWS WAF Bot Control (AI Content Scraper category)
    4. IP reputation lists

Related Posts

References

AWS WAF Developer Guide

AWS Shield Developer Guide

AWS Firewall Manager Developer Guide

AWS Route 53 Routing Policies Comparison

AWS Route 53 Routing Policies Comparison

  • Amazon Route 53 supports 7 routing policies that determine how DNS queries are answered.
  • Choosing the right routing policy depends on whether you need failover, latency optimization, geographic restrictions, or traffic distribution.
  • Multiple policies can be combined using alias records and health checks for complex routing architectures.

Route 53 Routing Policies Comparison

Policy Use Case How It Works Health Checks
Simple Single resource, no special routing Returns all values in random order No (can’t attach)
Weighted Traffic distribution, blue/green, A/B testing Routes based on assigned weights (0-255) Yes
Latency-based Best performance for global users Routes to region with lowest latency Yes
Failover Active-passive disaster recovery Primary until unhealthy, then secondary Yes (required for primary)
Geolocation Content localization, compliance, restrictions Routes based on user’s geographic location Yes
Geoproximity Route based on resource location + bias Routes to nearest resource; bias expands/shrinks coverage Yes
Multivalue Answer Simple load balancing with health checks Returns up to 8 healthy records randomly Yes
IP-based Route by client IP/CIDR (ISP optimization) Routes based on client subnet CIDR mapping Yes

Simple Routing

  • Routes traffic to a single resource (or multiple values returned in random order).
  • Cannot attach health checks to simple routing records.
  • If multiple values are returned, client chooses one randomly (client-side load balancing).
  • Can only have one record per name with simple routing.
  • Best for: Single server, single resource behind a load balancer.

Weighted Routing

  • Routes traffic based on weights assigned to records (0-255).
  • Traffic proportion = record weight / sum of all weights for the same name.
  • Setting weight to 0 stops traffic to that resource (useful for maintenance).
  • If all records have weight 0, traffic is distributed equally.
  • Supports health checks – unhealthy records removed from responses.
  • Best for: Blue/green deployments (90/10 split), A/B testing, gradual migrations, load distribution across regions.

Latency-based Routing

  • Routes traffic to the region with the lowest network latency for the user.
  • Latency is measured between the user’s DNS resolver and AWS regions.
  • Requires resources in multiple AWS regions.
  • Supports health checks – if lowest-latency resource is unhealthy, routes to next-best.
  • Latency data is updated periodically by AWS (not real-time per request).
  • Best for: Global applications deployed in multiple regions needing best user experience.

Failover Routing

  • Routes traffic to primary resource when healthy, secondary when primary fails health check.
  • Active-passive configuration – only one designation per record set (primary or secondary).
  • Health check required on primary record; optional on secondary.
  • Secondary can point to a static S3 website (maintenance page) or another resource.
  • Can be combined with other routing policies using alias records.
  • Best for: Disaster recovery, maintenance pages, active-passive HA architectures.

Geolocation Routing

  • Routes traffic based on geographic location of the user (continent, country, or US state).
  • Most specific match wins – state > country > continent > default.
  • A default record is recommended – users from unmapped locations get this response.
  • If no default and no match, Route 53 returns “no answer”.
  • Does NOT route to closest resource – routes to the location you configure (use geoproximity for nearest).
  • Best for: Content localization (language), compliance (restrict access by country), serving region-specific content.

Geoproximity Routing

  • Routes traffic based on geographic distance between user and resources.
  • Bias values (-99 to +99) expand or shrink the geographic area that routes to a resource.
  • Positive bias = attracts more traffic (expands coverage area).
  • Negative bias = repels traffic (shrinks coverage area).
  • Supports both AWS resources (auto-detects region) and non-AWS resources (specify latitude/longitude).
  • Requires Route 53 Traffic Flow to use geoproximity routing.
  • Best for: Routing to nearest resource with ability to shift traffic between regions using bias.

Multivalue Answer Routing

  • Returns up to 8 healthy records in response to each DNS query.
  • Similar to simple routing but supports health checks – only healthy resources returned.
  • Not a substitute for a load balancer but provides basic DNS-level load balancing with health checking.
  • Each record can have its own health check.
  • Best for: Basic load distribution with health checking when you don’t need ELB.

IP-based Routing

  • Routes traffic based on client’s source IP address mapped to CIDR blocks.
  • Create CIDR collections with locations, then map records to locations.
  • Useful when you know the IP ranges of your users (corporate networks, ISPs).
  • More precise than geolocation – routes based on actual network, not estimated location.
  • Best for: ISP-specific routing, enterprise users with known IP ranges, optimizing costs by routing to specific endpoints.

Combining Routing Policies

  • Alias records can point to other Route 53 record sets, enabling policy combinations.
  • Example: Latency → Weighted (route to nearest region, then split between blue/green within region).
  • Example: Failover → Latency (primary is latency-based across regions, secondary is S3 static page).
  • Example: Geolocation → Failover (per-country routing with DR fallback).
  • Traffic Flow – visual editor for building complex routing trees with multiple policies.

AWS Certification Exam Practice Questions

  1. A company wants to gradually migrate traffic from an on-premises data center to AWS by sending 10% of traffic to AWS initially, increasing over time. Which routing policy supports this?
    1. Latency-based
    2. Weighted
    3. Failover
    4. Geolocation
  2. An application deployed in us-east-1 and eu-west-1 should route users to whichever region provides the fastest response. Which routing policy is appropriate?
    1. Geolocation
    2. Geoproximity
    3. Latency-based
    4. Weighted (50/50)
  3. A streaming service must serve different content libraries to users in different countries due to licensing restrictions. Which routing policy enforces this?
    1. Latency-based
    2. Geolocation
    3. Geoproximity
    4. IP-based
  4. A company needs to route traffic to the nearest data center but temporarily shift more traffic to a new region during a migration. Which routing policy allows adjusting the geographic coverage area?
    1. Geolocation with failover
    2. Weighted with latency
    3. Geoproximity with bias
    4. Multivalue answer
  5. An architect needs DNS-level health checking where unhealthy endpoints are automatically removed from DNS responses, but a full load balancer is not required. Which policy provides this with multiple IPs?
    1. Simple routing
    2. Weighted routing
    3. Failover routing
    4. Multivalue answer routing

Related Posts

References

Route 53 Routing Policies

Route 53 Traffic Flow

DynamoDB vs DocumentDB vs Neptune – Which AWS Database to Choose

AWS DynamoDB vs DocumentDB vs Neptune

  • AWS offers multiple purpose-built NoSQL database services, each optimized for different data models and access patterns.
  • DynamoDB is a key-value/document database for high-scale low-latency workloads, DocumentDB is MongoDB-compatible for document workloads, and Neptune is a graph database for highly connected data.
  • Choice depends on data model, query patterns, scale requirements, and existing application compatibility.

DynamoDB vs DocumentDB vs Neptune Comparison

Feature DynamoDB DocumentDB Neptune
Data Model Key-value + Document Document (JSON) Graph (property graph + RDF)
Compatibility AWS proprietary API MongoDB 3.6/4.0/5.0 compatible Gremlin, SPARQL, openCypher
Architecture Serverless, fully managed Cluster-based (primary + replicas) Cluster-based (primary + replicas)
Scaling Automatic, unlimited (horizontal) Vertical (instance size) + read replicas (up to 15) Vertical (instance size) + read replicas (up to 15)
Serverless Option Yes (On-Demand or Provisioned) Yes (DocumentDB Elastic Clusters) Yes (Neptune Serverless)
Latency Single-digit milliseconds Low milliseconds Milliseconds for traversals
Max Item/Document Size 400KB 16MB N/A (graph edges/vertices)
Query Flexibility Limited (partition key + sort key, GSI/LSI) Rich (MongoDB query language, aggregation pipelines) Graph traversals (multi-hop relationships)
Transactions Yes (up to 100 items, 4MB) Yes (multi-document ACID) Yes (ACID)
Global Replication Global Tables (multi-region active-active) Global Clusters (up to 5 regions, read replicas) Global Database (up to 5 read regions)
Change Streams DynamoDB Streams / Kinesis Data Streams Change Streams (MongoDB compatible) Neptune Streams
Caching DAX (microsecond reads) No built-in (use ElastiCache) No built-in (use ElastiCache)
Full-Text Search No (integrate OpenSearch) Basic text indexes Neptune Analytics (vector + full-text)
Vector Search No No Yes (Neptune Analytics)
Pricing Per request (on-demand) or per RCU/WCU (provisioned) Per instance-hour + storage + I/O Per instance-hour + storage + I/O

Amazon DynamoDB

  • Fully serverless key-value and document database – single-digit millisecond latency at any scale.
  • Capacity modes: On-Demand (pay per request, zero capacity planning) or Provisioned (with Auto Scaling).
  • Designed for massive scale – handles 10+ trillion requests per day, peaks above 100 million requests/second.
  • Global Tables – multi-region, multi-active replication with Multi-Region Strong Consistency (MRSC, GA 2025).
  • DynamoDB Accelerator (DAX) – in-memory cache for microsecond read latency.
  • DynamoDB Streams – capture item-level changes for event-driven processing (Lambda integration).
  • TTL – automatic item expiration at no cost.
  • Zero-ETL to Redshift – replicate data to Redshift for analytics without pipelines.
  • Limitations: 400KB item size, limited query flexibility (must know partition key), no joins, no aggregations.
  • Best for: High-scale applications with known access patterns – gaming leaderboards, session stores, IoT, e-commerce carts, serverless backends.

Amazon DocumentDB

  • MongoDB-compatible document database – supports MongoDB 3.6, 4.0, and 5.0 API compatibility.
  • Purpose-built storage – separates compute from storage (similar to Aurora); storage auto-scales to 128TB.
  • Rich queries – full MongoDB query language, aggregation pipelines, secondary indexes, geospatial queries.
  • Elastic Clusters – shard collections across multiple nodes for horizontal scaling (millions of reads/writes per second).
  • Global Clusters – cross-region disaster recovery with up to 5 read regions.
  • Change Streams – MongoDB-compatible change data capture for event-driven architectures.
  • 16MB document size – suitable for complex nested documents.
  • Not 100% MongoDB compatible – some features differ (check compatibility matrix).
  • Best for: MongoDB workloads migrating to AWS, content management, catalogs, user profiles, applications needing flexible schemas with rich querying.

Amazon Neptune

  • Fully managed graph database – purpose-built for storing and querying highly connected data.
  • Supports three query languages: Apache TinkerPop Gremlin (property graphs), SPARQL (RDF/linked data), and openCypher (declarative graph queries).
  • Neptune Analytics – analyze graph data with vector search, graph algorithms, and full-text search.
  • Neptune Serverless – automatically scales compute based on workload.
  • Neptune ML – machine learning predictions on graph data using GNNs (Graph Neural Networks) via SageMaker.
  • Global Database – cross-region read replicas for low-latency reads and disaster recovery.
  • Neptune Streams – capture graph changes for downstream processing.
  • Up to 15 read replicas – scale reads across multiple instances.
  • Best for: Relationship-heavy data – social networks, recommendation engines, fraud detection, knowledge graphs, network topology, identity graphs, supply chain.

When to Choose Which

  • Choose DynamoDB when:
    • You need extreme scale with single-digit ms latency
    • Access patterns are well-defined (key-value lookups)
    • You want fully serverless with zero management
    • Use cases: session stores, gaming, IoT, e-commerce, serverless apps
  • Choose DocumentDB when:
    • You’re migrating from MongoDB or need MongoDB compatibility
    • Documents are complex/nested and need flexible querying
    • You need aggregation pipelines and secondary indexes
    • Use cases: content management, catalogs, user profiles
  • Choose Neptune when:
    • Data is highly connected with complex relationships
    • Queries involve traversing relationships (multi-hop)
    • You need graph algorithms (shortest path, centrality, community detection)
    • Use cases: social networks, fraud detection, knowledge graphs, recommendations

AWS Certification Exam Practice Questions

  1. A social media application needs to find “friends of friends” and recommend connections based on mutual relationships. Which database is purpose-built for this query pattern?
    1. DynamoDB with GSI
    2. DocumentDB with aggregation
    3. Neptune (graph traversal)
    4. RDS with JOIN queries
  2. A company is migrating a MongoDB application to AWS. They use aggregation pipelines, geospatial queries, and change streams extensively. Which service provides the best compatibility?
    1. DynamoDB with Document model
    2. DocumentDB
    3. Neptune
    4. ElastiCache for MongoDB
  3. A gaming application needs a leaderboard that handles 50,000 writes per second with single-digit millisecond latency, using simple key-value access patterns. Which database fits?
    1. DocumentDB
    2. Neptune
    3. Aurora
    4. DynamoDB
  4. A fraud detection system needs to analyze transaction patterns by traversing relationships between accounts, devices, IP addresses, and merchants to find suspicious clusters. Which database is best suited?
    1. DynamoDB with Streams
    2. DocumentDB with aggregation
    3. Neptune with graph algorithms
    4. Redshift for analytics
  5. An e-commerce application stores product catalogs with deeply nested attributes (variations, specifications, reviews) and needs to query by any attribute with aggregation. Documents average 2MB. Which database fits?
    1. DynamoDB (400KB limit would be exceeded)
    2. DocumentDB (16MB limit, rich queries)
    3. Neptune
    4. S3 with Athena

Related Posts

References

Amazon DynamoDB Developer Guide

Amazon DocumentDB Developer Guide

Amazon Neptune User Guide

AWS Step Functions vs EventBridge

AWS Step Functions vs EventBridge

  • Both Step Functions and EventBridge are serverless services for coordinating workflows, but they serve fundamentally different purposes.
  • Step Functions orchestrates multi-step workflows with state management and error handling.
  • EventBridge routes events between services based on content-based rules without maintaining state.
  • They are often used together – EventBridge triggers Step Functions workflows based on events.

Step Functions vs EventBridge Comparison

Feature Step Functions EventBridge
Pattern Orchestration (centralized control) Choreography (decoupled routing)
State Management Yes – tracks execution state, input/output between steps No – stateless event routing
Execution Model Sequential, parallel, branching, looping Fire-and-forget event delivery
Duration Standard: up to 1 year; Express: up to 5 minutes Near real-time delivery (no duration concept)
Error Handling Built-in Retry, Catch, Fallback states Dead-letter queue on target delivery failure
Visibility Visual workflow graph, step-by-step execution history Rule match metrics, limited execution visibility
Targets/Integrations 200+ AWS service integrations (direct SDK calls) 200+ AWS service targets per rule
Event Sources Triggered by API call, EventBridge, API Gateway, Lambda 90+ AWS services, SaaS partners, custom apps
Filtering Choice state (conditions on input data) Content-based filtering on event body (event patterns)
Parallelism Parallel state, Distributed Map (millions of items) Multiple targets per rule (fan-out)
Human Approval Yes – Task tokens with callback pattern No native support
Scheduling Wait state (delay steps) EventBridge Scheduler (cron/rate/one-time)
Replay Redrive failed executions (2024) Event Archive and Replay
Pricing Standard: per state transition; Express: per request + duration Per event published ($1/million)

AWS Step Functions

  • Serverless workflow orchestration – coordinates multiple AWS services into visual workflows.
  • Standard Workflows – up to 1 year, exactly-once execution, full execution history, ideal for long-running processes.
  • Express Workflows – up to 5 minutes, at-least-once, high-volume event processing (100K+ executions/second).
  • States: Task, Choice, Parallel, Map, Wait, Pass, Succeed, Fail.
  • Direct SDK integrations – call 200+ AWS services without Lambda (DynamoDB PutItem, SQS SendMessage, ECS RunTask, Bedrock InvokeModel).
  • Distributed Map – process millions of items from S3 in parallel (up to 10,000 concurrent executions).
  • Callback pattern – pause workflow, wait for external system/human approval via task token.
  • Error handling – Retry with exponential backoff, Catch with fallback states, per-step timeout.
  • Redrive (2024) – restart failed executions from the point of failure without re-running completed steps.
  • Variables and JSONata (2024) – workflow-level variables and powerful data transformation expressions.
  • Best for: Multi-step processes needing coordination, error handling, human approval, long-running workflows, batch processing.

Amazon EventBridge

  • Serverless event bus – routes events between decoupled services based on rules.
  • Receives events from 90+ AWS services automatically without configuration.
  • Content-based filtering – event patterns match on any field in the event JSON body.
  • Multiple targets per rule – fan-out a single event to up to 5 targets.
  • EventBridge Scheduler – millions of one-time or recurring schedules (replaces CloudWatch Events).
  • EventBridge Pipes – point-to-point with filtering, enrichment, and transformation between source and target.
  • Event Archive and Replay – store events indefinitely for reprocessing or debugging.
  • Schema Registry – auto-discover event schemas for code generation.
  • Global endpoints – automatic failover to secondary region.
  • SaaS integrations – receive events from Zendesk, Datadog, Shopify, Auth0, etc.
  • Best for: Event-driven architectures, reacting to AWS service changes, decoupled microservices, SaaS integration, scheduling.

When to Choose Which

  • Choose Step Functions when:
    • You need to coordinate multiple steps in a specific order
    • Workflow requires error handling with retries and fallbacks
    • You need visibility into which step succeeded/failed
    • Process requires human approval or external callbacks
    • Long-running processes (minutes to months)
    • Batch processing of millions of items (Distributed Map)
  • Choose EventBridge when:
    • You need to react to events from AWS services or SaaS apps
    • Services should be decoupled (producers don’t know about consumers)
    • Routing based on event content to different targets
    • You need scheduling (cron jobs, one-time future events)
    • Fan-out: one event triggers multiple independent actions
    • Cross-account or cross-region event routing
  • Use Both Together: EventBridge detects an event (e.g., S3 upload) → triggers Step Functions workflow → orchestrates multi-step processing (validate → transform → load → notify).

AWS Certification Exam Practice Questions

  1. An order processing system requires validating payment, checking inventory, reserving items, charging the card, and sending confirmation – each step depends on the previous one succeeding. If payment fails, the reserved items must be released. Which service handles this?
    1. EventBridge with multiple rules
    2. Step Functions with error handling (Catch/compensating actions)
    3. SQS with multiple queues
    4. SNS with filter policies
  2. A company wants to automatically trigger different Lambda functions when EC2 instances change state (running, stopped, terminated) – each state routes to a different function. Which service is most appropriate?
    1. Step Functions with Choice state
    2. CloudWatch Alarms
    3. EventBridge with content-based rules
    4. SNS with message filtering
  3. A data pipeline processes millions of S3 objects in parallel, with each object needing 3 transformation steps. The pipeline must track progress and retry individual failures. Which approach is recommended?
    1. EventBridge Pipes with SQS
    2. Lambda triggered by S3 events
    3. Step Functions Distributed Map
    4. EventBridge with Lambda targets
  4. A workflow requires pausing execution until a human reviews and approves a document via an external web application (may take hours or days). Which feature supports this?
    1. EventBridge wait pattern
    2. Step Functions callback pattern with task token
    3. SQS visibility timeout
    4. Lambda with DynamoDB polling
  5. A company needs to schedule 2 million one-time reminder notifications to be sent at specific future times (each different). Which service handles this at scale?
    1. Step Functions Wait state
    2. CloudWatch Events cron
    3. EventBridge Scheduler
    4. SQS delay queues

Related Posts

References

AWS Step Functions Developer Guide

Amazon EventBridge User Guide

EventBridge Scheduler User Guide

AWS CloudWatch vs CloudTrail vs Config

AWS CloudWatch vs CloudTrail vs Config

  • AWS provides three core monitoring and governance services that are often confused but serve distinct purposes.
  • CloudWatch monitors performance and operational health, CloudTrail records API activity (who did what), and Config tracks resource configuration changes and compliance.
  • All three work together for a complete observability and governance strategy.

CloudWatch vs CloudTrail vs Config Comparison

Feature CloudWatch CloudTrail Config
Purpose Performance monitoring & observability API audit trail & activity logging Resource configuration tracking & compliance
Answers “How is it performing?” “Who did what and when?” “What changed and is it compliant?”
Data Type Metrics, logs, traces, events API call records (events) Resource configuration snapshots
Scope Resources, applications, services AWS account API activity AWS resource inventory & state
Retention Metrics: 15 months; Logs: configurable (forever) 90 days (console) or S3 (indefinite) Indefinite (configuration history)
Alerting Yes (Alarms on metrics and logs) Via EventBridge or CloudWatch Logs Yes (Config Rules – non-compliant triggers SNS)
Automation Auto Scaling, EC2 actions, Lambda EventBridge rules trigger actions Auto-remediation via SSM Automation
Cross-account Cross-account dashboards, metric sharing Organization trail Aggregator (multi-account, multi-region)
Pricing Per metric, log ingestion, dashboard Free (management events, 1 copy); data events paid Per rule evaluation + per configuration item recorded
Example CPU > 80% for 5 minutes → alarm User X deleted S3 bucket at 3:42pm Security group changed to allow 0.0.0.0/0 → non-compliant

Amazon CloudWatch

  • Monitoring and observability service for AWS resources and applications.
  • Metrics – collect and track standard (free) and custom metrics; 1-second resolution available.
  • Alarms – trigger actions (Auto Scaling, SNS, EC2 stop/terminate/reboot) when metrics cross thresholds.
  • Logs – centralized log collection with Logs Insights for SQL-like querying.
  • Dashboards – create visualizations across accounts and regions.
  • CloudWatch Agent – collect OS-level metrics (memory, disk) and application logs from EC2.
  • Anomaly Detection – ML-based bands to detect unusual metric behavior.
  • Composite Alarms – combine multiple alarms with AND/OR logic to reduce noise.
  • Synthetics – canary scripts to monitor endpoints and APIs proactively.
  • Application Signals – automatic application monitoring with SLOs (GA 2024).
  • Internet Monitor – monitor internet connectivity to your application.
  • Database Insights – unified database monitoring across RDS, Aurora, and self-managed databases.

AWS CloudTrail

  • Records all API calls made in your AWS account – who, what, when, from where.
  • Management events – control plane operations (CreateBucket, RunInstances, etc.) – free, 1 copy per region.
  • Data events – data plane operations (S3 GetObject, Lambda Invoke, DynamoDB GetItem) – paid.
  • Insights events – detect unusual API activity patterns (e.g., spike in API calls).
  • Trail delivery – send events to S3 (long-term storage) and/or CloudWatch Logs (real-time alerting).
  • Organization trail – single trail for all accounts in AWS Organizations.
  • CloudTrail Lake – managed data lake for querying events with SQL (replaces Athena queries on S3).
  • Event history – 90-day free lookup in the console (management events only).
  • Integrity validation – digest files prove logs haven’t been tampered with.
  • Network activity events (2024) – track VPC endpoint API calls for data perimeter monitoring.

AWS Config

  • Tracks resource configuration changes and evaluates compliance over time.
  • Configuration recorder – captures current state of resources as configuration items.
  • Configuration history – timeline of how a resource’s configuration changed.
  • Config Rules – evaluate resources against desired configurations (400+ AWS managed rules + custom Lambda rules).
  • Conformance Packs – collection of Config Rules and remediation actions packaged as a single entity.
  • Auto-remediation – automatically fix non-compliant resources via SSM Automation documents.
  • Aggregator – centralized view across multiple accounts and regions.
  • Advanced Query – SQL queries on current configuration state of all resources.
  • Proactive compliance (2024) – evaluate CloudFormation templates BEFORE deployment.
  • Service-linked rules – Config Rules managed by other AWS services (Security Hub, Control Tower).
  • Resource timeline – view config changes, compliance changes, and CloudTrail events together.

How They Work Together

  • Security incident investigation: Config shows WHAT changed → CloudTrail shows WHO changed it → CloudWatch shows the IMPACT on performance.
  • Compliance automation: Config Rule detects non-compliant resource → triggers SNS → Auto-remediation fixes it → CloudTrail logs the remediation → CloudWatch tracks the metric.
  • Proactive monitoring: CloudWatch alarm fires on high error rate → CloudTrail reveals recent deployment → Config shows configuration change that caused it.

When to Choose Which

  • Use CloudWatch – Monitor CPU/memory/disk, set alarms for thresholds, centralize application logs, create dashboards, track SLOs.
  • Use CloudTrail – Audit API calls, investigate security incidents, meet compliance requirements for activity logging, detect unusual API patterns.
  • Use Config – Track resource configuration drift, enforce compliance rules, audit resource history, auto-remediate non-compliant resources.
  • Use all three together – Complete governance: monitoring (CloudWatch) + auditing (CloudTrail) + compliance (Config).

AWS Certification Exam Practice Questions

  1. A security team needs to determine who deleted an S3 bucket last Tuesday and from which IP address. Which service provides this information?
    1. CloudWatch Logs
    2. CloudTrail
    3. AWS Config
    4. VPC Flow Logs
  2. A company needs to ensure all Security Groups in their account never allow SSH (port 22) from 0.0.0.0/0. If a non-compliant Security Group is detected, it should be automatically remediated. Which service provides this?
    1. CloudWatch Alarm with Lambda
    2. CloudTrail with EventBridge rule
    3. AWS Config Rule with auto-remediation
    4. GuardDuty
  3. An operations team wants to receive an alert when EC2 CPU utilization exceeds 90% for more than 5 minutes and automatically add instances to the fleet. Which service and feature enables this?
    1. CloudTrail with SNS
    2. Config Rule with remediation
    3. CloudWatch Alarm with Auto Scaling action
    4. EventBridge with Step Functions
  4. A compliance auditor needs to see the complete configuration history of an RDS instance over the past 6 months, including every change to its configuration. Which service provides this timeline view?
    1. CloudTrail event history
    2. CloudWatch Logs
    3. AWS Config (configuration timeline)
    4. RDS event notifications
  5. An organization wants to detect when an unusually high number of API calls are made to IAM (potential credential compromise). Which service and feature is purpose-built for this?
    1. CloudWatch Anomaly Detection
    2. Config Rule
    3. CloudTrail Insights
    4. GuardDuty

Related Posts

References

Amazon CloudWatch User Guide

AWS CloudTrail User Guide

AWS Config Developer Guide

AWS KMS vs CloudHSM vs Secrets Manager vs Parameter Store

AWS KMS vs CloudHSM vs Secrets Manager vs Parameter Store

  • AWS provides multiple services for managing encryption keys and secrets, each designed for different security requirements and use cases.
  • KMS is managed key management, CloudHSM is dedicated hardware security modules, Secrets Manager is for rotating secrets, and Systems Manager Parameter Store is for configuration and secrets storage.
  • Choice depends on compliance requirements (FIPS 140-2 Level 3), key control needs, rotation requirements, and cost.

KMS vs CloudHSM vs Secrets Manager vs Parameter Store Comparison

Feature KMS CloudHSM Secrets Manager Parameter Store
Purpose Managed encryption key service Dedicated HSM for key management Secret storage with automatic rotation Configuration & secret storage
Key Control AWS manages HSM, you manage keys You manage everything (single-tenant HSM) Uses KMS for encryption Uses KMS for encryption (SecureString)
FIPS 140-2 Level 3 (since 2023) Level 3 N/A (uses KMS) N/A (uses KMS)
Multi-tenancy Multi-tenant (shared infrastructure) Single-tenant (dedicated hardware) Multi-tenant Multi-tenant
Automatic Rotation Yes (annual for AWS-managed, configurable 90-365 days for customer-managed) Manual (you control rotation) Yes (built-in for RDS, Redshift, DocumentDB; Lambda for custom) No built-in rotation
Cross-account Yes (key policy + IAM) No (same VPC/account) Yes (resource policy) Yes (resource policy, Advanced tier)
Cross-region Multi-Region keys Cluster in single region Multi-Region secret replication No native replication
Max Secret Size 4KB (symmetric key operations) Unlimited (HSM capacity) 64KB 4KB (Standard) / 8KB (Advanced)
Pricing $1/month per key + API calls ~$1.50/hour per HSM ($1,095/month) $0.40/secret/month + API calls Free (Standard) / $0.05/parameter/month (Advanced)
Versioning Automatic (rotation creates new version) Manual Yes (staging labels: AWSCURRENT, AWSPREVIOUS) Yes (up to 100 versions)
Audit CloudTrail CloudTrail + HSM audit logs CloudTrail CloudTrail
AWS Integration 100+ services natively Custom integration required RDS, Redshift, DocumentDB, ECS, Lambda ECS, Lambda, CloudFormation, CodeDeploy
Key Types Symmetric (AES-256), Asymmetric (RSA, ECC), HMAC Symmetric, Asymmetric, HMAC, custom algorithms N/A (stores secrets, not keys) N/A (stores values)

AWS KMS (Key Management Service)

  • Fully managed encryption key service integrated with 100+ AWS services.
  • Three key types: AWS owned (free, AWS-managed), AWS managed (auto-created per service), Customer managed (full control).
  • Envelope encryption – generates data keys for encrypting data locally; KMS never stores data keys.
  • Multi-Region keys – replicate keys across regions for cross-region encryption/decryption.
  • Key policies + IAM – fine-grained access control; grants for temporary access.
  • Automatic key rotation – configurable 90-365 days for customer-managed keys (was annual only before 2024).
  • External Key Store (XKS) – use keys stored in your own HSM outside AWS.
  • FIPS 140-2 Level 3 validated since March 2023.
  • Best for: Most encryption use cases – S3, EBS, RDS, DynamoDB, Lambda, and 100+ other AWS services.

AWS CloudHSM

  • Dedicated, single-tenant HSM instances in your VPC – you own and manage the keys.
  • FIPS 140-2 Level 3 validated hardware – required for certain regulatory compliance.
  • Full key control – AWS cannot access your keys; AWS manages hardware only.
  • Supports PKCS#11, JCE, CNG, and OpenSSL interfaces for custom applications.
  • Cluster-based – deploy across multiple AZs for HA; keys automatically replicated.
  • Custom key store for KMS – back KMS keys with CloudHSM for compliance + service integration.
  • SSL/TLS offloading – use CloudHSM for web server private keys.
  • Code signing, certificate authority – custom crypto operations not available in KMS.
  • Best for: Regulatory compliance (PCI-DSS, HIPAA requiring dedicated HSM), custom cryptographic operations, SSL offloading, certificate authorities.

AWS Secrets Manager

  • Purpose-built for managing secrets (database credentials, API keys, tokens).
  • Automatic rotation – built-in for RDS (MySQL, PostgreSQL, Oracle, SQL Server, MariaDB), Redshift, DocumentDB; Lambda-based for custom secrets.
  • Multi-Region replication – replicate secrets across regions for DR and multi-region applications.
  • Versioning with staging labels – AWSCURRENT, AWSPREVIOUS, AWSPENDING during rotation.
  • Resource-based policies – share secrets cross-account.
  • Integration – ECS/Fargate (inject as environment variables), Lambda, RDS Proxy.
  • Batch retrieval – retrieve up to 20 secrets in a single API call.
  • Best for: Database credentials that need automatic rotation, API keys, OAuth tokens, any secret requiring lifecycle management.

Systems Manager Parameter Store

  • Hierarchical configuration storage for both configuration data and secrets.
  • Two tiers: Standard (free, 4KB, 10K params) and Advanced ($0.05/month, 8KB, 100K params).
  • Parameter types: String, StringList, SecureString (encrypted with KMS).
  • Hierarchy and tagging – organize parameters like /prod/db/password, /dev/api/key.
  • No built-in rotation – use EventBridge + Lambda for custom rotation.
  • Parameter policies (Advanced tier) – expiration notifications, no-change notifications.
  • Public parameters – AWS provides latest AMI IDs, ECS-optimized AMI, etc.
  • CloudFormation integration – resolve parameters dynamically during stack creation.
  • Best for: Application configuration, feature flags, non-rotating secrets, AMI IDs, and cost-sensitive use cases where rotation isn’t needed.

When to Choose Which

  • Choose KMS – Encrypting data in AWS services (S3, EBS, RDS), envelope encryption, most standard encryption needs.
  • Choose CloudHSM – Regulatory requirement for dedicated HSM (FIPS 140-2 Level 3 single-tenant), custom cryptographic operations, SSL offloading, running your own CA.
  • Choose Secrets Manager – Database credentials needing automatic rotation, API keys with lifecycle management, cross-region secret replication.
  • Choose Parameter Store – Application configuration, feature flags, non-rotating secrets, cost-sensitive (free tier), hierarchical organization of config data.
  • Combine KMS + Secrets Manager – Secrets Manager uses KMS for encryption; use customer-managed KMS key for additional control.
  • Combine CloudHSM + KMS – Use CloudHSM as a custom key store backing KMS keys (compliance + service integration).

AWS Certification Exam Practice Questions

  1. A company needs to store database credentials that automatically rotate every 30 days and are accessible from ECS tasks as environment variables. Which service is most appropriate?
    1. KMS with custom rotation
    2. Parameter Store SecureString
    3. Secrets Manager
    4. CloudHSM
  2. A financial institution must use dedicated hardware security modules (not shared) for key management to satisfy PCI-DSS Level 1 compliance. Which service meets this requirement?
    1. KMS with customer-managed keys
    2. CloudHSM
    3. KMS with external key store
    4. Secrets Manager with KMS
  3. A development team needs to store application configuration values (non-sensitive) and sensitive database passwords together in a hierarchical structure with minimal cost. Which approach is recommended?
    1. Secrets Manager for all values
    2. Parameter Store (String for config, SecureString for passwords)
    3. KMS encrypted S3 bucket
    4. DynamoDB with encryption
  4. An application needs encryption keys that work identically across 3 AWS regions for cross-region data encryption/decryption without re-encrypting. Which feature enables this?
    1. CloudHSM cluster replication
    2. Secrets Manager multi-region secrets
    3. KMS Multi-Region keys
    4. KMS key import in each region
  5. A company wants to use AWS KMS for service integrations but needs their keys to remain in their on-premises HSM that they fully control. Which KMS feature supports this?
    1. CloudHSM custom key store
    2. KMS imported key material
    3. KMS External Key Store (XKS)
    4. KMS with VPN connection

Related Posts

References

AWS KMS Developer Guide

AWS CloudHSM User Guide

AWS Secrets Manager User Guide

AWS Systems Manager Parameter Store

AWS Container Services Cheat Sheet

AWS Container Services Cheat Sheet

  • AWS provides a full container stack: orchestration (ECS, EKS), compute (Fargate, EC2), registry (ECR), and supporting services (App Mesh, Cloud Map, Proton).
  • Containers package applications with dependencies for consistent deployment across environments.

Container Orchestration

Amazon ECS (Elastic Container Service)

  • AWS-native container orchestrator – deeply integrated with IAM, CloudWatch, ALB, VPC.
  • Task Definition – blueprint for containers (image, CPU, memory, ports, IAM role, volumes).
  • Service – maintains desired count of tasks, integrates with load balancers, handles rolling updates.
  • Launch types: EC2 (you manage instances) or Fargate (serverless).
  • No control plane cost – free; pay only for EC2 or Fargate compute.
  • Capacity Providers – automatic EC2 Auto Scaling and Fargate/Fargate Spot management.
  • Service Connect – simplified service-to-service communication (built-in service mesh).
  • ECS Exec – interactive shell into running containers for debugging.
  • ECS Anywhere – run ECS tasks on on-premises servers.
  • Blue/Green deployments – native CodeDeploy integration.

Amazon EKS (Elastic Kubernetes Service)

  • Managed Kubernetes – certified conformant, runs upstream K8s.
  • Control plane: fully managed by AWS ($0.10/hour per cluster).
  • Compute options: Managed Node Groups, Self-Managed Nodes, Fargate, EKS Auto Mode.
  • EKS Auto Mode – AWS manages nodes, scaling, upgrades, and security patches automatically.
  • Add-ons: CoreDNS, kube-proxy, VPC CNI, EBS CSI, managed via EKS.
  • EKS Anywhere – run Kubernetes on-premises with EKS management.
  • EKS Connector – register external Kubernetes clusters to the EKS console.
  • Full Kubernetes ecosystem: Helm, Karpenter, Istio, ArgoCD, Prometheus, etc.

Compute

AWS Fargate

  • Serverless compute for ECS and EKS – no EC2 to manage.
  • Per-task pricing: vCPU-hour + GB-hour (per second billing, 1-min minimum).
  • Isolation: each task/pod runs in its own Firecracker microVM.
  • Fargate Spot: up to 70% discount; tasks can be interrupted with 2-min warning.
  • Limitations: no GPU, no EBS, no daemonsets, no privileged containers.
  • Storage: 20GB ephemeral per task (configurable up to 200GB) + EFS supported.

Container Registry

Amazon ECR (Elastic Container Registry)

  • Fully managed Docker container registry – stores, manages, and deploys container images.
  • Private repositories with IAM-based access control.
  • Public repositories (ECR Public Gallery) for open-source images.
  • Image scanning – automatic vulnerability scanning (Basic with Clair, or Enhanced with Inspector).
  • Lifecycle policies – automatically clean up old/untagged images.
  • Cross-region and cross-account replication.
  • Image immutability – prevent image tags from being overwritten.
  • OCI support – stores OCI images and Helm charts.

Networking & Service Discovery

AWS App Mesh

  • Service mesh using Envoy proxy for traffic management, observability, and security between services.
  • Supports ECS, EKS, and EC2 workloads.
  • Features: traffic routing, retries, timeouts, circuit breaking, mutual TLS.

Amazon VPC Lattice

  • Application-layer networking – connect, secure, and monitor services across VPCs and accounts.
  • Simpler than App Mesh – no sidecar proxies needed.
  • Supports ECS, EKS, Lambda, and EC2 targets.

AWS Cloud Map

  • Service discovery – register and discover services using DNS or API.
  • Health checking for registered instances.
  • Used by ECS Service Connect and App Mesh.

CI/CD & DevOps

  • AWS CodePipeline – CI/CD pipeline automation for container deployments.
  • AWS CodeBuild – build container images (docker build + push to ECR).
  • AWS CodeDeploy – blue/green deployments for ECS services.
  • AWS Proton – managed delivery service for container and serverless application templates.
  • AWS Copilot – CLI for building, releasing, and operating containerized apps on ECS.

Monitoring & Logging

  • CloudWatch Container Insights – metrics and logs for ECS and EKS (CPU, memory, network, disk per task/pod).
  • AWS X-Ray – distributed tracing for containerized microservices.
  • FireLens – ECS log router using Fluent Bit/Fluentd to send logs to CloudWatch, S3, Splunk, Datadog.
  • CloudWatch Logs – awslogs driver for ECS; Fluent Bit DaemonSet for EKS.

AWS Certification Exam Practice Questions

  1. A team wants to run containers without managing any infrastructure and needs the lowest operational overhead. They don’t use Kubernetes. Which combination is correct?
    1. EKS with Fargate
    2. ECS with Fargate
    3. ECS with EC2
    4. EKS with Managed Node Groups
  2. A company needs to automatically scan container images for vulnerabilities when pushed to the registry. Which service and feature provides this?
    1. ECS image scanning
    2. ECR Enhanced Scanning (with Amazon Inspector)
    3. GuardDuty container protection
    4. AWS Config rules
  3. An application needs service-to-service communication with mutual TLS, traffic routing, and retry policies across ECS and EKS services. Which service provides this?
    1. VPC Lattice
    2. Cloud Map
    3. AWS App Mesh
    4. ECS Service Connect
  4. A company needs to run Kubernetes on-premises while managing it with the same tools used for their AWS EKS clusters. Which service supports this?
    1. ECS Anywhere
    2. EKS Anywhere
    3. EKS Connector
    4. AWS Outposts

Related Posts

References

Amazon ECS Developer Guide

Amazon EKS User Guide

Amazon ECR User Guide

AWS Storage Services Cheat Sheet

AWS Storage Services Cheat Sheet

  • AWS provides storage services across four categories: Object (S3), Block (EBS), File (EFS, FSx), and Hybrid/Edge (Storage Gateway, Snow Family).
  • Each is optimized for different access patterns, latency requirements, and cost profiles.

Object Storage

Amazon S3

  • Unlimited object storage with 99.999999999% (11 nines) durability.
  • Max object size: 5TB; multipart upload for objects >100MB.
  • Storage Classes:
    • S3 Standard – frequently accessed, low latency, high throughput.
    • S3 Intelligent-Tiering – automatic cost optimization with access pattern monitoring.
    • S3 Standard-IA – infrequent access, lower storage cost, retrieval fee.
    • S3 One Zone-IA – single AZ, 20% cheaper than Standard-IA.
    • S3 Glacier Instant Retrieval – archive with millisecond access.
    • S3 Glacier Flexible Retrieval – archive, 1-12 hour retrieval.
    • S3 Glacier Deep Archive – lowest cost, 12-48 hour retrieval.
    • S3 Express One Zone – single-digit millisecond, single AZ, for analytics.
  • Lifecycle Policies – automatically transition objects between classes or expire them.
  • Versioning – keep multiple versions; protect against accidental deletes.
  • Replication – Cross-Region (CRR) or Same-Region (SRR) replication.
  • Object Lock – WORM (Write Once Read Many) for compliance (Governance or Compliance mode).
  • S3 Event Notifications – trigger Lambda, SQS, SNS, EventBridge on object events.
  • S3 Transfer Acceleration – faster uploads using CloudFront edge locations.
  • S3 Select / Glacier Select – retrieve subset of data using SQL.
  • Encryption: SSE-S3 (default), SSE-KMS, SSE-C, client-side.
  • Access Control: Bucket policies, IAM policies, ACLs (legacy), Access Points, Block Public Access.

Block Storage

Amazon EBS

  • Persistent block storage for EC2 instances.
  • Volume Types:
    • gp3 – general purpose SSD, 3,000 IOPS baseline, up to 16,000 IOPS. Cost-effective default.
    • gp2 – general purpose SSD, burst up to 3,000 IOPS (legacy, prefer gp3).
    • io2 Block Express – highest performance SSD, up to 256,000 IOPS, sub-ms latency. For databases.
    • io1 – provisioned IOPS SSD, up to 64,000 IOPS.
    • st1 – throughput-optimized HDD, up to 500 MB/s. For big data, data warehouses.
    • sc1 – cold HDD, lowest cost, up to 250 MB/s. For infrequent access.
  • Single AZ – must be in same AZ as EC2 instance.
  • Snapshots – point-in-time backups to S3 (incremental); can copy cross-region.
  • Multi-Attach – io2 volumes can attach to up to 16 Nitro instances in same AZ.
  • Encryption – AES-256 via KMS; encrypt at rest, in transit, and snapshots.
  • Elastic Volumes – resize, change type, or adjust IOPS without downtime.

EC2 Instance Store

  • Ephemeral block storage physically attached to host – highest IOPS/throughput.
  • Data lost on instance stop/terminate/failure.
  • Use for: temporary buffers, caches, scratch data.

File Storage

Amazon EFS

  • Managed NFS (NFSv4.1) – concurrent access from multiple EC2, ECS, Lambda.
  • Elastic – grows/shrinks automatically; pay only for what you use.
  • Performance modes: General Purpose (latency-sensitive) and Max I/O (high parallelism).
  • Throughput modes: Elastic (auto), Bursting, Provisioned.
  • Storage classes: Standard, Infrequent Access (IA), Archive – with lifecycle management.
  • Regional – data stored across multiple AZs; One Zone option available at lower cost.
  • Supports cross-region replication for DR.

Amazon FSx

  • FSx for Windows File Server – managed Windows SMB with Active Directory, DFS, VSS.
  • FSx for Lustre – high-performance parallel file system (HPC, ML). Integrates with S3.
  • FSx for NetApp ONTAP – multi-protocol (NFS, SMB, iSCSI) with snapshots, clones, tiering.
  • FSx for OpenZFS – high-performance NFS with snapshots and data compression.

Hybrid & Edge Storage

AWS Storage Gateway

  • Hybrid cloud storage connecting on-premises to AWS.
  • S3 File Gateway – NFS/SMB access to S3 objects.
  • FSx File Gateway – local cache for FSx for Windows File Server.
  • Volume Gateway – iSCSI block storage backed by S3 (Cached or Stored mode).
  • Tape Gateway – virtual tape library (VTL) backed by S3/Glacier.

AWS Snow Family

  • Snowcone – 8-14TB, portable edge computing and data transfer.
  • Snowball Edge – 80-210TB, Storage Optimized or Compute Optimized.
  • Snowmobile – 100PB, exabyte-scale data migration (truck).
  • Use for: offline data migration, edge computing where connectivity is limited.

AWS DataSync

  • Automated data transfer – on-premises to AWS (S3, EFS, FSx) or between AWS services.
  • Up to 10x faster than open-source tools; built-in scheduling, integrity validation.

AWS Transfer Family

  • Managed SFTP, FTPS, FTP, and AS2 transfers directly to/from S3 or EFS.

AWS Certification Exam Practice Questions

  1. A company needs to store 500TB of data that is rarely accessed (once per quarter) but must be retrievable within milliseconds. Which storage class is most cost-effective?
    1. S3 Standard
    2. S3 Standard-IA
    3. S3 Glacier Instant Retrieval
    4. S3 Glacier Deep Archive
  2. A database requires 100,000 IOPS with sub-millisecond latency on a single EC2 instance. Which EBS volume type should be used?
    1. gp3
    2. io1
    3. io2 Block Express
    4. st1
  3. Multiple EC2 instances across AZs need shared access to a POSIX-compliant file system with automatic capacity scaling. Which service fits?
    1. EBS Multi-Attach
    2. S3
    3. EFS
    4. FSx for Lustre
  4. A company needs to migrate 50TB of on-premises data to S3, but their internet connection would take 2 weeks. Which service provides faster physical transfer?
    1. S3 Transfer Acceleration
    2. DataSync
    3. Snowball Edge
    4. Storage Gateway
  5. An on-premises application uses NFS to access files that must be stored in S3 for durability. Which service provides this transparent NFS-to-S3 bridge?
    1. EFS
    2. FSx for ONTAP
    3. S3 File Gateway
    4. DataSync

Related Posts

References

Amazon S3 User Guide

Amazon EBS User Guide

Amazon EFS User Guide

AWS Storage Gateway User Guide