PuglieseWeb
  • Home
  • Software development
    • Cloud Data Security Principles
      • Separation of Duties (SoD)
      • Security Controls and Data Protection Framework
      • Vaultless Tokenization
    • Multi-cloud strategies
    • DMS
      • How CDC Checkpoints Work
      • Oracle to PostgreSQL Time-Window Data Reload Implementation Guide
      • Join tables separate PostgreSQL databases
      • Multi-Stage Migration Implementation Plan
      • Notes
      • Oracle Golden Gate to PostgreSQL Migration
      • Step-by-Step CDC Recovery Guide: Oracle to PostgreSQL Migration
    • AWS Pro
      • My notes
        • Data Migration Strategy
        • OpsWorks VS CloudFormation
      • Implementation Guides
        • AWS Lambda Scaling and Concurrency Optimization Guide
        • Understanding Cross-Account IAM Roles in AWS
        • HA TCP with Redundant DNS
        • Understanding 429 (Too Many Requests) & Throttling Pattern
        • EC2 Auto Scaling Log Collection Solutions Comparison
        • AWS PrivateLink Implementation Guide for Third-Party SaaS Integration
        • AWS Cross-Account Network Sharing Implementation Guide
        • Cross-Account Route 53 Private Hosted Zone Implementation Guide
          • Route 53
            • Routing Policies
              • Using a Weighted Routing Policy
              • Simple Routing Policy
              • Multivalue Answer Routing
            • Latency Routing Policy
            • Route 53 Traffic Flow
        • Direct Connect Gateway Implementation Guide
        • CICD for Lambda
        • AWS IAM Identity Center Integration with Active Directory
        • AWS Transit Gateway Multi-Account Implementation Guide
          • AWS Multi-Account Network Architecture with Infrastructure Account
      • Links
      • Cloud Adoption Framework
      • Data Stores
        • Data Store Types and Concepts in AWS
        • S3
          • Amazon S3 (Simple Storage Service)
            • Bucket Policies
          • Managing Permissions in Amazon S3
          • Amazon Glacier: AWS Archive Storage Service
          • Lab: Querying Data in Amazon S3 with Amazon Athena
          • LAB: Loading Data into a Redshift Cluster
        • Attached Storage
          • EBS
          • AWS Elastic File System (EFS): From Sun Microsystems to Modern Cloud Storage
          • AWS FSx Service Guide
          • Amazon Storage Gateway Guide
        • Databases
          • Amazon Storage Gateway Guide
          • Amazon RDS (Relational Database Service)
          • Aurora DB
          • Dynamo DB
          • Document DB
          • Amazon Redshift Overview
          • Data Pipeline
            • Data Lake VS Lake Formation
          • AWS Data Preparation Services
          • Amazon Neptune
          • Amazon ElastiCache
          • AWS Specialized Database Services
          • LAB - Deploy an Amazon RDS Multi-AZ and Read Replica in AWS
      • Networking
        • Concept
        • Basics
          • VPG
          • VPC
            • VPC endpoints
              • Interface Endpoint VS Elastic Network Interface (ENI)
            • PrivateLink
              • PrivateLink SAAS Use case
            • Transit Gateway
            • 5G Networks
            • VPN CloudHub
            • VPC security
            • VPC peering
            • VPC Endpoint
            • Route Table (and Routers)
            • Network Access Control List (NACL)
            • Network Security Group
            • NAT Gateway
              • NACL vs NAT
          • Elastic Load Balancing (ELB)
            • Gateway Load Balancer (GWLB)
          • CIDR ranges examples
          • Enhanced Networking
          • Elastic Fabric Adapter (EFA)
          • Elastic Network Interface (ENI)
        • Network to VPC Connectivity
          • Transit VS Direct Connect Gateway
          • Direct Connect
            • VIF (Virtual Interfaces)
            • VIF VS ENI
            • Customer Routers VS Customer Gateways
        • VPC-to-VPC
        • NAT & Internet Gateway
        • Routing
          • IPv4 Address Classes and Subnet Masks
          • VPC's DNS server
          • Transit VPC VS Transit Gateway
          • Example Routing tables configuration
          • Cross-regions failover
          • Loopback
        • Enhanced Networking
        • Hybrid and Cross-Account Networking
        • AWS Global Accelerator
        • Route 53
        • Cross-Account Route 53
        • CloudFront SSL/TLS and SNI Configuration
        • ELB
        • Lab: Creating a Multi-Region Network with VPC Peering Using SGs, IGW, and RTs
        • LAB - Creating a CloudFront Distribution with Regional S3 Origins
        • Lab: Creating and Configuring a Network Load Balancer in AWS
        • Lab: Troubleshooting Amazon EC2 Network Connectivity
        • Lab: Troubleshooting VPC Networking
      • Security
        • Cloud Security
          • IAM
            • SCIM
            • Use case 1
          • Core Concepts of AWS Cloud Security
            • OAuth VS OpenID Connect
          • Understanding User Access Security in AWS Organizations
          • Exploring Organizations
          • Controlling Access in AWS Organizations
            • SCP (Service Control Policy) implementation types
        • Network Controls and Security Groups
          • Firewalls
            • Network Controls and Security Groups Overview
          • AWS Directory Services
          • AWS Identity and Access Management (IAM) and Security Services
            • ASW Identity Sources
          • AWS Resource Access Manager (RAM): Cross-Account Resource Sharing
            • AWS App Mesh
        • Encryption
          • History and Modern Implementation of Encryption in AWS
          • Secret Manager
          • DDoS Attacks and AWS Protection Strategies: Technical Overview
          • AWS Managed Security Services Overview
          • IDS and IPS
          • AWS Service Catalog
      • Migrations
        • Migration Concepts
          • Hybrid Cloud Architectures
          • Migration Strategies
        • Migration Application
          • Services and Strategies
          • AWS Data Migration Services
          • Network Migrations and Cutovers
            • Network and Broadcast Addresses
            • VPC DNS
          • AWS Snow Family
      • Architecting to scale
        • Scaling Concepts and Services
          • Auto-Scaling
          • Compute Optimizer
          • Kinesis
          • DynamoDB Scaling
          • CloudFront Part Duex
            • CloudFront's Behavior
            • Lambda@Edge and CloudFront Functions
        • Event-Driven Architecture
          • SNS and Fan-out Architecture
            • SNS & outbox pattern
          • AWS Messaging Services: SQS and Amazon MQ
          • Lab: Scaling EC2 Using SQS
          • Lambda
          • Scaling Containers in AWS
          • Step Function and Batch
          • Elastic MapReduce
          • AWS Data Monitoring and Visualization Services
      • Business Continuity
        • AWS High Availability and Disaster Recovery
        • AWS Disaster Recovery Architectures
        • EBS Volumes
        • AWS Compute Options for High Availability
        • AWS Database High Availability Options
        • AWS Network High Availability Options
        • Lab: Connect Multiple VPCs with Transit Gateway
        • Deployment and Operations Management
          • Software Deployment Strategies
            • AWS CI/CD
            • Elastic Beanstalk
              • Elastic Beanstalk and App Runner
            • CloudFormation
            • Cross-Account Infrastructure Deployment
              • Example Code Pipeline
            • AWS Container Services
            • AWS API Gateway
            • LAB: Understanding CloudFormation Template Anatomy
          • Management Tool
            • Config and OpsWorks
            • System Manager
            • Enterprise Apps
            • AWS Machine Learning Landscape
            • AWS IoT Services
      • Cost Management and Optimization
        • Concepts
        • AWS Cost Optimization Strategies
        • AWS Tagging and Resource Groups
        • Managing Costs Across AWS Accounts
        • AWS Instance Purchasing Options
        • AWS Cost Management Tools
      • Others
        • SCPs vs AWS Config
        • Questions notes
        • Comparison of Deployment Strategies in AWS
        • Bedrock vs EMR
        • Software Deployment Strategies
    • AWS
      • Others
        • AWS Example architectures
          • Gaming application
          • Digital Payment System
            • Marketplace Application
            • Analytics & Reporting System MVP
            • Reporting System 2
            • Data Pipeline
            • Monitoring and visualization solution for your event-driven architecture (EDA) in AWS.
              • Visualize how services are linked together for each business flow
              • Visualize flow and metrics
            • Reporting
            • Data
        • AWS Key Learning
        • AWS NFRs
          • AWS Integration Pattern Comparison Matrix
          • AWS 99.999% Architecture
        • AWS Best Practices
          • use S3 for data migration
          • Principle of centralized control
          • For CPU Spikes in DB use RDS Proxy
          • API Security
          • Lambda VS ECS
          • Use CloudFront for Dynamic content
        • ECS Sizing
        • AWS Q&A
          • AWS Prep
          • prepexam
          • Big Data/ AI Q&A
          • DB Q&A
          • AWS Application Servers Q&A
          • General Q&A
          • VPC Q&A
      • DRs
      • AI, Analytics, Big Data, ML
        • EMR
          • Flink
          • Spark
          • Hadoop
            • Hive
        • Extra
          • Glue and EMR
          • Redshift Use Cases
        • AI
          • Media Services (Elastic Transcoder, Kinesis)
          • Textract
          • Rekognition (part of the exam)
          • Comprehend
          • Kendra
          • Fraud Detector
          • Transcribe, Polly, Lex
          • Translate
          • Time-series and Forecast
        • Big Data
          • Processing & Analytics
            • Amazon Athena VS Amazon Redshift
            • Athena & AWS Glue: Serverless Data Solutions
          • BigData Storage Solutions
          • EMR
        • Business intelligence
        • Sagemaker
          • SageMaker Neo
          • Elastic Inference (EI)
          • Integration patterns with Amazon SageMaker
          • Common Amazon SageMaker Endpoint usage patterns
          • Real-time interfaces
          • ML Example
        • Machine Learning
          • Data Engineering
            • Understanding Data Preparation
            • Feature Engineering: Transforming Raw Data into Powerful Model Inputs
            • Feature Transformation and Scaling in Machine Learning
            • Data Binning: Transforming Continuous Data into Meaningful Categories
          • Exploratory Data Analysis
            • Labs
              • Perform Feature Engineering Using Amazon SageMaker
            • Categorical Data Encoding: Converting Categories to Numbers
            • Text Feature Extraction for Machine Learning
            • Feature Extraction from Images and Speech: Understanding the Fundamentals
            • Dimensionality Reduction and Feature Selection in Machine Learning
          • Modelling
            • Prerequisites for Machine Learning Implementation
            • Classification Algorithms in Machine Learning
            • Understanding Regression Algorithms in Machine Learning
            • Time Series Analysis: Fundamentals and Applications
            • Clustering Algorithms in Machine Learning
      • Databases
        • Capturing data modification events
        • Time-Series Data (Amazon Timestream)
        • Graph DBs
          • Amazon Neptune
        • NoSQL
          • Apache Cassandra (Amazon Keyspaces)
          • Redshift
            • Redshift's ACID compliance
          • MongoDB (Amazon DocumentDB)
          • DynamoDB
            • Additional DynamoDB Features and Concepts
            • DynamoDB Consistency Models and ACID Properties
            • DynamoDB Partition Keys
          • Amazon Quantum Ledger DB (QLDB)
        • RDS
          • DR for RDS
          • RDS Multi-AZ VS RDS Proxy
          • Scaling Relational Databases
          • Aurora Blue/Green deployments
          • Aurora (Provisioned)
          • Amazon Aurora Serverless
        • Sharing RDS DB instance with an external auditor
      • Caching
        • DAX Accelerator
        • ElastiChache
        • CloudFront (External Cache)
        • Global Accelerator (GA)
      • Storages
        • S3
          • MFA Delete VS Object Lock
          • S3 Standard VS S3 Intelligent-Tiering
        • Instance Storage
        • EBS Volumes
          • Burst Capacity & Baseline IOPS
          • Provisioned IOPS vs GP3
          • EBS Multi-Attach
        • Snapshots
        • AWS Backup
        • File Sharing
          • FSx (File system for Windows or for Lustre)
          • EFS (Elastic File System)
      • Migration
        • Migration Hub
        • Application Discovery Service
        • Snow Family
        • DMS
        • SMS (Server Migration Service)
        • MGN (Application Migration Service)
        • Transfer family
        • DataSync
        • Storage Gateway
          • Volume gateway
          • Tape Gateway
          • File Gateway
          • Storage Gateway Volume Gateway VS Storage Gateway File Gateway
        • DataSync VS Storage Gateway File Gateway
      • AWS Regional Practices and Data Consistency Regional Isolation and Related Practices
      • Front End Web application
        • Pinpoint
        • Amplify
        • Device Farm
      • Glossary
      • Governance
        • Well-Architected Tool
        • Service Catalog and Proton
          • AWS Service Catalog
          • AWS Proton
        • AWS Health
        • AWS Licence Manager
        • AWS Control Tower
        • AWS Trusted Advisor
        • Saving Plans
        • AWS Compute Optimizer
        • AWS CUR
        • Cost Explorer and Budgets
        • Directory Service
        • AWS Config
        • Cross-Account Role Access
        • Resource Access Manager (RAM)
        • Organizations, Accouts, OU, SCP
      • Automation
        • System Manager (mainly for inside EC2 instances)
        • Elastic Beanstalk (for simple solutions)
        • IaC
          • SAM
          • CloudFormation
            • !Ref VS !GetAtt
            • CloudFormation examples
      • Security
        • Identity Management Services
          • IAM
            • Identity, Permission, Trust and Resource Policies
              • IAM Policy Examples
              • Trust policy
            • IAM roles cannot be attached to IAM Groups
            • AWS IAM Policies Study Guide
            • Cross-Account Access in AWS: Resource-Based Policies vs IAM Roles
            • EC2 instance profile VS Trust policy
          • Cognito
        • STS
        • AI based security
          • GuardDuty
          • Macie (S3)
        • AWS Network Firewall
        • Security Hub
        • Detective (Root Cause Analysis)
        • Inspector (EC2 and VPCs)
        • System Manager Parameter Store
        • Secret Manager
          • Secret Manger VS System Manager's Parameter Store
          • Secret Manager VS AWS KMS
        • Shield
          • DDoS
        • KMS vs CloudHSM
        • Firewall Manager
        • AWS WAF
      • Compute
        • Containers
          • ECS
            • ECS Anywhere
          • EKS
            • EKS Anywhere
          • Fargate
            • ECS Fargate VS EKS Fargate
          • ECR (Elastic Container Registry)
        • EC2
          • EC2 Purchase Options
            • Spot instances VS Spot Fleet
          • EC2 Instance Types
            • T Instance Credit System
          • Auto Scaling Groups (ASG)
          • Launch Template vs. Launch Configuration
          • AMI
          • EC2 Hibernation
        • Lambda
          • Publish VS deploy
      • Data Pipeline
      • ETL
      • AppFlow
      • AppSync
      • Step Functions
      • Batch
        • Spring Boot Batch VS AWS Batch
      • Decoupling Workflow
      • Elastic Load Balancers
      • Monitoring
        • OpenSearch
        • CloudWatch Logs Insights VS AWS X-Ray
        • QuickSight
        • Amazon Managed Service for Prometheus
        • Amazon Managed Grafana
        • CloudWatch Logs Insights
          • CloudWatch Logs Insights VS Kibana VS Grafana
        • CloudWatch Logs
        • CloudTrail
        • CloudWatch
        • X-Ray
      • On-Premises
        • ECS/EKS Anyware
        • SSM Agent
      • Serverless Application Repository
      • Troubleshooting
      • Messaging, Events and Streaming
        • Kinesis (Event Stream)
        • EventBridge (Event Router)
          • EventBridge Rule Example
          • EventBridge vs Apache Kafka
          • EventBridge VS Kinesis(Event Stream)
          • Event Bridge VS SNS
        • SNS (Event broadcaster)
        • SQS (Message Queue)
        • MSK
        • Amazon MQ
        • DLQ
    • Software Design
      • CloudEvents
        • CloudEvents Kafka
      • Transaction VS Operation DBs
      • Event-based Microservices
        • Relations database to event messages
      • Hexagonal Architecture with Java Spring
      • Distributed Systems using DDD
        • Scaling a distributed system
        • Zookeeper
        • Aggregates
        • Bounded Context
      • API Gateway
      • Cloud
        • The Twelve Factors
        • Open Service Broker API
      • Microservices
    • Design technique
    • Technologies
      • Kafka
      • Docker
        • Docker Commands
        • Artifactory
        • Dockerfile
      • ReactJs
        • Progressive Web App (PWA)
        • Guide to File Extensions in React Projects
    • Guides
      • OCP
      • AWS
        • Creating and Assuming an Administrator AWS IAM Role
        • Standing Up an Amazon Aurora Database with an Automatically Rotated Password Using AWS Secrets Manag
        • Standing Up an Apache Web Server EC2 Instance and Sending Logs to Amazon CloudWatch
        • Creating a Custom AMI and Deploying an Auto Scaling Group behind an Application Load Balancer
        • Assigning Static IPs to NLBs with ALB Target Groups
        • Hosting a Wordpress Application on ECS Fargate with RDS, Parameter Store, and Secrets Manager
        • Amazon Athena, Amazon S3, and VPC Flow Logs
      • Creating a CloudTrail Trail and EventBridge Alert for Console Sign-Ins
      • Load Balancer VS Reverse Proxy
      • Health check
      • Load Balancer
      • HTTP Protocol
      • TCP/IP Network Model
      • Event-base Microservices Implementation Guideline
      • How to write a service
      • Observability
      • Kafka Stream
      • Security
        • Securing Properties
          • HashiCorp Vault
      • Kubernates
      • Unix
        • Networking
        • Firewall
        • File system
        • alternatives
      • Setup CentOS 8 and Docker
    • Dev Tools
      • Docker Commands
      • Intellij
      • CheatSheets
        • Unix Commands
        • Vim Command
      • Templates
  • Working for an enterprise
    • Next step
    • Job roles
      • SME role
    • Common issues
