AWS

Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.

Billing

• Track daily AWS spend broken down by service (SageMaker, Bedrock, Lambda, EC2, and more)
• Monitor total AI infrastructure cost across your AWS account over time
• Scope costs to a specific initiative using AWS Cost Allocation Tags
• Use monthly spend observations in value formulas to calculate net ROI

1. In AWS: Create a user in IAM with the ReadOnlyAccess policy for Cost Explorer (ce:GetCostAndUsage)
2. In AWS: Generate an access key ID and secret access key for that user
3. Back in Roiva: Paste them here in the format access_key_id:secret_access_key
4. Back in Roiva: To scope costs to a specific initiative, activate a Cost Allocation Tag in the AWS Billing console, add that tag to your resources, then enter the tag key and value in the Filters field on the initiative link

• Tag AWS resources with a consistent key (e.g. Initiative=InvoiceAI), activate it as a Cost Allocation Tag in AWS Billing, then add tag_key and tag_value as Filters on your initiative link — costs will be scoped to that tag automatically
• Without tag filters, the sync pulls account-wide cost totals — still useful as a baseline or for tracking overall AI spend
• SageMaker, Bedrock, and Lambda are the most common services for AI initiative cost tracking