To comply with corporate standards AWS resources may need to be tagged with specific key/value pairs (e.g. cost-centre, business unit etc.)
It would be very useful to allow a dictionary of tags to be provided which would be included in the creation of the AWS artifacts.

Describe a specific use case for the enhancement or feature:
When deploying the Elastic Serverless forwarder into a shared AWS account:

• Cost centres are charged based on their actual consumption, and tags are used to identify this
• Ownership of resources is identified by tags

By adding the ability to tag the serverless function, Queues etc with the correct tags it would enable compliance with corporate standards.

This could be achieved by supplying an optional yaml file at deploy-time that is a dictionary of tag key/values. These would then be applied to all resources created.

sam deploy (if using the publish_lambda.sh script) supports a --tags flag to achieve this.
Alternatively, use something like `--config-file myconfig.yaml`` see Specify a configuration file to specify the tags, and the myconfig.yaml file location could be passed in as an argument to the publish_lambda.sh.