Powered by GitBook
On this page

Was this helpful?

  1. Software development
  2. AWS
  3. Others
  4. AWS Q&A

AWS Prep

PreviousAWS Q&ANextprepexam

Last updated 7 months ago

Was this helpful?

  • A solutions architect is designing a database solution that must support a high rate of random disk reads and writes. It must provide consistent performance, and requires long-term persistence.

Provisioned IOPS volumes support a high rate of random disk reads and writes. Provisioned IOPS volumes handle I/O-intensive workloads (particularly database workloads) that are sensitive to storage performance and consistency. Provisioned IOPS volumes use a consistent IOPS rate that you specify when you create them. Amazon EBS delivers the provisioned performance 99.9% of the time.

A solutions architect at an ecommerce company wants to store application log data using Amazon S3. The solutions architect is unsure how frequently the logs will be accessed or which logs will be accessed the most. The company wants to keep costs as low as possible by using the appropriate S3 storage class.

Which S3 storage class should be implemented to meet these requirements?

. S3 Intelligent-Tiering provides automatic cost savings for data with unknown or variable access patterns without retrieval fees, performance impact, or operational overhead by automatically moving data to the most cost-effective access tier based on access frequency.

S3 Intelligent-Tiering monitors access patterns and moves objects that have not been accessed for 30 consecutive days to the Infrequent Access tier. After 90 days without access, S3 Intelligent-Tiering moves the data to the Archive Instant Access tier. For data that does not require immediate retrieval, you can set up S3 Intelligent-Tiering to monitor and automatically move objects that have not been accessed for 180 days or more to the Deep Archive Access tier to achieve up to 95% in storage cost savings.

