Engineering integration guide
AWS + UbiGrowth workflows
AWS is Amazon's cloud platform, where infrastructure, application services, and operational events are managed. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make AWS part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a engineering workflow around AWS with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Account, IAM Role, CloudWatch Metric, CloudWatch Alarm, Cost and Usage Report, Tag, and Resource. AWS resources are identified by ARN, which encodes account, region, and service. The same logical system spanning regions is many ARNs, and cost attribution depends entirely on tags that nothing enforces.
AWS is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Engineering systems produce more signal than any other part of the business and the least usable summary. AWS knows exactly what happened; turning that into something the rest of the company can act on is manual work that nobody owns.
The second problem is direction of risk. An integration that reads engineering activity is low-risk and useful. An integration that can act on infrastructure or production systems is a different category entirely, and the two are often discussed as if they were the same project.
You're likely here because
- Engineering activity is invisible outside the engineering team
- Incident context has to be reassembled manually every time
- Internal tool requests sit behind product work indefinitely
Record model
What a AWS integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are AWS's.
Identity and matching
AWS resources are identified by ARN, which encodes account, region, and service. The same logical system spanning regions is many ARNs, and cost attribution depends entirely on tags that nothing enforces.
Start here
Read Cost and Usage data for untagged resources and route the ownership question to the team the account belongs to.
What this will not do
It will not reduce your bill. It makes unattributed and idle spend visible; deciding what to switch off remains an engineering call.
The constraint to plan around
Cost and Usage Reports lag by up to a day and are revised, and API access is per-region, so a naive cross-region query is many calls with independent failure modes.
Build notes
What you actually have to reason about in AWS.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| ARN | encodes partition, service, region, and account — the only globally unambiguous identifier |
| tags | the entire basis of cost attribution, and nothing enforces their presence |
| lineItem/UnblendedCost | the Cost and Usage Report field that means what people assume "cost" means |
| resource state | per-service and inconsistent — there is no common lifecycle across services |
| region | API calls are regional, so a global view is N calls with N independent failure modes |
Authentication
IAM role assumed via STS with an external id for third-party access, never long-lived access keys. The policy should be least-privilege per service and per resource, and read-only for anything that only reports — which is most of it.
Events and delivery
EventBridge carries service events with at-least-once delivery. CloudTrail records API activity with a delay and is the audit surface rather than a real-time feed; treating it as live produces alerts minutes late.
Workflow
How the AWS workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Connect read-only first
AWS is connected with scoped, read-only credentials so context and reporting value can be proven without any action risk.
Step 02
Assemble the engineering picture
Delivery, incident, or operational activity is summarized in a form the rest of the business can act on rather than a raw feed.
Step 03
Build the internal surface
Launch produces the dashboard or internal tool that was never going to clear the product backlog, reviewed like any other internal service.
Step 04
Bound any action path
If the workflow needs to act, that path is specified separately with explicit scope, approval, and a record of what ran.
Design decisions
The engineering decisions this connection forces.
Each of these has to be settled before the AWS workflow is allowed to write anything.
Step 01
Separate read from act
Reading AWS for context and reporting is a different risk decision from letting a workflow act on it. Do not bundle them into one project.
Step 02
Make execution paths explicit
Any action that reaches a real environment should run through a reviewable execution path with a record of what ran, not an implicit side effect.
Implementation path
How to implement the AWS workflow.
- 01
Start read-only against AWS and produce something the team already wants: delivery visibility, incident context, or an operational summary.
- 02
Use scoped credentials rather than a shared token, and confirm what the scope can actually reach.
- 03
Build the internal surface in Launch, and review the result as you would any other contribution.
- 04
After untagged-spend routing works, add idle-resource detection scoped to the accounts that responded, so the second pass builds on the first rather than restarting.
Governance
Controls that matter.
Control 01
Credentials are scoped and workspace-approved; no shared secret belongs in a prompt or in generated code.
Control 02
Actions that reach production systems run through explicit, reviewable execution paths.
Control 03
Generated code and configuration are reviewed on the same terms as any other change.
Failure modes
How a AWS integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Cost attribution covers only part of the estate.
Cause
Resources are untagged and nothing enforces tagging.
Fix
Report untagged spend as its own line and route it to account owners, rather than excluding it.
Symptom 02
A cross-region query returns partial results without erroring.
Cause
Per-region calls failed independently and errors were swallowed.
Fix
Treat each region's call as a separate result with its own success state, and surface partial failure.
Symptom 03
Reported costs change after the fact.
Cause
Cost and Usage Report data is revised for up to a day or more.
Fix
Recompute rather than storing figures as final, and label the reporting window.
What changes at scale
API throttling is per service, per region, and per account, with exponential backoff expected. A full-estate sweep should be rate-aware per service rather than globally parallel.
Examples
What a working AWS workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Infrastructure operations
With AWS connected read-only, delivery and operational activity can appear alongside commercial context instead of living in a separate report.
Internal tool that was stuck in the backlog
A small tool reading AWS gets built in Launch and reviewed like any other internal service, without consuming sprint capacity.
Limitations and considerations
What to validate before you depend on this.
- Cost and Usage Reports lag by up to a day and are revised, and API access is per-region, so a naive cross-region query is many calls with independent failure modes.
- A write here provisions or destroys infrastructure and bills for it. Automation with mutating permissions is a production-change mechanism, and it should go through the same review as any deploy.
- When the workload genuinely needs cloud primitives. Assembling infrastructure directly is correct for differentiated systems; wrapping it in a workflow layer helps only for the undifferentiated glue around them.
- Write or action access to AWS is a materially different risk decision from read access and should be scoped, reviewed, and approved separately.
- Generated code and configuration still require review. Speed of production does not change ownership of what ships.
FAQ
AWS integration questions.
What records does a AWS integration actually work with?
The primary records are Account, IAM Role, CloudWatch Metric, CloudWatch Alarm, Cost and Usage Report, Tag, and Resource. AWS resources are identified by ARN, which encodes account, region, and service. The same logical system spanning regions is many ARNs, and cost attribution depends entirely on tags that nothing enforces.
What should the first AWS workflow be?
Read Cost and Usage data for untagged resources and route the ownership question to the team the account belongs to.
What will a AWS integration not do?
It will not reduce your bill. It makes unattributed and idle spend visible; deciding what to switch off remains an engineering call.
What is the main constraint to plan around?
Cost and Usage Reports lag by up to a day and are revised, and API access is per-region, so a naive cross-region query is many calls with independent failure modes.
What changes about a AWS integration at scale?
API throttling is per service, per region, and per account, with exponential backoff expected. A full-estate sweep should be rate-aware per service rather than globally parallel.
How does authentication work for AWS?
IAM role assumed via STS with an external id for third-party access, never long-lived access keys. The policy should be least-privilege per service and per resource, and read-only for anything that only reports — which is most of it.
Does AWS support webhooks, and can they be trusted?
EventBridge carries service events with at-least-once delivery. CloudTrail records API activity with a delay and is the audit surface rather than a real-time feed; treating it as live produces alerts minutes late.
What is the risk of writing to AWS?
A write here provisions or destroys infrastructure and bills for it. Automation with mutating permissions is a production-change mechanism, and it should go through the same review as any deploy.
When is connecting AWS the wrong call?
When the workload genuinely needs cloud primitives. Assembling infrastructure directly is correct for differentiated systems; wrapping it in a workflow layer helps only for the undifferentiated glue around them.
What should a AWS integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require AWS to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow act on AWS, not just read it?
Action paths are possible but should be treated as a separate, bounded project with scoped credentials, explicit approval, and a record of what ran.
How are credentials handled?
Through workspace-approved, scoped grants. A shared secret pasted into a prompt or embedded in generated code is not an acceptable pattern.
What is a safe first integration?
A read-only workflow that produces something the team already wants from AWS — delivery visibility or incident context — before any action path is considered.
How this access is governed
What ARIA is allowed to do in AWS, and who decides.
Connecting AWS is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.