INFRASTRUCTURE EVIDENCE
AWS Add cloud infrastructure context to evidence.
EC2, ECS, EKS and RDS metadata explain where production runs in AWS. AutoObserve maps cloud resource relationships onto telemetry identity — without replacing CloudWatch or your existing observability stack.
- Evidence
- Resource metadata · Cloud context
- Source
- AWS API / CloudTrail
- Enables
- Infrastructure relationships
- Status
- Preview
AWS
Resource metadata
AutoObserve
Infrastructure context
Investigation
WHY THIS INTEGRATION MATTERS
Cloud context grounds telemetry in infrastructure reality.
When checkout-api degrades, knowing the RDS instance, security group and region matters. AWS infrastructure evidence adds that layer to connected investigations.
Resource relationships
Map services to EC2, ECS tasks, EKS pods and backing stores.
Cloud identity
Enrich telemetry with account, region and resource identifiers.
Infrastructure change
Correlate CloudTrail events with production behaviour.
Blast-radius reasoning
Understand shared infrastructure dependencies during incidents.
EVIDENCE RECEIVED
Resource metadata and cloud context from AWS
AWS API metadata becomes infrastructure evidence — linked to service identity and runtime topology.
- Resource metadata
- Cloud context
Discover
Inventory EC2, ECS, EKS and RDS resources in scope.
Map
Link cloud resources to Kubernetes and telemetry identity.
Correlate
Join infrastructure context with metrics, logs and traces.
Investigate
Start incidents with cloud relationships already resolved.
HOW AUTOOBSERVE USES THIS EVIDENCE
Evidence becomes infrastructure investigation context.
AWS is not replaced — it is connected. AutoObserve treats cloud metadata as one evidence class alongside telemetry and runtime.
Provides
- Resource metadata
- Cloud context
AutoObserve creates
- Infrastructure relationships
- Cloud identity
- Resource topology
- Change correlation
AWS is where it runs. AutoObserve is how you connect it.
CONNECT AWS INFRASTRUCTURE
Ingest cloud metadata alongside telemetry.
API polling, CloudTrail and Kubernetes paths feed the same evidence model — scoped to the accounts and regions you operate.
Poll EC2, ECS, EKS and RDS metadata for connected context.
AWS APIs
AutoObserve connector
AutoObserve
QUICK START
Connect AWS infrastructure evidence
Configure account access and resource scope, then verify checkout-api resolves to cloud context.
Configure AWS access
Grant read-only IAM permissions for target accounts and regions.
Link EKS runtime
Connect EKS clusters for combined cloud and Kubernetes context.
Verify infrastructure context
Confirm checkout-api resolves to region and backing resources.
WHAT SUCCESS LOOKS LIKE
Cloud context resolved. Infrastructure ready.
Success means services map to AWS resources — not merely that API credentials are configured.
Resources discovered
checkout-api backing stores appear in infrastructure context.
Region resolved
Production region appears on service identity.
Cross-signal correlation
Cloud metadata aligns with telemetry during incidents.
REAL INCIDENT
Same checkout spike — service identity in focus.
The canonical checkout-api degradation with identity context highlighted — the resource linkage that grounds telemetry in AWS infrastructure.
Metric
14:31:00
Checkout latency +184%
Walk through the evidence chain · 1/6
Evidence step 1 of 6
TROUBLESHOOTING
Common AWS integration failures
Problem
No resources discovered
Likely cause
IAM policy missing ec2:Describe*, eks:Describe* or scoped regions.
Resolution
Verify read-only IAM policy covers target accounts, regions and services.
Verify
checkout-api backing resources appear within one sync window.
Problem
Resources present but not linked to services
Likely cause
Tag or naming convention does not match telemetry identity.
Resolution
Align resource tags with service.name and Kubernetes labels.
Verify
RDS instance links to checkout-api in investigation context.
Problem
Stale infrastructure metadata
Likely cause
API rate limits or overly broad inventory scope.
Resolution
Narrow scope to production accounts and reduce poll frequency.
Verify
Resource state matches production during incident window.
PRODUCTION INTELLIGENCE
How AWS contributes to production understanding
Cloud infrastructure evidence enables resource relationship reasoning inside connected production intelligence.
| Evidence | Enables |
|---|---|
| Resource metadata | Infrastructure relationships |
| Cloud context | Region and account scope |
| CloudTrail events | Infrastructure change correlation |
DESIGN PARTNERS
Validate this evidence source with your production stack.
Design partners connect real evidence sources and validate investigation workflows before GA — with direct engineering access.