Connect AWS to ShipVitals
Daily cost per account and service
BetaGuided setup · about 3 minutes
Beta: this connector is new in the beta, and we're still checking it against more accounts.
What it reads
- ce:GetCostAndUsage
- Reads daily cost per service and linked account
- ce:GetDimensionValues
- Lists the linked accounts billed, with their names
Read-only: ShipVitals can't change anything at AWS.
What ShipVitals keeps: The role's ARN and your workspace's External ID. No AWS key: ShipVitals assumes the role. AWS charges your account $0.01 for each Cost Explorer request: about 2 a day, and about 13 for the first sync.
How to connect
- Enter your 12-digit AWS account ID.
- Read the template, then open it in CloudFormation and create the stack.
- Come back: ShipVitals waits for the role, then checks it.
About 3 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs.
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
AWS reports a day in full after 1 day; ShipVitals waits for it.
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- AWS no longer accepts what ShipVitals signs in with. Create a new key, or connect again, and replace it in the connection.
- A permission is missing
- The ShipVitals role can't read Cost Explorer. Update the stack with the current template.
- Access removed
- ShipVitals can't assume the ShipVitals role any more: the stack may have been deleted. Create it again from the AWS wizard.
- Rate-limited
- AWS is limiting Cost Explorer requests. ShipVitals tries again later.
- Quota reached
- The account used up a AWS quota. The sync resumes when the quota resets.
- Not found
- Cost Explorer has no data yet. Open Cost Explorer once in the Billing console; data appears within 24 hours.
- AWS is unavailable
- AWS is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach AWS
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that AWS is reachable.
- An answer ShipVitals didn't expect
- AWS answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- A field in the connection doesn't work with AWS. Check it against How to connect, and test again.