A development team is deploying a new product on AWS and is using AWS Lambda as part of the deployment. The team allocates 512 MB of memory for one of the Lambda functions. With this memory allocation, the function is completed in 2 minutes. The function runs millions of times monthly, and the development team is concerned about cost. The team conducts tests to see how different Lambda memory allocations affect the cost of the function.

Which steps will reduce the Lambda costs for the product? (Select TWO.)

A

Increase the memory allocation for this Lambda function to 1,024 MB if this change causes the run time of each function to be less than 1 minute.

Correct. In this case, the team increases the memory allocation by 100%. The new run time is more than 100% faster (less than 1 minute), so a reduction in the overall costs will occur.

Duration is calculated from the time your code begins running until it returns or otherwise terminates, rounded up to the nearest 100 milliseconds. The price depends on the amount of memory that you allocate to your function. In the Lambda resource model, you choose the amount of memory that you want for your function, and you receive proportional CPU power and other resources. An increase in memory size initiates an equivalent increase in CPU that is available to your function.

For more information about Lambda pricing, see .

B

Increase the memory allocation for this Lambda function to 1,024 MB if this change causes the run time of each function to be less than 90 seconds.

Incorrect. In this case, the team increases the memory allocation by 100%. For the change to increase cost-effectiveness, the run time would need to be more than 100% faster (less than 1 minute instead of less than 90 seconds).

