Automate

Each finding comes with a plan to fix it.

Sherpa is an AI platform for AWS. Automate turns each cost, security, inventory and performance finding into a step-by-step remediation plan, with AWS CLI commands and CloudFormation or Terraform where they apply. Sherpa never applies a fix; your team does.

After you sign up, a member of the Sherpa team contacts you within one business day to discuss your AWS environment and the right way to start.

Sherpa

Example findings from different areas

Idle load balancer prod-web-alb
Cost $412 a month Open
12 servers one size too big
Cost $5,310 a month Open
Security group open to SSH from anywhere
Security Critical Open
checkout-api errors at 4.2%
Performance Open

The problem

Why do AWS findings never get fixed?

Dashboards list problems, but someone still has to work out the remediation, write the commands and judge whether each change is safe for production workloads. That is where findings stall and the operational backlog grows.

4 areas

a fix plan for each finding — cost, security, inventory and performance.

Source: Sherpa product fact.

From finding to fix

How does a finding become a fix?

1
See it.

The affected resource, what it costs or puts at risk today in your environment, and the monthly saving wherever Sherpa can price it.
2
Decide.

Resolve the finding, or dismiss it with a documented reason, and reopen it later if priorities change. Each decision stays on the finding, with a history the whole team can see.
3
Apply it.

Work from the steps, the AWS CLI commands, and CloudFormation or Terraform when that's how the resource is managed. Your team applies each change through its own approval process, on its own schedule.

Example

What does a fix look like?

Example

Unattached storage volume vol-0a1b2c3d4e5f6a7b8 · unattached · $86 a month.

aws ec2 create-snapshot --volume-id vol-0a1b2c3d4e5f6a7b8 --description "Before delete"
aws ec2 delete-volume --volume-id vol-0a1b2c3d4e5f6a7b8

Sherpa never applies a fix; your team does.

Honest plans

Does every finding get the same kind of plan?

Clear-cut fixes get the full sequence of steps and the AWS CLI or infrastructure code to carry them out.
Resizes without enough usage data get a “collect more data first” plan until there is enough utilization history to judge the right size.
Slow or failing services get an investigation plan that starts with identifying the root cause.
Riskier deletions spell out what your team should verify before the resource is removed.

Start fixing this week.

After you sign up, a member of the Sherpa team contacts you within one business day to discuss your AWS environment and the right way to start.

Questions

Questions we get asked.

Does Sherpa change my AWS account automatically?

No. Sherpa never applies a fix. It writes the remediation plan; your team reviews it and decides what to apply, and when. Sherpa is an AI platform for AWS.

Can I get the AWS CLI or Terraform for a fix?

Yes. Plans include the steps and AWS CLI commands, plus CloudFormation, or Terraform when the resource is managed that way, so changes fit how your team already manages infrastructure.

How do we track what we fixed?

Each finding keeps its decision history: resolved, dismissed with a reason, or reopened. On the cost side, Sherpa also reports recommended against realised savings each month, so you can show what remediation returned.

Which areas does Automate cover?

Automate covers cost, security, inventory and performance findings, with a separate list for each operational area.

Can I export the plan?

Not yet. Your engineers copy the commands from the plan into their own change-management process.

Still have a question?