AWS Cloud Intro
AWS Cloud Intro
AWS Abbreviations and Meaning.
IAM means, Identity and Access Management
SCP means, Service Control Policy
MFA means, Multi-Factor Authentication
STS means, Security Token Service
SSO means, Single Sign-On
IAM IC means, IAM Identity Center (formerly AWS Single Sign-On)
KMS means, Key Management Service
HSM means, Hardware Security Module
ACM means, AWS Certificate Manager
CA means, Certificate Authority
WAF means, Web Application Firewall
DDoS means, Distributed Denial of Service
CSPM means, Cloud Security Posture Management
ARN means, Amazon Resource Name
ABAC means, Attribute-Based Access Control
RBAC means, Role-Based Access Control
SSM means, AWS Systems Manager
AWS Config means, AWS Config (configuration tracking and compliance service)
GuardDuty means, Amazon GuardDuty (threat detection service)
Macie means, Amazon Macie (sensitive-data discovery and protection service)
2. Compute and containers
EC2 means, Elastic Compute Cloud
ECS means, Elastic Container Service
EKS means, Elastic Kubernetes Service
ECR means, Elastic Container Registry
AMI means, Amazon Machine Image
ASG means, Auto Scaling Group
ELB means, Elastic Load Balancing
ALB means, Application Load Balancer
NLB means, Network Load Balancer
Fargate means, AWS Fargate (serverless compute for containers)
Lambda means, AWS Lambda (serverless compute service)
EB means, Elastic Beanstalk
EFA means, Elastic Fabric Adapter
EMR means, Elastic MapReduce
HPC means, High Performance Computing
3. Storage and backup
S3 means, Simple Storage Service
EBS means, Elastic Block Store
EFS means, Elastic File System
FSx means, Amazon FSx (managed file storage service family)
AWS Backup means, AWS Backup (centralized backup service)
DLM means, Data Lifecycle Manager
IOPS means, Input/Output Operations Per Second
RAID means, Redundant Array of Independent Disks
RPO means, Recovery Point Objective
RTO means, Recovery Time Objective
4. Networking and connectivity
VPC means, Virtual Private Cloud
CIDR means, Classless Inter-Domain Routing
IGW means, Internet Gateway
NAT means, Network Address Translation
NACL means, Network Access Control List
SG means, Security Group
ENI means, Elastic Network Interface
EIP means, Elastic IP Address
DNS means, Domain Name System
TLS means, Transport Layer Security
SSL means, Secure Sockets Layer
VPN means, Virtual Private Network
DX means, Direct Connect
TGW means, Transit Gateway
GWLB means, Gateway Load Balancer
CDN means, Content Delivery Network
POP means, Point of Presence
AZ means, Availability Zone
IP means, Internet Protocol
TCP means, Transmission Control Protocol
UDP means, User Datagram Protocol
HTTP means, Hypertext Transfer Protocol
HTTPS means, Hypertext Transfer Protocol Secure
BGP means, Border Gateway Protocol
MTU means, Maximum Transmission Unit
5. Databases and data services
RDS means, Relational Database Service
Aurora means, Amazon Aurora (managed relational database engine)
DDB means, DynamoDB (Amazon's managed NoSQL database)
DAX means, DynamoDB Accelerator
Redshift means, Amazon Redshift (cloud data warehouse)
DMS means, Database Migration Service
ETL means, Extract, Transform, Load
OLTP means, Online Transaction Processing
OLAP means, Online Analytical Processing
SQL means, Structured Query Language
NoSQL means, Not Only SQL
JDBC means, Java Database Connectivity
ODBC means, Open Database Connectivity
CDC means, Change Data Capture
DB means, Database
6. Monitoring, management and deployment
CW means, CloudWatch (Amazon CloudWatch)
CT means, CloudTrail (AWS CloudTrail)
IaC means, Infrastructure as Code
CFN means, CloudFormation (AWS CloudFormation)
CI/CD means, Continuous Integration / Continuous Delivery or Deployment
API means, Application Programming Interface
SDK means, Software Development Kit
CLI means, Command Line Interface
SLA means, Service-Level Agreement
SLO means, Service-Level Objective
SLI means, Service-Level Indicator
MTTR means, Mean Time to Repair or Recover
MTBF means, Mean Time Between Failures
KPI means, Key Performance Indicator
AWS Organizations means, AWS Organizations (multi-account management service)
7. Additional AWS and cloud terms worth learning
SES means, Simple Email Service
SNS means, Simple Notification Service
SQS means, Simple Queue Service
API GW means, API Gateway
CF means, CloudFront
ACU means, Aurora Capacity Unit
WCU means, Write Capacity Unit
RCU means, Read Capacity Unit
ECR Public means, Elastic Container Registry Public
EKS means, Elastic Kubernetes Service
ECS means, Elastic Container Service
AWS RAM means, Resource Access Manager
AWS DRS means, AWS Elastic Disaster Recovery
AWS Shield means, AWS Shield (DDoS protection service)
AWS Secrets Manager means, AWS Secrets Manager (secrets management service)
Important for certification exams: some entries above are general IT abbreviations rather than official AWS service abbreviations, and some are informal shorthand rather than universally standardized AWS acronyms. For example, CW, CT, CF, and DDB are convenient shorthand.
AWS Cloud Concepts
Concept of AWS Cloud.
What cloud computing is?
Cloud computing basically means that you have to meet certain criteria. Let's break it down and quickly walk through the five criteria.
The first criteria AWS have to meet for AWS to be considered cloud computing is that AWS has to offer an on-demand self-service, which is the ability to provision compute features or capabilities like servers, databases, network, storage, and more on demand; that's when the service is needed.
The second criteria is that cloud computing needs to have network connectivity to access and provision resources that are needed.Â
The third criteria is that cloud computing needs resource pooling. Well, what is resource pooling? AWS provides pooled resources to serve multiple different AWS customers. AWS has thousands of servers, databases, and more that we can on-demand provision and build in our own environment. And these pooled resources are available to me, to you, and to others as well.Â
The fourth criteria that cloud computing needs, which is elasticity, elasticity is the ability to scale with demand. As your demand increases, you can scale up your AWS resources, and then when that demand decreases, you can scale your resources back down.
And the fifth and last criteria that AWS must meet to be considered cloud computing is that the resource usage in the AWS accounts can be monitored and billed.Â
On-premises Services
It is the use of IT infrastructure owned and maintained locally. Example your Desktop, NFS, etc.
Cloud ServicesÂ
It is the use of computing resources provided remotely by a cloud provider. Example AWS EC2, Security group, etc.
IaaS
Infrastructure as a Service provides virtualized computing resources such as servers, storage, and networking while customers manage operating systems and applications. Example, AWS provides the infrastructure; you configure the OS, software, and application.Â
Paas
Platform as a Service provides a managed platform for building and deploying applications without managing most underlying infrastructure. Example, Developer uploads application code while AWS handles infrastructure provisioning, scaling, and deployment.Â
SaaS
Software as a Service provides complete software applications over the internet, usually accessed through a browser or application. Users access email software online without installing or managing mail servers.Â
Public Cloud
Computing infrastructure owned and operated by a cloud provider and offered to multiple customers over the internet. Example, different organizations use AWS infrastructure while their resources and data remain logically isolated.Â
Private Cloud
Cloud infrastructure dedicated exclusively to one organization, providing greater control over infrastructure, security, and configuration. Example, a bank operates a private cloud in its own data center exclusively for internal applications.Â
Hybrid Cloud
An environment combining private or on-premises infrastructure with public cloud resources, allowing workloads and data to operate across both.Example, a company stores sensitive data on-premises while running its customer-facing website on AWS.Â
High availability
High availability is a way to design your systems to have the ability to keep your systems up and running and providing service as often as possible. It is designed so that if a system component fails, then that failure can be replaced or fixed as quickly as possible. So it maximizes the system's online time. But high availability does not mean it stops failures. And high availability also does not mean that there will be no downtime or outages.Â
Fault tolerance.
It is similar to high availability, but fault tolerance is the actual ability of a system to keep operating in the event of a failure. For example, let's say that one or more of the system's components fails, but the system is able to continue on with those faults failing.Â
Disaster recoveryÂ
It is about restoring systems, data, and business operations after a disruptive event.
Agility
The ability to quickly provision, modify, experiment with, and deploy IT resources in response to changing requirements. The ease to do and undo.
Elasticity.
Scaling is the ability of a system to scale. So increasing or decreasing the load placed upon that system. There are two ways to scale, vertically and horizontally.
Vertical scaling means changing the capacity of an individual resource. For example, moving from a smaller EC2 instance type to a larger one.
Horizontal scaling  means adding or removing multiple resources/instances.
Now, Elasticity. What is it? Â generally means dynamically matching provisioned resources to changing demand, which can involve different scaling mechanismsÂ
Here are a few exam tips.
Vertical scaling is a larger size and horizontal scaling is adding more instances of the same size, and adding elasticity is using automation along with horizontal scaling to match our capacity to our demand.
Pay-as-you-go Consumption
A pricing model where customers pay for resources based on actual usage rather than purchasing infrastructure upfront. Example, a company pays for EC2 compute time used instead of purchasing physical servers before they are needed.
CapEx — Capital Expenditure
Money spent upfront purchasing long-term assets such as servers, buildings, networking equipment, and data-center infrastructure. Example, a company spends $100,000 purchasing physical servers and networking equipment for its data center.
OpEx — Operational Expenditure
Ongoing expenses incurred while operating a business or consuming services, typically paid periodically or according to usage. A company pays its monthly AWS bill based on the cloud resources it consumed.Â
The hierarchy you should mentally picture is:
AWS Global Infrastructure → Regions → Availability Zones → Data centers
with AWS's global network also supporting edge infrastructure.
Region is a geographic cloud provide area where you deploy workloads, VPC are at this level
Availability Zone is an isolated infrastructure within a Region, It is used to provide high availability/fault isolation. Subnets are created within the availability zones.
Data Centers are building within availability zones that help to provides cloud resources for a particular cloud service provider.
Edge location AWS edge infrastructure/points of presence used by services such as CloudFront to serve users closer to them.
For example, you might host an application in an AWS Region while using Amazon CloudFront's edge network to deliver cached content closer to usersÂ
This one is extremely important, not only for Cloud Practitioner, but throughout AWS security. See it as
AWS, security OF the cloud
and
Customer, security IN the cloud
AWS handles the underlying physical facilities, hardware, networking, and infrastructure supporting AWS services. The customer remains responsible for things such as their data, identities and access controls, configurations and services such as EC2, the guest operating system and applications.
Management Console is the browser GUI. It's excellent for visual learning.
AWS CLI lets you control AWS from a terminal. AWS describes CLI v2 as the current major version and notes that it gives direct access to AWS service APIs.
AWS SDKs let applications interact with AWS programmatically. AWS provides SDKs or toolkits for languages including Python, JavaScript, Java, Go, .NET, PHP, Ruby, Rust and others
On-Demand Pricing: Pay for compute capacity without long-term commitments. Use for unpredictable or short-term workloads by launching resources whenever required.
Savings Plans: Discounted compute pricing for committing to consistent usage for one or three years. Use for predictable workloads by purchasing a suitable hourly commitment.
Reserved Capacity Concepts: Reserve capacity or commit to longer-term usage for potential savings and availability benefits. Use for stable, predictable workloads requiring consistent resources.
Spot Pricing: Access unused AWS compute capacity at substantial discounts, but AWS can interrupt it. Use for fault-tolerant, flexible workloads such as batch processing.
AWS Free Tier: Provides limited free usage of eligible AWS services. Use for learning, testing, and small workloads while monitoring service-specific usage limits.
AWS Pricing Calculator: Estimates expected AWS costs before deployment. Use when planning architectures by selecting services, configurations, usage levels, and purchasing options.
AWS Budgets: Tracks costs or usage against configured thresholds and sends alerts. Use to control spending by creating budgets and setting notification thresholds.
AWS Cost Explorer: Visualizes and analyzes historical and forecasted AWS spending and usage. Use to identify cost trends, expensive services, and optimization opportunities.
Data-Transfer Considerations: AWS may charge for data moving between Regions, Availability Zones, services, or the internet. Consider transfer patterns when designing architectures to minimize costs.
AWS Support Plans: Provide different levels of technical guidance and support. Choose a plan based on workload criticality, required response times, and organizational support needs.
AWS Well-Architected Framework
What is the AWS Well Architected Framework?
The AWS Well-Architected Framework is AWS's best practices and the core strategies for architecting systems in the cloud. It helps you design, build and operate reliable, secure, efficient, and cost effective systems that will increase your likelihood of success. AWS Well-Architected Framework is based on six pillars:
Operational excellence
Security
Reliability
Performance efficiency
Cost optimization
Sustainability
The Well-Architected Framework also identifies a set of general design principles to facilitate good design in the cloud which are to:
Stop guessing your capacity
Use auto scaling to ensure your supply meets your demand
Test systems at production scale
Automate your architecture and this makes experimentation easier
Allow for evolutionary changes and use data to make the needed changes
And to improve through game days and run tests to see your systems at production level
Why are we discussing cloud computing and the Well-Architected Framework?" Well, the reason is that this gives you a solid basis for understanding AWS.
AWS also provides an AWS Well-Architected Tool along with the best practices to help us too and this tool will review your workloads and compare your workloads to the latest AWS best practices for architectural design.
Operational excellence which is the ability to support development and run workloads effectively, gain insight into their operations, and to continuously improve supporting processes and procedures to deliver business value.
The five design principles for operational excellence are:
Perform operations as code
Make frequent, small, reversible changes
Refine operations procedures frequently
Anticipate failure
Learn from all operational failures
Security encompasses the ability to protect data, systems and assets to take advantage of cloud technologies to improve your security.
There are seven design principles for security in the cloud:
Implement a strong identity foundation
Maintain traceability
Apply security at all layers
Automate security best practices
Protect data in transit and at rest
Keep people away from data
and Prepare for security events
Reliability encompasses the ability of a workload to perform its intended function correctly and consistently when it's expected. This includes the ability to operate and test the workload through its total lifecycle.
There are five design principles for reliability in the cloud:
Automatically recover from failure
Test recovery procedures
Scale horizontally to increase aggregate workload availability
Stop guessing capacity
and Manage change in automation
Performance efficiency includes the ability to use computing resources efficiently to meet system requirements and to maintain that efficiency as demand changes and technologies evolve.
There are five design principles for performance efficiency in the cloud:
Democratize advanced technologies
Go global in minutes
Use serverless architectures
Experiment more often
and Consider mechanical sympathy
Cost optimization: includes the ability to run systems to deliver business value at the lowest price point.
Sustainability: This focuses on environmental impacts, especially energy consumption and efficiency, because they are important levers for architects to inform direct action to reduce resource usage.
There are six design principles for sustainability in the cloud:
Understand your impact
Establish sustainability goals
Maximize utilization
Anticipate and adopt new, more efficient hardware and software offerings
Use managed services
and Reduce the downstream impact of your cloud workloads
Parallelization: Thinking parallel is similar to decoupling, but it is how to divide a job into its simplest form and then distribute that load to multiple components to handle the demand. And an example would be breaking down large datasets into smaller chunks that can be processed simultaneously and provide faster processing times.
AWS Migration considerations
For this task statement, ensure you know how to use AWS Cloud Adoption Framework and which resources can help support your migration journey to AWS.
The AWS CAF provides a comprehensive approach to cloud and it identifies specific organizational capabilities for successful cloud transformations. These capabilities provide best practice guidance and help you improve your cloud readiness. These capabilities are grouped into six perspectives:
Business
People
Governance
Platforms
Security
and Operations
Ensure you know how to use the AWS CAF to identify and prioritize transformation opportunities, evaluate and improve your cloud readiness, and iteratively evolve your transformation roadmap.
What are the benefits of using AWS CAF?
Reduce the business risk through improved reliability, increase performance, and enhance security.
You can increase your operational efficiency by reducing costs and increasing productivity.
You can grow by creating new products and services to reach new customers or new markets.
And you can improve performance by improving your sustainability and transparency.
What are some cloud adoption strategies?
Well, when organizations start migrating to AWS, they could be in different stages of adoption.
The project stage is when you are evaluating if migrating to AWS would meet your specific requirements and needs.
The foundation stage is when the migration to AWS begins. Maybe you move a few production applications to AWS or deploy an initial framework for the landing zone to a non-production environment.
The migration stage is where you define roles for cloud operations, establish a cloud center of excellence, also known as a CCOE, and prepare for long-term cloud operations instead of on-premises operations.
Last is the reinvention stage where all new projects start in AWS.
An assessment of where you and your organization sits is completed to understand which stage of adoption you are at before the migration begins.
For the exam, ensure you know how to identify appropriate migration strategies, such as database replication, using the AWS database migration service, or AWS Snowball.
The seven migration strategies.
Retire is for applications you want to decommission or retire.
Retain is for applications that you want to keep in the source environment or applications that are not ready to migrate.
Rehost, also known as lift and shift are for applications to migrate without making any changes to the application.
Relocate is for a large number of servers that are made up of one or more applications.
Repurchase is also known as drop and shop and is for applications with a different version or product and provides more value than the existing infrastructure.
Replatform is also known as lift, tinker, and shift and is for applications that need some level of optimization in order to operate efficiently or take advantage of AWS capabilities.
Refactor or re-architect is for applications that you want to migrate to AWS and take full advantage of the cloud-native features to improve agility, performance, and scalability.
What are some other AWS services and resources that are available to support your cloud migration journey?
Let's say that you're migrating your application that stores financial information to AWS. Your application requires low latency access and the data is constantly changing. Which AWS service could you use for this application migration?
Amazon Elastic File System
AWS Snowball Edge
Amazon Simple Storage Service
or Amazon Relational Database Service?
Well, Amazon S3 is always a good choice, but for the low latency requirement, Amazon S3 is not the best choice because Amazon S3 sits in the public zone and it is located outside of your Amazon VPC, so it could have more latency. AWS Snowball Edge is used for migration when you need to move large amounts of data into or out of AWS. My choices would be Amazon EFS and Amazon RDS. Amazon RDS is a managed database service that provides a scalable relational database with fast performance, high availability, and security. Amazon EFS provides scalable file storage with Amazon EC2 instances, and the storage capacity is elastic too.
What if you're migrating a NoSQL database and you must ensure the database is scalable, fast, and reliable? What AWS database service would you choose?
Amazon S3
Amazon RDS
Amazon Redshift
or Amazon DynamoDB?
Well, DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with scalability. NoSQL and non-relational are keywords for DynamoDB just as relational is a keyword for Amazon RDS. Amazon DynamoDB is a key-value and document database and stores JSON-type documents. AWS has another fully managed relational database service, Amazon Aurora.
What if you need to launch a Microsoft SQL Server database in AWS but you need to ensure the database is cost optimized and only a standard license for SQL server is required.
Do you launch an Amazon Aurora database that runs SQL server and buy a standard Microsoft SQL server license from the AWS License Manager service?
Or do you use an RDS instance that runs SQL server with a standard SQL license?
Or do you launch an Amazon EC2 instance and install SQL server and purchase a standard SQL license from Microsoft?
Or do you use a Windows server with SQL Server Standard AMI so you do not need to buy or manage your own license?
Well, AWS offers multiple Amazon Machine Images or AMIs for Amazon EC2 instances. If you launch an Amazon EC2 instance using a Windows AMI, you can choose one bundled with SQL Server Standard, and you do not need to purchase your own license from Microsoft. You could possibly choose the Amazon RDS database instance that runs SQL Server Standard and purchase the license, but the question asked for cost optimization and Amazon RDS costs more than Amazon EC2 because Amazon RDS is a managed service. Also, Amazon Aurora only supports MySQL and PostgresSQL, not SQL Server.
Another area of focus for this task statement is data backups because you need a plan in place to store your data once migrated. Ensure you understand the cost storage options for the AWS storage services. For example, Amazon S3 Glacier storage classes are designed to be the lowest-cost, Amazon S3 storage classes allowing you to archive large amounts of data at a very low cost. But you do have to consider the retrieval fees and the retrieval times.
Review these materials to learn more about the topics covered in this exam domain:
Cloud computing with AWS
What is cloud computing?
AWS Well-Architected Framework
High availability and scalability in AWS
Migration and transfer
Cloud economics in AWS resources