C

Reduce the memory allocation for this Lambda function to 256 MB if this change causes the run time of each function to be less than 4 minutes.

Correct. In this case, the team reduces the memory by 50%. The new run time is less than 200% slower (less than 4 minutes), so a reduction in the overall costs will occur.

Duration is calculated from the time your code begins running until it returns or otherwise terminates, rounded up to the nearest 100 milliseconds. The price depends on the amount of memory that you allocate to your function. In the Lambda resource model, you choose the amount of memory that you want for your function, and you receive proportional CPU power and other resources. An increase in memory size initiates an equivalent increase in CPU that is available to your function.

D

Increase the memory allocation for this Lambda function to 2,048 MB if this change causes the run time of each function to be less than 1 minute.

Incorrect. In this case, the team increases the memory allocation by 300%. For the change to increase cost-effectiveness, the run time would need to be more than 300% faster (less than 30 seconds instead of less than 1 minute).

E

Reduce the memory allocation for this Lambda function to 256 MB if this change causes the run time of each function to be less than 5 minutes.

Incorrect. In this case, the team reduces the memory allocation by 50%. For the change to increase cost-effectiveness, the run time would need to be less than 200% slower (less than 4 minutes instead of less than 5 minutes).

A company is using Amazon DynamoDB to stage its product catalog, which is 1 TB in size. A product entry consists of an average of 100 KB of data, and the average traffic is about 250 requests each second. A database administrator has provisioned 3,000 read capacity units (RCUs) of throughput.

However, some products are popular among users. Users are experiencing delays or timeouts because of throttling. The popularity is expected to continue to increase, but the number of products will stay constant.

What should a solutions architect do as a long-term solution to this problem?

Increase the provisioned throughput to 6,000 RCUs.

Incorrect. This solution would address the immediate situation, but it would not address the long-term needs that the scenario identifies. Eventually, the 6,000 RCUs would be consumed, and users would experience the same problem.

B

Use DynamoDB Accelerator (DAX) to maintain the frequently read items.

Correct. DAX provides increased throughput for read-heavy workloads. DAX also provides potential cost savings by reducing the need to overprovision RCUs. This feature is especially beneficial for applications that require repeated reads for popular products.

C

Augment DynamoDB by storing only the key product attributes, with the details stored in Amazon S3.

Incorrect. This solution would address the immediate situation, but it would not address the long-term needs that the scenario identifies. The storage of the details in Amazon S3 could increase query times because the company would need to query the S3 objects and the DynamoDB table to gather the complete information about a product.

D

Change the partition key to consist of a hash of the product key and product type instead of just the product key.

Incorrect. In this scenario, a change of the partition key to distribute data would not work. Some products are more popular than other products are, so the product key and product type are not randomized elements.

A company designs a mobile app for its customers to upload photos to a website. The app needs a secure login with multi-factor authentication (MFA). The company wants to limit the initial build time and the maintenance of the solution.

Which solution should a solutions architect recommend to meet these requirements?

A

Use Amazon Cognito Identity with SMS-based MFA.

Correct. Amazon Cognito user pools are user directories that provide sign-up and sign-in options for web users and mobile app users. You can add MFA to Amazon Cognito user pools for secondary validation.

B

Edit IAM policies to require MFA for all users.

Incorrect. The process of editing IAM policies for each user is time-consuming and ongoing work as new users start to use the mobile app. Moreover, the company wants to limit the initial build time. Creation and management of IAM users would be a high-maintenance solution.

C

Federate IAM against the corporate Active Directory that requires MFA.

Incorrect. When you design a public application that has a growing number of users, it is best practice to federate. However, Active Directory does not provide the sign-up feature of Amazon Cognito.

D

Use Amazon API Gateway and require server-side encryption (SSE) for photos.

Incorrect. Although API Gateway supports in-transit and at-rest SSE for secure upload of photos, this solution does not address the need for MFA. The question is about secured login and MFA.

A solutions architect needs to allow developers to have SSH connectivity to web servers. The requirements are as follows:

  • Limit access to users originating from the corporate network.

  • Web servers cannot have SSH access directly from the internet.

  • Web servers reside in a private subnet.

Which combination of steps must the architect complete to meet these requirements? (Select TWO.)

A

Create a bastion host that authenticates users against the corporate directory.

Incorrect. A bastion host meets the requirement to prevent direct SSH access from the internet. However, simple authentication of users against the corporate directory would not prevent those users from logging in to the bastion host from a location outside the corporate network.

B

Create a bastion host with security group rules that only allow traffic from the corporate network.

Correct. A bastion host meets the requirement to prevent direct SSH access from the internet. The addition of a security group rule that only allows SSH access from the corporate network meets the requirement to limit access accordingly.

