Skip to content

Security: codewithmuh/certified-aws-developer-associate-notes

Security

SECURITY.md

Security Policy

Reporting Security Issues

We take cloud security and the accuracy of architectural patterns in these certification notes seriously. If you identify a security risk, vulnerable reference template, or credential leak, please report it responsibly.

DO NOT create a public issue for security disclosures.

Please send security reports to:


AWS Cloud Security Best Practices (DVA-C02 Domain Alignment)

When building on Amazon Web Services following these patterns:

  1. IAM (Identity & Access Management):
    • Enforce MFA across all IAM users and root account.
    • Use IAM Roles instead of long-lived access keys (AKIA...) wherever possible (EC2 Instance Profiles, Lambda Execution Roles, ECS Task Roles).
    • Follow the principle of least privilege with specific resource ARNs and condition blocks.
  2. Encryption at Rest & in Transit:
    • Enable AWS KMS customer-managed keys (CMK) for EBS volumes, S3 buckets, RDS databases, and DynamoDB tables.
    • Enforce TLS 1.2+ for all API Gateway endpoints and Application Load Balancer listeners.
  3. Secrets Management:
    • Store database passwords and API tokens in AWS Secrets Manager or AWS Systems Manager Parameter Store (SecureString).
    • Never embed credentials in CloudFormation templates, SAM manifests, or application code.
  4. VPC Network Isolation:
    • Place database (RDS, DynamoDB DAX) and internal microservices in private subnets without public IPv4 addresses.
    • Restrict Security Group inbound rules to known CIDRs or security group references.

There aren't any published security advisories