Well architect framework key to Security
Hello Everyone,
I hope everyone doing well and keeping good progress in Cloud upskilling.
Let's explore very important concept of AWS Shared responsibility model in this article.
Imagine you're renting an apartment in a high-security building. The building owner (AWS) is responsible for the overall structure, common areas, and basic security. You, as the tenant (AWS customer), are responsible for what happens inside your apartment and how you use it.
AWS Responsibilities: Security of the Cloud
AWS takes care of the foundation and infrastructure, much like how a building owner maintains the structure and common areas.

Physical Security
AWS secures its data centers, just as the building owner ensures the main entrance is locked and monitored. You don't need to worry about someone breaking into the AWS server rooms, just as you don't concern yourself with intruders entering the building's maintenance areas.
Network Infrastructure
AWS manages the underlying network, similar to how the building owner maintains the electrical wiring and plumbing. You simply "plug in" to use these services without worrying about their maintenance.
Virtualization Layer
AWS handles the hypervisor, which is like the building's elevator system. You use it to access your "floor" (your cloud resources), but you don't maintain the elevator itself.
Customer Responsibilities: Security in the Cloud
As an AWS customer, you're responsible for what you bring into and do within the cloud, much like how you manage your apartment's contents and activities.
Data Security
You must secure your data, just as you'd lock up valuables in your apartment. This includes encrypting sensitive information and managing access to it.
Access Management
Managing who can access your AWS resources is your responsibility, similar to deciding who gets keys to your apartment. This involves setting up IAM users, roles, and permissions.
Operating System Management
If you're using Amazon EC2, you need to manage the operating system, much like how you'd maintain the appliances you bring into your apartment. This includes patching, updates, and security configurations.
Application Security
Securing applications you deploy on AWS is your job, just as you're responsible for the security of the devices you use in your apartment.
Real-World Examples
Let's look at some practical examples to illustrate this model:
Example 1: Amazon S3
- AWS Responsibility:
- Ensuring the S3 service is available and functioning
- Protecting the underlying infrastructure that stores your data
- Your Responsibility:
- Configuring bucket policies and access controls
- Encrypting sensitive data before uploading
- Monitoring access logs for suspicious activity
Example 2: Amazon EC2
1.AWS Responsibility:
- Maintaining the physical servers and network infrastructure
- Ensuring the availability of the EC2 service
2.Your Responsibility:
- Patching and updating the operating system of your EC2 instances
- Configuring security groups and network ACLs
- Implementing application-level security measures
Shared Controls
Some aspects of security are shared between AWS and the customer. For example:
Patch Management: AWS patches the infrastructure, but you patch your guest OS and applications.
Configuration Management: AWS configures its infrastructure, but you configure your own guest OS, databases, and applications.
Conclusion
Understanding the AWS Shared Responsibility Model is crucial for maintaining a secure and compliant cloud environment.
By clearly delineating responsibilities, AWS and its customers can work together to create a robust security posture. Remember, AWS provides the secure foundation, but it's up to you to build securely upon it. Just as you'd take precautions to secure your apartment within a well-protected building, you must actively manage the security of your AWS resources and data.