C

Attach an IAM role to the bastion host with relevant permissions.

Incorrect. The IAM permissions that are assigned to a bastion host would not prevent users from logging in to the host from locations outside the corporate network. A role that is assigned to an instance would control what AWS API calls that instance can perform.

D

Configure the web servers' security group to allow SSH traffic from a bastion host.

Correct. The configuration of the web servers' security group to only allow SSH access from the bastion host will prevent access from other systems.

E

Deny all SSH traffic from the corporate network in the inbound network ACL.

Incorrect. This solution fails to solve the problem because the Deny statement would block external traffic only from the corporate network. This solution would not prevent users from outside the corporate network from attempting to access the web server directly. Even if the instance were in a private subnet, this solution would not block SSH access from any other instance. Therefore, sideways SSH traffic would be permitted.

A solutions architect is responsible for a new highly available three-tier architecture on AWS. An Application Load Balancer distributes traffic to two different Availability Zones with an auto scaling group that consists of Amazon EC2 instances and a Multi-AZ Amazon RDS DB instance. The solutions architect must recommend a multi-Region recovery plan with a recovery time objective (RTO) of 30 minutes. Because of budget constraints, the solutions architect cannot recommend a plan that replicates the entire architecture. The recovery plan should not use the secondary Region unless necessary.

Which disaster recovery strategy will meet these requirements?

A

Backup and restore

Incorrect. A backup and restore strategy can meet the cost objectives, but this strategy would not meet the RTO requirement.

B

Multi-site active/active

Incorrect. A multi-site active/active strategy would conflict with the budget constraints. Although a multi-site active/active strategy would provide a low RTO, this strategy is not appropriate for this scenario.

C

Pilot light

Correct. A pilot light strategy meets all the requirements. This strategy does not have a large increase in cost. This strategy offers an RTO within 10s of minutes.

D

Warm standby

Incorrect. A warm standby strategy might be an alternative to a pilot light strategy. However, the solutions architect in this scenario must not use the secondary Region unless necessary. This strategy would keep resources in the secondary Region that would not be used, which would increase costs unnecessarily. Therefore, it is not the correct answer.

An application provides a feature that allows users to securely download private and personal files. The web server is currently overwhelmed with serving files for download. A solutions architect must find a more effective solution to reduce the web server load and cost, and must allow users to download only their own files.

Which solution meets all requirements?

A

Store the files securely on Amazon S3 and have the application generate an Amazon S3 presigned URL for the user to download.

Correct. You can use presigned URLs to share access to your S3 buckets. When you create a presigned URL, you associate it with a specific action and an expiration date. Anyone who has access to the URL can perform the action embedded in the URL as if they were the original signing user.

B

Store the files in an encrypted Amazon Elastic Block Store (Amazon EBS) volume, and use a separate set of servers to serve the downloads.

Incorrect. Amazon EBS is a high-performance, block-storage service for use with Amazon EC2 for throughput and transaction-intensive workloads at any scale. The addition of a second set of servers would shift the work to another EC2 instance and would not reduce costs. Encryption of the EBS volume would not allow specific users to access only their specific files.

C

Have the application encrypt the files and store them in the local Amazon EC2 instance store prior to serving them up for download.

Incorrect. An instance store is not appropriate for this scenario. An instance store is ideal for temporary storage of information that changes frequently, such as buffers, caches, scratch data, and other temporary content. An instance store also is ideal for data that is replicated across a fleet of instances, such as a load-balanced pool of web servers.

D

Create an Amazon CloudFront distribution to distribute and cache the files.

Incorrect. CloudFront is a content delivery network service that securely delivers data, videos, applications, and APIs globally with low latency and high transfer speeds. The use of a CloudFront cache alone would not allow users to download only their own files. You can use CloudFront signed URLs to allow users to download only their own files, but signed URLs are not mentioned in this response.

A company is planning to use a third-party service for application analytics. A solutions architect sets up a VPC peering connection between the company's VPC on AWS and the third-party analytics provider's VPC on AWS.

Which additional step should the solutions architect take so that network traffic can flow between the two VPCs?

A

Resolve any overlapping CIDR ranges.

Incorrect. This step is not necessary because the solutions architect would not be able to create the VPC peering relationship if the CIDR ranges overlapped.

B

Configure the route tables for both VPCs.

Correct. A route table contains a set of rules, known as routes. These routes determine where to direct network traffic from your subnet or gateway. Routes give you control of whether network traffic is routed over the peering connection.

C

Verify that neither VPC has additional peering connections.

Incorrect. Multiple peering connections are allowed. The default quota for the number of peering connections to a VPC is 50, and the maximum quota is 125. You would not be able to establish the peering connection if you were already at the maximum number.

D

Verify that internet gateways are attached to each VPC.

Incorrect. An internet gateway is not required for VPC peering.

An application runs on Amazon EC2 instances in multiple Availability Zones behind an Application Load Balancer. The load balancer is in public subnets. The EC2 instances are in private subnets and must not be accessible from the internet. The EC2 instances must call external services on the internet. Each Availability Zone must be able to call the external services, regardless of the status of the other Availability Zones.

How should these requirements be met?

Question

An application runs on Amazon EC2 instances in multiple Availability Zones behind an Application Load Balancer. The load balancer is in public subnets. The EC2 instances are in private subnets and must not be accessible from the internet. The EC2 instances must call external services on the internet. Each Availability Zone must be able to call the external services, regardless of the status of the other Availability Zones.

How should these requirements be met?

Report Content ErrorsA

Create a NAT gateway attached to the VPC. Add a route to the gateway that connects to each private subnet route table.

Incorrect. Unlike internet gateways, which apply to the entire VPC, NAT gateways must reside within a subnet and within a single Availability Zone. The use of a single NAT gateway would result in a single point of failure.

B

Configure an internet gateway. Add a route to the gateway that connects to each private subnet route table.

Incorrect. This solution would turn the private subnets into public subnets and would make the EC2 instances accessible from the internet.

C

Create a NAT instance in the private subnet of each Availability Zone. Update the route tables for each private subnet to direct internet-bound traffic to the NAT instance.

Incorrect. To securely route traffic from private subnets to the internet, you must create NAT instances in public subnets.

D

Create a NAT gateway in each Availability Zone. Update the route tables for each private subnet to direct internet-bound traffic to the NAT gateway.

Correct. A NAT gateway is assigned to a public subnet and is associated with a single Availability Zone. This solution ensures that each Availability Zone is independent of the others for internet routing.

