The AWS provider collects price metrics for Amazon Elastic Compute Cloud (EC2) from Amazon’s own APIs.
This section provides the minimum requirements that you should match before using the AWS telemetry provider.
A IAM user that has been granted the AWSPriceListServiceFullAccess
policy, that is the following permissions:
DescribeServices
GetAttributeValues
GetProducts
You may find more information on AWS cost permissions here.
Versions >= 2.0.0 are compatible with Akamas from version 1.9.0
EC2
In order to gather price information about a component you’re required to input an extra field in its definition:
region
, which tells the provider the AWS region of the modeled instance
Please note this field is mandatory and must be specified as follows:
Here is a complete list of AWS region names, together with their Akamas-compatible codes:
US East (Ohio)
us-east-2
US East (N. Virginia)
us-east-1
US West (N. California)
us-west-1
US West (Oregon)
us-west-2
Africa (Cape Town)
af-south-1
Asia Pacific (Hong Kong)
ap-east-1
Asia Pacific (Mumbai)
ap-south-1
Asia Pacific (Osaka-Local)
ap-northeast-3
Asia Pacific (Seoul)
ap-northeast-2
Asia Pacific (Singapore)
ap-southeast-1
Asia Pacific (Sydney)
ap-southeast-2
Asia Pacific (Tokyo)
ap-northeast-1
Canada (Central)
ca-central-1
China (Beijing)
cn-north-1
China (Ningxia)
cn-northwest-1
Europe (Frankfurt)
eu-central-1
Europe (Ireland)
eu-west-1
Europe (London)
eu-west-2
Europe (Milan)
eu-south-1
Europe (Paris)
eu-west-3
Europe (Stockholm)
eu-north-1
Middle East (Bahrain)
me-south-1
South America (São Paulo)
sa-east-1
AWS GovCloud (US-East)
us-gov-east-1
AWS GovCloud (US)
us-gov-west-1
To install the AWS provider, create a YAML file (called provider.yml
in this example) with the specification of the provider:
Then you can install the provider with the Akamas CLI:
The installed provider is shared with all users of your Akamas installation and can monitor many different systems, by configuring appropriate telemetry provider instances.
To create an instance of the CSV provider, build a YAML file (instance.yml
in this example) with the definition of the instance:
Then you can create the instance for the aws-system
using the Akamas CLI:
When you create an instance of the AWS provider, you should specify some configuration information to allow the provider to correctly extract and process metrics from your CSV files.
You can specify configuration information within the config
part of the YAML of the instance definition.
accessKeyId
- the access key id of your chosen IAM use
secretAccessKey
- the secret access key of your chosen IAM user
The following represents the complete configuration reference for the telemetry provider instance.
Then you can create the instance for the aws-system
using the Akamas CLI:
When you create an instance of the AWS provider, you should specify some configuration information to allow the provider to correctly extract and process metrics from your CSV files.
You can specify configuration information within the config
part of the YAML of the instance definition.
accessKeyId
- the access key id of your chosen IAM use
secretAccessKey
- the secret access key of your chosen IAM user
The following YAML file represents a template to define the telemetry provider instance.
The following table describes the configuration reference for the config
section
accessKeyId
String
The access key id of your chosen IAM user
Valid IAM credentials
Yes
secretAccessKey
String
The secret access key of your chosen IAM user
Valid IAM credentials
Yes