Different Types of Pricing Plans

On-Demand: -book instances -up to 72% discounting -Billed per second -better for uninterruped workload

Reserved Instance: - reserve an instance attribute (type, region. tenanct, os) up 72% discount - reserved for 1 or 3 years - no yp front payment partial up front payment, full upfront payment - converitble, ri - able to sell or exchange in marketplace

Saving Plan: - up to 73% discount

Spot Instance - up to 90% discount - able to bid on an instance and use it - aws able to take it back at any point - for interuppable task such as analyzing data, image processing,

Dedicated Hosts, - able to use bring your own liencse for compliance - reserve physical server, able to chose where to host instance - control over os, - must reserve for 1 or 3 years - no upfront payment, partial payment or full payment - billed per instance use in secs

Dedicated Instance - reserve instances, not able to chose where to host instance - no control over core, os, and so on

EC2- scalable virtuals instances of machines that a can be used for variety of applications hoseted in the cloud. On-Demand - pay for instance by the hour or even seconds, Resevred Instance: - get discount rate if up to 1 year - 3years,<br /> Spot Instances - bid for unused EC2 at lower price, but connected can be lost at any point. .Configurations: Type, Size, Storage, ELB,Networking and auto scaling - Types General Purpose, Memory - OPtimized, Computer OPtimuized, Storage optimized,

6 pillars of Well Architect Framework

1. Operation Excellence
2. • perform operation as code (iaas)
3. • learn from operational failiure
4. • anticipate failure
5. Reliability
6. • automatically recover from failure
7. • scale horzontally
8. • stop guessing capacity
9. • manage change with automation
10. Security.
11. • principle of least privilage, IAM
12. • protect data in transit and at rest
13. • security at all layers
14. Performance Efficiency
15. • go global in minutes
16. • experiment frequently,
17. • user serverless architecture
18. Sustainability.
19. • adopt efficient tech
20. • used managed services
21. Cost Optimization
22. • pay for what you suse
23. • use cloudwatch to mesure efficiecy
24. • use tags to meaure roi
25. • use managed service to reduce cost

Saving Plans:

Basic Support Plan:

• use customer services, documentation, whitepaper.
• utilized Trusted Advisor 7 core check.

Developer Support Plan:

• unlimited support case/
• cloud support associate
• acesss to 24/7 1 AWS contact

Business Support Plan: 24/7

• Trusted Advisor ALL Check
• cloud support enginners
• for production level workload
• unlimited support case/
• acesss to unlimited AWS contact

• able to call with fix production failure: < 24hours

Enterprise on-Ramp- 24/7 Support Plan:

• for production level
• unlimited support case/
• acesss to 24/7 / unlimited AWS contact

• able to call with fix production failure: < 24hours

Enterprise 24/7 Support Plan:

• for production level
• unlimited support case/
• acesss to 24/7 AWS contact

• able to call with fix production failure: < 24hours

Orgazination

• global service to manage multiple - account
• mange billing for group of users in a single payment method
• help get volume discount
• • • pooling for Reserved EC2 for saving
• • • share RI and Saving Plans discount
• • • management accoiunt can turn it off
• api help automate the process
• ability to set policies that restircts access to all the user in the account

Strageties

• create different accounts for departments to to better resources isolations
• helps with regulations
• use tags for resources

SCP - service control policies

• able to whitelist or blacklist IAM actions
• help manage each account in Org
• able to restrict services for accounts
• must explicitly allow actions

Pricing Model :

• pay as you go, pay less as you use more, save when you reserve, pay less as AWS grows.

CloudFormation:

• Infastrucuture as Code,
• • control vm, os, and appplication
• • defines and manages AWS infastructure
• • provides templates
• • works with ECS, s3 , efs, rds,
• • manages entire stack of resoources
• • full control over

Elastic BeanStalk

• • Platform as service
• • simplified application deployment and scaling
• • limited control over
• • use cases: complex archi

CodeDeploy

• • deploy code

CodeCommit

• • comparable to github
• • store code and provides verision controls
• • allows collaboration

CodeBuild

• • able to build apps in the cloud
• • complies and run the application

CodePipeLine

• • commit -> deplot -> build in one step

artifact, start, cloud9 and sssm

Database

• 1. Relational Database
• helpful for storing massive amounts of data -able to store diiffernt types of data
• managed services, provided backup,high availibility, high storage,
• across muiltiple az
• able to recover fast --AWS reposibility - making sure its operational, security of storgae, infasturcture mangaement and safaty -Coustomer Resposibil;ity= mangament of data, encryption and access contraol and monitor performance Types" 1) RDS
• non flexible scheme
• SQL, POSTGRESS SQL,
• relational dataset 2) NoSQL
• flexible scheme
• 3)Data Warehousing 4)In memory caching Aurora:
• faster thatn RDS -SQL

RedShift- Data Warehouse ElasticCache : inmemory cacheing service

Scalibilty

• Vertical ability to increase or decrease the capacity of system to adapt to demand.
• Horizontal able to increase the number of instances to distriute the load acrross resources

High Availability

• ensure that the system is stay operation the longest times, and able to return failure in a quickest.

EC2

Load Balacing

• distribute traffic across mutiple targets to ensure that no single resources is overwheled

Elacstic Load Balancing and Auto Scaling Group

Scalibility

verticle vs Horizontal - able to increase or decrease performance load according to demand - increasing performance in a instance vs increasing number of instances

high avalibles

• ensure system is operational the longest times, reduce impact of failure
• able handle load across AZ

ECS Instance Storage: - way to mount volume storage to ec2 instance - provides persistance storagae even after termination - different types - temporary, and file system 30 GB for free tier (general pupose) Elastic Block Storage, - volume storage. dddd - discount for different types Elastic File System - network file sysem - can mount 100s of ec2 instance - has a high thought(read/ write) capabiliteis - - can be used for muiltiple OS - windows vs linux - others

IAM Guidelines & Best Practices 1) MFA 2) IMA Roles instead of USER 3) Follow the principle of least provilage 4) rotate user credentials 5) use managed policies

Shared Responsibility | AWS | Security of infastructure , Avalibity of IAM services, Offer Policies for common scenarios.

| Customer | manage and secure accss keys and user accounts, implement strong passwods, utlized mFA, IAM permision must be implemented correctly and follow the principle of least privilage.

Security Tools: Credential Report: Details about all IAM users in aws account such as passwords and access keys. Useful for auditing and review user credentails. Access Advisor: Policy Simulator:

IAM - Identity and Acess managment What is it ? It is a service used controling AWS account and providing credientials and permissions to users that have access to its resources. Consist of User, Roles, Group. User- account with access to aws resources have username, password and access keys Role - positioon with certain permissions Groip= group of users

Polices- set of permission that either allow or deny to access specific aws services (applies to user, role, group).

Policy Inheritance: Polices can be set for user, groups and roles, they can overlap with each other. (Inline policy) - for each users (managed )- resualble policies created and maintained by aws or customer. (group inherited )- applies to all users in that group.

policies structure JSON files, key elements included(Version stattement, action, reources , and effect.)