A user is designing a new service that receives location updates from 3,600 rental cars every hour. The cars upload their location to an Amazon S3 bucket. Each location must be checked for distance from the original rental location.

Which services will process the updates and automatically scale?

A

Amazon EC2 and Amazon Elastic Block Store (Amazon EBS)

Incorrect. This solution has no S3 component, so it does not meet the question's requirements.

B

Amazon Kinesis Data Firehose and Amazon S3

Incorrect. Kinesis Data Firehose could upload the data to an S3 bucket. However, the data already has been uploaded. The scenario requires a service that will perform an action (in this case, a calculation of the distance from the rental car to the original rental location).

C

Amazon Elastic Container Service (Amazon ECS) and Amazon RDS

Incorrect. This solution has no S3 component, so it does not meet the question's requirements.

D

Amazon S3 events and AWS Lambda

Correct. When an object is placed in an S3 bucket, that action needs to invoke an action that calculates the distance from the car to the original rental location. S3 Event Notifications calls the Lambda function, and Lambda runs the code to do the calculation.

A company is reviewing a recent migration of a three-tier application to a VPC. The security team discovers that the principle of least privilege is not being applied to Amazon EC2 security group ingress and egress rules between the application tiers.

What should a solutions architect do to correct this issue?

A

Create security group rules using the instance ID as the source or destination.

Incorrect. Security group rules are used to control inbound and outbound traffic that can reach instances associated with a security group. You cannot specify an instance ID as a source or destination in a security group.

B

Create security group rules using the security group ID as the source or destination.

Correct. Security group rules are used to control inbound and outbound traffic that can reach instances associated with a security group. You can specify the security group ID as the source or destination. This solution ensures that the security group rules are implemented correctly and that application tiers are able to communicate.

C

Create security group rules using the VPC CIDR blocks as the source or destination.

Incorrect. VPC CIDR blocks are groups of IP addresses that are assigned to your VPC. Although this solution is scoped to a private VPC address space, that space is shared with other applications. The other applications may not need access to the hosted application services. Therefore, this solution does not follow the principle of least privilege.

D

Create security group rules using the subnet CIDR blocks as the source or destination.

Incorrect. Subnet CIDR blocks are groups of IP addresses that are assigned to a specific subnet within your VPC. Although it is possible to create security group rules by using the subnet CIDR blocks as the source or destination, it would not follow the principle of least privilege. This is because other applications in the VPC subnet may not need access to the hosted application.

A company built a food ordering application that captures user data and stores it for future analysis. The application's static front-end is deployed on an Amazon EC2 instance. The front-end application sends the requests to the backend application running on a separate EC2 instance. The backend application then stores the data in Amazon RDS.

What should a solutions architect do to decouple the architecture and make it scalable?

Use Amazon S3 to serve the static front-end application, which sends requests to Amazon EC2 to run the backend application. The backend application will process and store the data in Amazon RDS.

Incorrect. A solution that uses one EC2 instance for the backend application is an example of a tightly coupled architecture. This solution cannot scale without additional architectural improvements such as an EC2 Auto Scaling group and/or an Elastic Load Balancer.

B

Use Amazon S3 to serve the static front-end application and write requests to an Amazon Simple Notification Service (Amazon SNS) topic. Subscribe the backend Amazon EC2 instance HTTP/S endpoint to the topic, and process and store the data in Amazon RDS.

Incorrect. Amazon SNS decouples the architecture and is scalable. However, messages that are published to the SNS topic are not stored and cannot be re-examined if processing fails. Additionally, a solution that uses one EC2 instance for the backend application is an example of a tightly coupled architecture. This type of solution cannot scale without additional architectural improvements such as an EC2 Auto Scaling group and/or an Elastic Load Balancer.

C

Use an EC2 instance to serve the static front-end application and write requests to an Amazon SQS queue. Place the backend instance in an Auto Scaling group, and scale based on the queue depth to process and store the data in Amazon RDS.

Incorrect. A solution that uses one EC2 instance for the frontend application is an example of a tightly coupled architecture. This solution cannot scale without additional architectural improvements such as an EC2 Auto Scaling group and/or an Elastic Load Balancer.

D

Use Amazon S3 to serve the static front-end application and send requests to Amazon API Gateway, which writes the requests to an Amazon SQS queue. Place the backend instances in an Auto Scaling group, and scale based on the queue length to process and store the data in Amazon RDS.

Correct. A solution that moves the static frontend application to Amazon S3 will decouple the frontend application from the backend application. This solution will allow for scalability and improve application availability by removing the EC2 instance as a single point of failure.

A serverless managed services like API Gateway and Amazon SQS would also eliminate single points of failure and further decouple the frontend requests from processing operations. API Gateway is an AWS service that creates, publishes, maintains, monitors, and secures REST, HTTP, and WebSocket APIs at any scale. Amazon SQS provides a highly available and scalable message queuing service.

The addition of a backend EC2 instance to an EC2 Auto Scaling group will improve backend scalability and remove another single point of failure.

A company is designing a website that will be hosted on Amazon S3.

How should users be prevented from linking directly to the assets in the S3 bucket?

Create a static website, then update the bucket policy to require users to access the resources with the static website URL.

Incorrect. You can use S3 bucket policies to grant permissions to S3 resources. However, the users still would be able to access the objects directly in the S3 bucket.

B

Create an Amazon CloudFront distribution with an origin access control (OAC) and update the bucket policy to grant permission to the OAC only.

Correct. To restrict access to the assets in S3 buckets, you can create an OAC and associate it with the website distribution. You would configure the S3 bucket permissions so that CloudFront can use the OAC to access the files in the S3 bucket and serve the files to the users. Afterward, the users can access the static website files only through CloudFront, not directly from the S3 bucket.

C

Create a static website, then configure an Amazon Route 53 record set with an alias pointing to the static website. Provide this URL to users.

Incorrect. Route 53 is a highly available and scalable DNS web service. This solution still would allow the users to access the objects directly in the S3 bucket.

D

Create an Amazon CloudFront distribution with an AWS WAF web ACL that permits access to the origin server through the distribution only.

Incorrect. AWS WAF will block or allow requests based on conditions that you specify, but the web ACL would not prevent the users from linking directly to the resources in the origin of the S3 bucket.

A company needs to implement a relational database with a multi-Region disaster recovery Recovery Point Objective (RPO) of 1 second and a Recovery Time Objective (RTO) of 1 minute.

Which AWS solution can achieve this?

A

Amazon Aurora Global Database

