AWS Core Service Categories
AWS services can be broken down into six major categories.
CATEGORY | DESCRIPTION |
Networking and Content Delivery | These are services for managing networking in the cloud. |
Databases | These are services that manage databases. |
Security, Identity and Compliance | These handle the security of your AWS infrastructure. |
Management and Governance | These ensure that AWS infrastructure is following best practices and meeting regulatory requirements |
Storage | These are services used to store data. |
Interacting With AWS
| WEB GUI | Command Line Interface | Programmatically |
| Console | AWS CLI | AWS SDK |
| Beginners | Engineer | Developers |
Benefits of the Cloud
● CAPEX can be converted to OPEX
a) Upfront expenditures are referred to as capital expenditures (CAPEX).
b) Day-to-day expenses are referred to as operational expenses (OPEX).
c) In the cloud, you trade upfront expenses for variable day-to-day expenses;
therefore, you pay for only what you use and give back what you don’t
need.
● In the cloud, you do not have to predict your future capacity.
● Allows faster deployment of applications
- Companies don’t have to order physical equipment and have it installed for
scaling up or upgrading according to requirements.
● High availability and low latency
- With AWS, you can access their entire global infrastructure and deploy
applications on any of their sites with just a click of a button.
Cloud Economics
AWS has five different pricing models, so you can select the one that saves you on cost for your specific workload.
| Free Tier | On-Demand | Reserved Volume | Discounts Price | Drops |
| Over 100 services available for free | Pay for what you use or the size you request | If you know you will be using a service for a long time, you can reserve it ahead of time (for 1-3 years) to save on cos | Like most things in the world, when you buy more, the price per unit goes down | AWS drops prices on services fairly regularly |
| 12 months of free service | There have been 129 price drops from 2006 to early 2023 | |||
| Some services are always free |
Cloud Native Design principles
| Design for Failure | - No single point of failure – no single component or location going down should take down your entire application - Add redundancy as much as possible |
| Decouple Components | - AWS offers Simple Queue Service (SQS) that allows you to move data between different components When components need to communicate with one another, they’ll send messages through the queue - Allows you to have individual components go down without loss of data |
| Implement Elasticity | - Make sure your application and all its components can scale up and down as load varies |
| Think Parallel | - Have multiple instances running concurrently to finish tasks as quickly as possible |
Thankyou for reading !!!!!