Following on from my last post on implementing AWS Backup, we have started to run it in production with a few instances after successful tests of backup and restores in a development environment. Some of the volumes that were being backed up did not have any name tags which made identifying the snapshots created by AWS backup time consuming (volumes should be tagged when the provisioning tasks are run but there were quite a few old instances in the account that had volumes attached with no name tag). I created a lambda using PowerShell Core (Windows PowerShell is not supported) to tag all the volumes in the account that are attached to an EC2 instance to make sure all volumes have a name. The lambda can be run periodically just in case an instance is created and the volume does not have a name tag applied.
This lambda was created on a Mac using PowerShell core and the AWSCore and AWSLambda modules:
PSVersion 6.1.1 PSEdition Core OS Darwin 18.5.0 Platform Unix AWSLambdaPSCore 184.108.40.206 AWSPowerShell.NetCore 3.3.485.0
Below is the complete code for the lambda,
The #requires statement is needed for any modules that will be used by the lambda. For this one it is just the AWS module, but you can include any modules that are PowerShell core compatible.
The list of volumes is saved into the variable VolumeList and a new list object is created to hold the volumes that don’t have a name tag. The VolumeList variable is iterated over to check for a name tag, if it doesn’t exist, the instance id and volume id is stored in the NoNameTagVolumeList variable.
The NoNameTagVolumeList is iterated over and name tags are created from either the name tag of the instance the volume the snapshot was created from is attached to, or if the instance does not have a name tag, then the instance ID is used and this is applied to the volume.
The lambda needs to the ability to be able to tag the volumes.
A policy is created with the permission to apply tags.
A trust policy is also required.
With the two policies, a role can be created for the lambda to use that will allow it to tag EC2 resources and also log what actions have taken place. The code below uses Get-Content and the two json files above to create the policy and role in the AWS account (the account running the commands but have permission to create IAM policies and roles).
Creating the lamdba
New-AWSPowerShellLambda -ScriptName 'TagVolumesWithNoName' -Template Basic
After running the command the directory structure looks like:
The lambda code should be placed in the TagVolumesWithNoName/TagVolumesWithNoName.ps1 script. This file has comments and template code when created and the readme.txt has more information and can be deleted once it has been read.
Copy the code from above TagVolumesWithNoName.ps1 into the newly created file TagVolumesWithNoName.ps1 and save it. The lambda is now ready to be published.
Publish the lambda
Publish-AWSPowerShellLambda -ScriptPath .\TagVolumesWithNoName\TagVolumesWithNoName.ps1 -Name TagVolumesWithNoName -Region 'eu-west-1'
As the lambda is published, you will be prompted to select an iam role. Enter the number of the IAM role that was created above.
I did run into errors publishing a couple of times and had to restart my PowerShell Core session and try again.
Once the lambda has been published, you will see it in the AWS console.
Test the lambda
Select the lambda that has been published from the lambda section in the AWS console.
To test the lambda from the console:
- Select configure test events from the drop down
- On the configure test event screen, give the event a name such as test and click save.
- You will be taken back to the main lambda view, click the test button to run the lambda.
- The lambda will run and tag any volumes that don’t have a name tag.
The below example volume did not have a name tag and the instance name tag value was ‘Matt-test-ubuntu-splunk’
After the lambda ran, the volume was tagged with the instance name.
Volumes should be tagged appropriately on provisioning of an EC2 instance, however sometimes they are not and currently to name the root ebs volume using cloudformation, requires a hacky workaround. Using PowerShell core running on a lambda is a good option to make sure volumes are tagged with a name tag which can be created as from the attached instance. This makes managing volumes easier and also helps identify snapshot that are created from these volumes. This lambda could be run on a schedule or started on another event from cloudwatch event.