Correct. This solution provides your application with an effective RPO of 1 second and an RTO of less than 1 minute.

B

Amazon DynamoDB global tables

Incorrect. The company needs to implement a relational database, but DynamoDB is a nonrelational database.

C

Amazon RDS for MySQL with Multi-AZ turned on

Incorrect. Although this solution achieves high availability, Multi-AZ deployment does not meet the company's requirement for a multi-Region disaster recover solution.

D

Amazon RDS for MySQL with a cross-Region snapshot copy

Incorrect. The solution will not allow the company to meet the RPO and RTO requirements.

Cost Explorer is showing charges higher than expected for Amazon Elastic Block Store (Amazon EBS) volumes connected to application servers in a production account. A significant portion of the charges from Amazon EBS are from volumes that were created as Provisioned IOPS SSD (io2) volume types. Controlling costs is the highest priority for this application.

Which steps should the user take to analyze and reduce the EBS costs without incurring any application downtime? (Select TWO.)

A

Use the Amazon EC2 ModifyInstanceAttribute action to enable EBS optimization on the application server instances.

Incorrect. EBS optimization can increase EBS performance of the instance, but it will not contribute to cost analysis or cost reduction.

B

Use the Amazon CloudWatch GetMetricData action to evaluate the read/write operations and read/write bytes of each volume.

Correct. The CloudWatch GetMetricData action can show the IOPS and throughput of an io2 volume to help you determine if the io2 volume is a good candidate for modification to a lower-cost volume type.

C

Use the Amazon EC2 ModifyVolume action to reduce the size of the underutilized io2 volumes.

Incorrect. You cannot use the EC2 ModifyVolume action to reduce the size of a volume. ModifyVolume can only expand the size of a volume.

D

Use the Amazon EC2 ModifyVolume action to change the volume type of the underutilized io2 volumes to General Purpose SSD (gp3).

Correct. You can make a change with the EC2 ModifyVolume action without incurring any volume downtime. First, use CloudWatch to get metrics on the underutilized io2 volumes. Then use ModifyVolume to change from io2 to gp3 to reduce costs.

E

Use an Amazon S3 PutBucketPolicy action to migrate existing volume snapshots to Amazon S3 Glacier Flexible Retrieval.

Incorrect. EBS volume snapshots are managed by AWS and cannot be migrated to S3 Glacier (with either instant or flexible retrieval tier). Amazon Data Lifecycle Manager (Amazon DLM), not Amazon S3, handles the current EBS snapshot lifecycle.

A solutions architect is designing a new workload in which an AWS Lambda function will access an Amazon DynamoDB table.

What is the MOST secure means of granting the Lambda function access to the DynamoDB table?

Create an IAM role with the necessary permissions to access the DynamoDB table. Assign the role to the Lambda function.

Correct. An IAM role is an IAM entity that defines a set of permissions for making AWS service requests. IAM roles are not associated with a specific user or group. Instead, trusted entities such as IAM users, applications, or AWS services assume roles.

B

Create a DynamoDB user name and password and give them to the developer to use in the Lambda function.

Incorrect. DynamoDB has no concept of user names or passwords. You can grant access to the Lambda function by using an IAM role.

C

Create an IAM user, and create access and secret keys for the user. Give the user the necessary permissions to access the DynamoDB table. Have the developer use these keys to access the resources.

Incorrect. The use of static keys in code makes it possible to compromise access to the environment. This solution is not a secure way for the Lambda function to access DynamoDB. This solution also is not scalable because the keys must be shared with every user.

D

Create an IAM role allowing access from AWS Lambda. Assign the role to the DynamoDB table.

Incorrect. The IAM role should be assigned to the Lambda function. The Lambda function then would use that role to access DynamoDB. This response reverses that logic.

A company is planning to use Amazon S3 to store images uploaded by its users. The images must be encrypted at rest in Amazon S3. The company does not want to spend time managing and rotating the keys, but it does want to control who can access those keys.

What should a solutions architect use to accomplish this?

A

Server-Side Encryption with encryption keys stored in an S3 bucket

Incorrect. A solution that stores the encryption keys in an S3 bucket would require the customer to rotate and manage access to the keys.

B

Server-Side Encryption with Customer-Provided Keys (SSE-C)

Incorrect. SSE-C requires the customer to manage the encryption keys. In this scenario, the customer does not want to manage the keys. Amazon S3 does not store, rotate, or manage access to the encryption keys.

C

Server-Side Encryption with encryption keys stored in AWS Systems Manager Parameter Store

Incorrect. A solution that stores the encryption keys in AWS Systems Manager Parameter Store would require the customer to rotate the keys.

D

Server-Side Encryption with AWS KMS-Managed Keys (SSE-KMS)

Correct. SSE-KMS uses AWS Key Management Service (AWS KMS) to create, manage, rotate, and control access to encryption keys.

A company wants to build an immutable infrastructure for its software applications. The company wants to test the software applications before sending traffic to them. The company seeks an efficient solution that limits the effects of application bugs.

Which combination of steps should a solutions architect recommend? (Select TWO.)

A

Use AWS CloudFormation to update the production infrastructure and roll back the stack if the update fails.

Incorrect. Updates to and rollbacks of the production infrastructure would impact the applications and users. The company would need a separate environment to test the software applications before the company deploys updates to production.

B

Apply Amazon Route 53 weighted routing to test the staging environment and gradually increase the traffic as the tests pass.

Correct. Route 53 weighted routing gives you the ability to send a percentage of traffic to multiple resources. You can use a blue/green deployment strategy to deploy software applications predictably and to quickly roll back deployments if tests fail.

C

Apply Amazon Route 53 failover routing to test the staging environment and fail over to the production environment if the tests pass.

Incorrect. Route 53 failover routing provides disaster recovery by routing traffic to a healthy resource. If the resource becomes unhealthy, Route 53 will route traffic to another healthy resource.

D

Use AWS CloudFormation with a parameter set to the staging value in a separate environment other than the production environment.

Correct. The company could use a separate environment to test changes before the company deploys changes to production.

E

Use AWS CloudFormation to deploy the staging environment with a snapshot deletion policy and reuse the resources in the production environment if the tests pass.

Incorrect. A snapshot deletion policy does not support all resources and may not retain all required resources.

For more information about Lambda pricing, see .

For more information about Lambda pricing, see .

For more information about Lambda pricing, see .

For more information about Lambda pricing, see .

For more information about DynamoDB and provisioning capacity tables, see .

For more information about DAX, see .

