AWS::GameLift::Fleet - Tags

This issue requests the addition of support in CloudFormation templates for tags when using AWS::GameLift::Fleet and AWS::GameLift::Alias among others in the gamefleet service where the Tags are already supported by the API and CLI.

Problems caused by this omission include:

If IAM policy conditions are being used based upon tags, there it no way to get the tags into place when creating the resources. This means that access to gamelift:CreateFleet and gamelift:CreateAlias of all resources is required by the user / role as well as UpdateFleetCapacity to deploy fleets and update or create aliases. Additionally, if a stack is to be rolled back, the Delete* permissions are also required for any and all these resources as tags will not have been applied.

If multiple games are being run in a single account, for example, this also limits the use of tags for filtered billing, though post-deployment scripts can assign tags after the fact, it is another step needing implemented for something already supported elsewhere.

By not being able to use cloudformation, the auto-update of aliases and removal of replaced fleets would need to be implemented separately.

Start by reviewing the AWS::GameLift::Fleet and AWS::GameLift::Alias resource coverage and comparing their CloudFormation behavior with the GameLift API and CLI, where Tags are already supported. Done means CloudFormation templates can provide tags for these resources during creation and replacement, including the related gamefleet resources mentioned in the issue.

Written by the indexing model from the issue text.