This project demonstrates how AWS Config can detect and enforce compliance for key cloud security best practices. Three security controls were tested in a live AWS environment, each starting in a NON_COMPLIANT state, then remediated to achieve COMPLIANT status.
The focus areas were:
By completing these exercises, the project validates AWS Config’s role in continuous compliance monitoring and automated policy enforcement, ensuring that cloud environments align with security best practices.
Situation:
In a cloud environment, unencrypted EBS volumes pose a data security risk because they allow unauthorized parties to potentially access sensitive information at rest. AWS Config provides the encrypted-volumes
rule to monitor compliance for encryption.
Task:
Deliberately create an unencrypted EBS volume to trigger a NON_COMPLIANT status in AWS Config, then remediate by enabling encryption, ensuring the environment meets security best practices.
Action:
Launched an EC2 instance named Test-Unencrypted-Volume with encryption disabled in the storage settings.
Opened AWS Config, searched for encrypted-volumes
, and verified the instance was flagged as NON_COMPLIANT.
📸 Screenshot 1 – NON_COMPLIANT status in AWS Config.
Stopped the EC2 instance, created an encrypted snapshot from the unencrypted volume, and generated a new encrypted volume.