Connect an AWS account
The fastest path is the Refine connector stack — one CloudFormation stack, launched from inside Refine, that creates the FOCUS 1.2 billing export, its S3 bucket, and a read-only IAM role in your account. If you already export FOCUS data, skip to the existing-export path below.
Quick setup (recommended)
- In Refine, open
Settings → AWS Accounts → Add Account(the welcome screen’s Connect your AWS account button lands here too) and choose Quick setup. - Click Launch the connector stack. The AWS console opens with the template pre-loaded — it runs in
us-east-1(required for Cost & Usage Data Exports). Tick the IAM acknowledgement and create the stack (~2 minutes). - Open the stack’s Outputs tab and paste into the form:
BucketName→ Source Bucket,RoleArn→ Role ARN. That is everything — the External ID was already carried into the stack by the launch link. No access keys are created and none leave your account: the stack creates a read-only IAM role that only Refine’s own application roles, in Refine’s AWS account, can assume, and only when they present your External ID. - Save. AWS delivers the first export within about a day; Refine picks it up automatically and notifies you.
Already exporting FOCUS?
Choose I have a FOCUS export in the same form and point Refine at that bucket, with a read-only IAM role Refine can assume — it needs read on the export’s prefix in that bucket, the AWS-managed SecurityAudit policy (the security views), ce:ListCostAllocationTags for which tag keys are activated for cost allocation, savingsplans:DescribeSavingsPlans for when each Savings Plan ends, and two CloudWatch metric reads (cloudwatch:GetMetricData and cloudwatch:ListMetrics) to confirm that a database or cache the bill looks idle for really is, and to read Bedrock model health — invocations, errors, throttles and latency. Numbers only; nothing there can read a prompt or a response. The easiest way to make that role is the same connector stack with ExistingBucketName set to your bucket and S3PathPrefix set to the prefix your export delivers under (the export’s details in the Billing console, Data Exports): it then creates only the role, able to read the objects under that prefix and no other object in the bucket, and touches nothing you already have. Re-connecting an account that used the older access-key setup? Use this path. Running the full stack again fails with “Cannot create duplicate export name”, because the export it made the first time is still there. Building the role by hand instead? Its name must start with Refine, and its trust policy must name arn:aws:iam::941275879372:root under the External ID shown on the form. To narrow it the way the stack does, also require aws:PrincipalArn to match arn:aws:iam::941275879372:role/amplify-d2gdmwnr3mkfp5-* or arn:aws:iam::941275879372:role/service-role/refine-focus-reports-replication-role-*.
What access does Refine get?
A read-only IAM role: AWS’s read-only SecurityAudit policy, read access to the export only, and four named reads — ce:ListCostAllocationTags, savingsplans:DescribeSavingsPlans, cloudwatch:GetMetricData and cloudwatch:ListMetrics. No write, payment or admin permissions. Refine never asks for, receives or stores an AWS access key. It assumes the role for an hour at a time, and only by presenting the External ID your stack was created with, so the role cannot be used by anyone else who learns its ARN. To revoke access at any time, delete the role in your AWS console — Refine immediately loses the ability to read, with nothing left over to expire.