Resource Auto Mapping
The Easiest Way to Associate Resources with Services and Environments and Keep Drift Free
Resource auto mapping allows you to specify cloud tags and labels in your services and environments and have configure8 automatically map all your cloud resources to the specified environments and services. Each time configure8 does a new discovery job on your cloud accounts, the auto mapping will be re-run, enabling a drift-free mapping of your resources to your environments and services.
Auto Mapping is currently supported for AWS and Kubernetes resource types, with GCP and Azure coming soon.
To enable resource auto mapping:
- 1.Go into the Environment you wish to have auto mapped. Create a new piece of metadata of type Auto Map, and enter the key-value pair you use to identify a resource's environment in your company's tagging scheme. For example, if you have an
env: productiontag on all the resources in your production environment, you'd add the following metadata to your production environment:
- 2.Go into the Service you wish to have auto mapped. Create a new piece of metadata of type Auto Map, and enter the key-value pair you use to identify a resource's service in your company's tagging scheme. Configure8 will look at both Tags as well as Kubernetes Namespaces in the matching process. For example, if you have a
service: exampleservicetag on all the resources that correspond to ExampleService, you'd add the following metadata to the service detail page for ExampleService:
- 3.In the Service page, go to the Environments tab and click + Add Environment to add the environment you tagged in Step1 to the service:
Configure8 does the rest of the work, automatically mapping resources to the intersection of resources that match the Auto Map metadata you entered for your environments and resources. When you create new Auto Map metadata, updates will be applied soon (similar to discovery). Additionally, remapping will be run automatically after each discovery job and whenever you change a tag or label in your service or environment's Auto Map metadata.
configure8 supports mapping Kubernetes resources by specifying the name of namespace to map all resources in that namespace to a service. To map a namespace, create a new piece of Metadata of type Auto Map, set the key to
kubernetes.io/metadata.name, and set the value to the namespace (i.e. opencost). configure8 supports specifying multiple namespaces via adding many Auto Map metadata entries. For example, if you set 3 auto-mapping tags with the same name configure8 will assume that at least one of the namespaces should be present to Auto Map the pods/containers to the service.
Last modified 2mo ago