- AWS Well-Architected Framework: Assists in designing and operating reliable, secure, efficient, and cost-effective systems on AWS.
- Cloud Computing: On-demand delivery of IT resources over the internet with pay-as-you-go pricing.
- AWS Role: Helps with undifferentiated heavy lifting, which includes repetitive and time-consuming IT tasks.
- Deployment Models:
- Cloud: Fully deployed in the cloud, no on-premises components.
- On-Premises: Private cloud deployment within a local data center.
- Hybrid: Connects cloud-based resources with on-premises infrastructure.
- Cost Efficiency: Aggregated usage across many customers leads to lower prices.
Key Concepts:
- Pay-as-you-go
- Cloud, Hybrid, On-Premises
- AWS Framework best practices
- Cost savings from cloud scale
Here's a table comparing the three AWS deployment models: Cloud, On-Premises, and Hybrid.
| Aspect | Cloud | On-Premises | Hybrid |
|---|---|---|---|
| Definition | Fully deployed in the cloud | Deployed within a local data center | Mix of cloud-based and on-premises resources |
| Infrastructure Location | Cloud provider (AWS) | Local data center | Combination of cloud and on-premises |
| Management | Managed by cloud provider (AWS) | Managed by in-house IT team | Managed by both cloud provider and in-house IT |
| Scalability | High, on-demand scalability | Limited by physical resources | Scalable, depending on cloud integration |
| Cost Structure | Pay-as-you-go pricing | Upfront capital investment required | Mix of capital investment and operational expenses |
| Maintenance | Handled by cloud provider (AWS) | Handled by in-house IT team | Split between cloud provider and in-house team |
| Security | Shared responsibility model | Full control by organization | Shared responsibility with flexibility |
| Deployment Speed | Fast, immediate resource availability | Slower, dependent on hardware setup | Moderate, dependent on integration complexity |
| Use Case | Startups, scaling applications, rapid deployment | Highly sensitive data, regulatory compliance | Gradual cloud adoption, legacy system integration |
This table highlights the differences and suitability of each deployment model in various scenarios.
When managing your own physical servers, you must first research and select the appropriate hardware, purchase and install it in a data center that you own or rent, and then set it up. In contrast, with AWS EC2, the data centers are already built and secured by AWS. You only pay for running instances, not for those that are stopped or terminated. EC2 instances share the underlying hardware with other instances, a concept known as multitenancy. The hypervisor, managed by AWS, coordinates this multitenancy, ensuring that each EC2 instance operates independently without awareness of others on the same host.