For more information about DAX, see .

For more information about DynamoDB table exports, see .

For more information about DynamoDB table exports, see .

For more information about primary keys, see

For more information about partition keys, see .

For more information about Amazon Cognito, see .

For more information about MFA SMS text messages for users, see .

For more information about the creation of IAM policies, see .

For more information about how to confirm users for Amazon Cognito, see .

For more information about data encryption in API Gateway, see .

For more information about bastion hosts, see .

For more information about bastion hosts, see .

For more information about security group rules, see .

For more information about bastion hosts, see .

For more information about IAM permissions for Amazon EC2, see .

For more information about security group rules, see .

For more information about network ACL rules, see .

For more information about disaster recovery, see .

For more information about presigned URLs, see .

For more information about how to share an object with a presigned URL, see .

For more information about Amazon EBS, see .

For more information about instance stores, see .

For more information about CloudFront distributions, see .

For more information about VPC peering, see .

For more information about VPC peering, see .

For more information about route tables for VPC peering, see .

For more information about VPC peering quotas, see .

For more information about VPC peering, see .

For more information about VPC peering, see .

For more information about NAT gateways, see .

For more information about internet gateways, see .

For more information about NAT instances, see .

For more information about NAT gateways, see .

For more information about Kinesis Data Firehose, see

For more information about how to use Kinesis Data Firehose to upload data to an S3 bucket, see .

For more information about S3 Event Notifications, see .

For more information about how to create reliable event processing with S3 Event Notifications, see .

For more information about about security group rules, see .

For more information about security group rules, see .

For more information about controlling traffic to AWS resources, see .

For more information about VPC CIDR blocks, see .

For more information about subnet CIDR blocks, see .

For more information about Elastic Load Balancing and EC2 Auto Scaling, see .

For more information about Amazon SNS, see

For more information about Elastic Load Balancing and EC2 Auto Scaling, see .

For more information about Elastic Load Balancing and EC2 Auto Scaling, see .

For more information about how to host static websites by using Amazon S3, see .

For more information about API Gateway, see

For more information about Amazon SQS, see

For more information about EC2 Auto Scaling, see .

For more information about S3 bucket policies, see .

For more information about how to use an OAC to restrict access to S3 content, see .

For more information about Route 53, see .

For more information about AWS WAF, see .

For more information about Aurora global database, see .

For more information about DynamoDB global tables, see .

For more information about Multi-AZ deployment with Amazon RDS, see .

For more information about cross-Region snapshots, see .

For more information about EBS-optimized instances, see .

For more information about I/O characteristics and monitoring, see .

For more information about EBS Elastic Volumes, see .

For more information about how to request modifications to EBS volumes, see .

For more information about Amazon DLM, see .

For more information about IAM roles, see .

For more information about DynamoDB, see

For more information about IAM users, see .

For more information about IAM roles, see .

For more information about Amazon S3 security best practices, see .

For more information about AWS Systems Manager Parameter Store, see .

For more information about SSE-KMS, see .

For more information about AWS KMS, see .

For more information about how to use CloudFormation to create multiple environments and test changes before you release updates to a production environment, see .

For more information about weighted routing, see .

For more information about failover routing, see .

For more information about how to use CloudFormation to create multiple environments and test changes before you release updates to a production environment, see .

For more information about deletion policies and snapshot options, see .

AWS Lambda Pricing
AWS Lambda Pricing
AWS Lambda Pricing
AWS Lambda Pricing
AWS Lambda Pricing
Managing Settings on DynamoDB Provisioned Capacity Tables
Amazon DynamoDB Accelerator (DAX)
In-Memory Acceleration with Dynamo DB Accelerator (DAX)
Exporting DynamoDB table data to Amazon S3
New – Export Amazon DynamoDB Table Data to Your Data Lake in Amazon S3, No Code Writing Required
How do I choose the right primary key for a DynamoDB table?
Choosing the Right DynamoDB Partition Key
Common Amazon Cognito Scenarios
SMS Text Message MFA
Creating IAM Policies
Signing Up and Confirming User Accounts
Data encryption in Amazon API Gateway
Linux Bastion Hosts on AWS
Linux Bastion Hosts on AWS
Security group rules
Linux Bastion Hosts on the AWS Cloud: Quick Start Reference Deployment
IAM roles for Amazon EC2
Security group rules
Network ACL rules
Disaster Recovery Options in the Cloud
Using presigned URLs
Sharing an object with a presigned URL
Amazon Elastic Block Store (Amazon EBS)
Amazon EC2 instance store
Overview of distributions
VPC peering basics
VPC peering basics
Updating your Route tables for a VPC peering connection
Amazon VPC quotas
VPC peering basics
VPC peering basics
NAT gateway basics
Internet gateways
NAT instances
NAT gateway basics
What Is Amazon Kinesis Data Firehose?
Choose destination
Amazon S3 Event Notifications
Reliable event processing with Amazon S3 event notifications
Security Group Rules
Security Group Rules
Control Traffic to Your AWS Resources Using Security Groups
VPC CIDR Blocks
Subnet CIDR Blocks
Use Elastic Load Balancing to Distribute Traffic Across the Instances in Your Auto Scaling Group
What Is Amazon SNS?
Use Elastic Load Balancing to Distribute Traffic Across the Instances in Your Auto Scaling Group
Use Elastic Load Balancing to Distribute Traffic Across the Instances in Your Auto Scaling Group
Hosting a Static Website Using Amazon S3
What Is Amazon API Gateway?
What Is Amazon Simple Queue Service?
Get Started with Amazon EC2 Auto Scaling
Using Bucket Policies
Restricting Access to an Amazon S3 Origin
Amazon Route 53 FAQs
AWS WAF FAQs
Using Amazon Aurora global database
Amazon DynamoDB global tables
Amazon RDS Multi-AZ
Cross-Region Snapshot Copy for Amazon RDS
Amazon EBS–optimized instances
I/O characteristics and monitoring
Amazon EBS Elastic Volumes
Request modifications to your EBS volumes
Amazon Data Lifecycle Manager
IAM roles
What Is Amazon DynamoDB?
IAM users
IAM roles
Amazon S3 Preventative Security Best Practices
AWS Systems Manager Parameter Store
Using Server-Side Encryption with AWS KMS Keys (SSE-KMS)
AWS Key Management Service
Reuse Templates to Replicate Stacks in Multiple Environments
Weighted Routing
Failover Routing
Reuse Templates to Replicate Stacks in Multiple Environments
DeletionPolicy Options