AWS::EC2::Instance should apply tags to created volumes

[hoegertn]

2. Scope of request

The documentation states that "The specified tags are applied to all instances or volumes that are created during launch" but this is not the case.

3. Expected behavior

Specifying tags on AWS::EC2::Instance should tag the instance and all created volumes.

5. Helpful Links to speed up research and evaluation

Docs: https://docs.aws.amazon.com/en_pv/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html#cfn-ec2-instance-tags

Support: https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-instance-tag-root-volume/

6. Category (required) - Will help with tagging and be easier to find by other users to +1

1. Compute (EC2, ECS, EKS, Lambda...)

[snemir]

+1

[stufox]

We'd also expect the root volume created in the template to have the tags applied in the RunInstances call (i.e. tag on create) rather than a separate CreateTags call after that so we can enforce volume tagging in SCP

[rmbhatt]

+1. not having a Name tag and other cost allocation tags on root volume created by CloudFormation service requires manual steps outside of stack actions.