I'm Kadota (id:lufiabb), Application engineer of the Mackerel team.
- AWS integration
About the feature that assigns roles by tags
Up to now, for AWS integration it has been possible to set the Mackerel services and roles linked by default at the AWS service unit, such as EC2 or RDS, but only one setting could be made per AWS service. So to assign a different Mackerel services and roles in the AWS service required the services and roles to be set manually or the creation of an AWS integration setting for each Mackerel services and roles. This made it difficult to manage auto scaling hosts.
This feature makes it possible to automatically set Mackerel services and roles by AWS tag information when a host is registered by AWS integration by setting tags in the formats shown below to the AWS resource in advance. If the specified Mackerel services and roles do not exist, the AWS integration will create them.
The tag format is described as follows:
- Key :
- Value :
<Service>:<Role> [/ <Service>:<Role> ...]
For example, to assign a “api” role in a "webapp" service, set this as
webapp:api. Furthermore, multiple roles can be assigned using “/” to delimit the services and roles, such as
webapp:api / webapp:db to set the two roles of “api” and “db”.
For EC2, the tag can be set from the following screen.
The initial release will support the following AWS services.
There is no way to change the tag key referenced by this feature from mackerel-integration or to disable the feature, so if the mackerel-integration tag is already set, there is the possibility it will be unintentionally used.
The tag editor of the AWS resource groups can be used to check the tags set in the current resource, so please check the current settings before the release planned for late February.