This script is used tag AWS volumes that were created by Kubernetes CSI external provisioner. In each execution, the script will tag all AWS volumes that are un-tagged using the tags of the attached instance. This is a workaround until it will be implemented by the external-provisioner natively. See related issue: https://github.com/kubernetes-c…

tag_untagged_csi_volumes.sh

#!/usr/bin/env bash

echo "$(date) - started to tag untagged CSI volumes"

untagged_csi_volumes=$(aws --profile my-aws-profile --output json ec2 describe-volumes \
  --query 'Volumes[?!not_null(Tags[?Key == `Environment`].Value)] | []')

for volume in $(echo "${untagged_csi_volumes}" | jq -r '.[] | @base64'); do

  volume_id=$(echo "$volume" | base64 --decode | jq -r '.VolumeId')
  instance_id=$(echo "$volume" | base64 --decode | jq -r '.Attachments[].InstanceId')

  instance_environment_tag=$(aws --profile my-aws-profile --output json ec2 describe-instances --instance-ids "$instance_id" \
    | jq -r '.Reservations[].Instances[].Tags[] | select(.Key=="Environment") | .Value')

  if [ -z "$instance_environment_tag" ]
  then
    echo "cannot tag volume $volume_id since $instance_id is not tagged with \"Environment\" tag"
  else
    echo "tagging $volume_id with Environment = $instance_environment_tag"
    aws --profile harmandev --output json ec2 create-tags --resources "$volume_id" \
      --tags Key=Environment,Value="$instance_environment_tag"
  fi

done

echo "$(date) - finished to tag untagged CSI volumes"