Loading the page…
Shaping the future of software engineering
Resolve AI connects to your AWS environment through a secure, temporary-access IAM role to ingest CloudWatch metrics and logs, and query AWS APIs for infrastructure state during investigations, correlating infrastructure signals with service behavior and deployment history to surface root cause without manual dashboard work.
Production failures in AWS rarely have a single origin. Resolve AI ingests CloudWatch metrics and logs, and queries AWS APIs for infrastructure state, correlating them against infrastructure state, code changes, and signals from your other integrated tools to trace failures back to their source.
When an incident fires, Resolve AI queries the relevant CloudWatch log groups to surface error patterns, trace request failures through Lambda functions and ECS tasks, and identify where in the execution chain things broke down.
CPU utilization, memory pressure, request counts, error rates: Resolve AI pulls CloudWatch metrics across your configured regions and connects them to incident timelines, so spikes are understood in context rather than in isolation.
During an investigation, Resolve AI queries AWS APIs and CloudWatch to reconstruct what your infrastructure was doing (Auto Scaling actions, RDS state, EC2/ELB status) at the time of the incident.
Resolve AI connects with the minimum permissions needed to investigate, reason, and act across your AWS environment.
Everything Resolve AI ingests or queries from your AWS environment, with step-by-step docs in the setup guide.
Queries configured log groups to surface error patterns and trace failures through Lambda functions, ECS tasks, and other AWS services.
Pulls metrics across regions to correlate performance signals as CPU, memory, request rates, error counts with incident timelines.
Queries AWS APIs and CloudWatch to reconstruct infrastructure state (Auto Scaling actions, RDS state, EC2/ELB status) during incidents.
A single IAM role configuration covers all AWS regions you specify, enabling cross-region investigations without additional setup.
AWS connects through a secure IAM role using temporary credential assumption. No long-lived access keys are required for the standard setup.
Log in to Resolve AI, open the AWS Integration, click Add Connection, and then click View Instructions to get the custom account details you'll need for the next step.
In your AWS account, create a new IAM role named resolve-access-role. Set the trust relationship using the target account from the Resolve AI UI and an External ID of your choosing. Attach the following managed policies: SecurityAudit, CloudWatchReadOnlyAccess, AmazonRDSReadOnlyAccess, and IAMReadOnlyAccess. Copy the Role ARN from the IAM console.
Name the connection (e.g. Production AWS), specify your target region or regions, and paste the Role ARN and External ID. Optionally, define a CloudWatch Log Group Allow List to restrict which log groups Resolve AI can query.
The cloud infrastructure standard for companies at every scale, AWS powers compute, storage, databases, networking, and hundreds of other services across 39 regions worldwide.
Resolve AI requires an IAM role with four read-only managed policies: SecurityAudit, CloudWatchReadOnlyAccess, AmazonRDSReadOnlyAccess, and IAMReadOnlyAccess. No write permissions are required. A sample trust policy is available in the setup guide.
No. Resolve AI uses temporary credential assumption via an IAM role rather than storing long-lived access keys. Credentials are scoped, temporary, and never retained by Resolve AI's cloud.
Yes. The CloudWatch Log Group Allow List in the integration configuration lets you define exactly which log groups Resolve AI is permitted to query. Any log group outside that list is inaccessible.
A single IAM role configuration can cover multiple regions you specify during setup. For multiple AWS accounts, each account requires its own IAM role and integration connection in Resolve AI.
Yes. For environments not reachable from Resolve AI's cloud, the Resolve Satellite proxies CloudWatch queries from within your infrastructure. The Satellite must be installed before configuring the AWS integration via this method.
Yes. Athena SQL queries on S3 data can be enabled as an optional extension of the AWS integration. See the AWS Athena setup guide for configuration steps.
AWS investigations go further when Resolve AI connects your full stack.
A single IAM role configuration covers all the AWS regions you choose to expose. Resolve AI reasons across regions in a single investigation, so incidents that span availability zones or regional boundaries don't require manual cross-account correlation.
For AWS environments behind a private VPC that Resolve AI cannot reach directly, the Resolve Satellite proxies CloudWatch queries securely from within your infrastructure, with no inbound network exposure required.
AWS data is one layer of the picture. Resolve AI connects CloudWatch signals to Kubernetes cluster state, application traces, code changes, and alerts from your observability tools, so investigations span the full environment rather than stopping at the cloud boundary.
Resolve AI uses temporary, assumed-role credentials scoped to read-only access. No long-lived credentials are stored by Resolve AI's cloud, and raw AWS data is never retained outside of active investigations.
For environments not reachable from Resolve AI's cloud, the Resolve Satellite proxies CloudWatch queries securely from within your infrastructure.
A CloudWatch Log Group Allow List lets you restrict exactly which log groups Resolve AI can query; anything outside the list is inaccessible.
Resolve AI begins correlating AWS signals immediately. For environments behind a private VPC, follow the Satellite setup before this step.
Create a Kubernetes secret with your AWS credentials, add the CloudWatch integration to your resolve-values.yaml, and run helm upgrade to apply. Full instructions are in the setup guide.
