AWS Resource Tagging as an Optional Parameter to Detonate

[nix-xin]

Problem Summary
Resource tagging in AWS is metadata applied to resources at the time of creation. Tags allow for easier management, searching, and filtering of AWS resources. It is possible for organizations to enforce tagging on specific resources and if the appropriate tags are not provided, the creation of a resource can be denied. When running a Stratus AWS technique, the warmup phase may be denied because of improper tags, or none provided. With no useful information as to why the warmup failed.

Possible Solution
Allow Stratus to accept an optional flag for custom tags passed in the warmup phase as Terraform is spinning up the required infrastructure for a technique. The tags can be colon separated key:value pairs separated by commas.

Here's an example: stratus detonate aws.persistence.lambda-backdoor-function --tags "owner:[email protected], reason:stratus testing"

[nix-xin]

So far I've tested this concept after a failed warmup in a resource tagging enforced environment. I modified the Terraform main.tf instruction to include the valid tags. Removed the terraform state file and re-applied the terraform instructions by manually executing the terraform command.

terraform apply