AWS Billing
Set up the AWS Billing connector in AccessLayer.
AWS Billing gives you access to cost and billing metadata from AWS Cost Explorer, including monitors, subscriptions, and cost category definitions.
In AccessLayer, the AWS Billing connector lets you query cloud spend metadata for reporting, chargeback analysis, and cost governance workflows.
Before you start
You will need AWS credentials that can call Cost Explorer APIs.
Before you begin, make sure you have:
- An AWS access key ID
- An AWS secret access key
- An AWS region for the Cost Explorer endpoint
- An optional AWS session token if you use temporary credentials
For additional details, see the AWS Cost Explorer documentation.
Cost Explorer access required
The IAM principal you use must have permission to read Cost Explorer billing metadata. If your organization uses temporary credentials, include the session token as well.
Generating your credentials
Create or retrieve an access key pair
In AWS IAM, create or retrieve an access key ID and secret access key for a user or role that can access Cost Explorer APIs.
Confirm the correct region
Use the AWS region where you want AccessLayer to resolve the Cost Explorer
endpoint. If you are unsure, start with us-east-1, which is AWS Cost
Explorer's primary endpoint region.
Copy a session token if required
If your AWS setup issues temporary credentials through STS or a federated login flow, copy the matching session token and add it to the connector config.
Troubleshooting
Confirm that the access key or assumed role has permission to call AWS Cost Explorer APIs for the billing metadata you want to query.
Double-check that the access key ID, secret access key, region, and session token all belong to the same credential set and have not expired.
Check whether the access key was rotated, disabled, or replaced, or whether the temporary session expired. Update the connector configuration with the new credentials if anything changed.