Category: Data, Terraform, encryption, automation

Before diving deeper into how this script is structured, we need to understand the fundamental steps in this process: Taking a snapshot Creating an encrypted volume from the snapshot Removing the unencrypted volumes So even though it might feel complex at some point, you have to remember these fundamental steps!

The goal for this article is to protect the data in our volumes by encrypting its operations with the application.

In order to run this, we have to the go the specific directory in the git repo (aws-devops/ebs-encrypt) and do: The idea behind leveraging an infrastructure as code scripting language such as Terraform is the flexibility and easiness of handling these resources in the cloud.

Else, this volume is not taken into consideration — line 108: we have to tag the volumes that have already gone through the function.

Related Articles