Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

1.3.2. Shared Responsibility: Customer's Role (Developer Focus)

First Principle: The customer is responsible for "security in the cloud," securing their data, applications, and configurations within AWS services, like application code, data encryption, and IAM permissions.

In the AWS Shared Responsibility Model, the customer's responsibility is for "security in the cloud." For developers, this means securing everything they put into and configure within the AWS Cloud, specifically concerning their applications.

Key Customer Responsibilities ("Security in the Cloud") for Developers:
  • Application Code Security: Writing secure code, performing code reviews, using secure libraries.
  • Data Security: Encrypting application data (at rest and in transit), data classification.
  • IAM Permissions: Configuring IAM roles and policies for applications using the Principle of Least Privilege.
  • Network Configuration (for application traffic): Configuring Security Groups and Network ACLs for application endpoints.
  • Operating System (if using EC2): Guest OS patches, security updates, firewall configurations for your application's EC2 instances.
  • Configuration of Managed Services: Properly configuring security settings for services like Amazon S3 bucket policies (e.g., preventing public access unless intended), DynamoDB table access.
  • Secure defaults are not a finished configuration: New S3 buckets are private by default; since April 2023 new buckets also have S3 Block Public Access on and ACLs disabled, and since January 2023 new objects are encrypted with SSE-S3 by default. Deciding who may actually access the bucket (IAM policies, bucket policies, CORS) is still your job.

Scenario: When developing an application running on an EC2 instance, you are responsible for patching the guest OS, configuring its security groups to allow only necessary traffic, and writing secure application code.

⚠️ Exam Trap: Even with managed services like Lambda, developers are still responsible for function code security, environment variable encryption, and VPC configuration. "Serverless" doesn't mean "security-free."

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned