Table of Contents

1. Challenge

   Create an EFS File System Named devshare with Encryption Enabled

   • Create an EFS file system with the name of devshare.
   • Leave default creation settings with encryption enabled.
2. Challenge

   Create a Mount Target for EFS Using EFSMountSecurityGroup

   Select your new EFS file system and navigate to the Network tab. Add the EFSMountSecurityGroup security group to each mount target to ensure your EC2 instance will have access to this volume.

3. Challenge

   Apply a File System Policy to the EFS Volume to Enforce In-Transit Encryption for All Clients

   Create a file system policy for the EFS volume to enforce in-transit encryption for all of your clients.

4. Challenge

   Mount the EFS Volume to the EC2 Instance and Create a File on the Elastic File System

   Connect using cloud_user credentials.

   Use the following command to mount your volume with encryption in flight, replacing fs-00000000 with your file system ID:

   • Example structure: sudo mount -t efs -o tls file-system-id efs-mount-point/

   • Example command mounting to local EFS directory you have created: sudo mount -t efs -o tls fs-000000000 /efs

   Verify the volume is ready for use by creating a file: sudo touch /efs/llama.txt

   Note: Keep in mind that without adding this to the /etc/fstab, the mount will not persist through a reboot. In this case, you are only preparing the volume for use by your team, so that's okay in this lab.