Our AWS module was built with the intention of only collecting data for a single profile. As usage as grown and our users needs have changed, we need a way to collect metrics from multiple AWS profiles. When launching cloudcost-exporter we need a way to
specify single profile to collect metrics for OR
specify single role ARN to use to for authentication
specify list of role ARN's to use for authentication
This is a fundamental change to how we generate clients with AWS and will require a proof of concept to help inform how to migrate the codebase over. Ideally we should support the current authentication model while allowing us to opt into adopting using role ARN's for authentication. Once both are available, an end user should be able to chose one or the other, but not both authentication mechanisms.
Overview
Our AWS module was built with the intention of only collecting data for a single profile. As usage as grown and our users needs have changed, we need a way to collect metrics from multiple AWS profiles. When launching
cloudcost-exporter
we need a way toThis is a fundamental change to how we generate clients with AWS and will require a proof of concept to help inform how to migrate the codebase over. Ideally we should support the current authentication model while allowing us to opt into adopting using role ARN's for authentication. Once both are available, an end user should be able to chose one or the other, but not both authentication mechanisms.
Documentation
Yace:
AWS SDK:
Goals
scripts
directory to demonstrate collecting ec2 instances from many profiles