Who owns what you're running on AWS?
Sherpa lists the resources across your AWS accounts, with who owns each one, what changed since yesterday and which versions are past end of support.
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.
What are we running that nobody owns?
214 resources have no owner, across 5 accounts.
| Type | Count | Accounts | Next step |
|---|---|---|---|
| Servers (EC2) | 38 | 4 | add an owner tag |
| Databases (RDS) | 6 | 2 | add an owner tag |
| Storage buckets (S3) | 170 | 5 | add an owner tag |
What changed since yesterday's scan?
3 resources changed, 1 without a stack update.
| Resource | What changed |
|---|---|
| Security group sg-0a1b2c3d | inbound rule added |
| RDS database orders-db | backup window changed (without a stack update) |
| Lambda function send-receipt | memory raised |
Which runtimes are out of support?
13 resources on versions past end of support.
| Resource | Version | Count | Next step |
|---|---|---|---|
| Lambda functions | Python 3.8 | 11 | upgrade |
| RDS databases | MySQL 5.7 | 2 | upgrade |
From a long list to clear answers.
What can we find out about our resources?
-
No owner
- Resources missing an owner tag.
- Grouped by type, account and region.
-
What changed
- Configuration changes since the last scan.
- Changes made without a stack update stand out.
-
Out of support
- Lambda runtimes and database versions past end of support.
- Plan upgrades before they become urgent.
-
Outside CloudFormation
- Servers, functions and databases not managed by CloudFormation.
- The workloads outside your infrastructure as code.
Who owns it, what does it cost, and is it exposed?
An untagged resource is a cost and a security question too. Ask once, get all three.
Are the basics turned on in every account?
Sherpa's foundation score shows, account by account, whether the basics are in place.
Why don't teams know what they run?
200+
AWS services, and every team creates its own resources.
Source: AWS.
Resources outlive the projects and people who created them. Without an owner, nobody turns them off.
Find out what you're running 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 we get asked.
What is a cloud asset inventory?
A record of the resources in your cloud accounts: what they are, where they run, who owns them and what changed. Sherpa keeps this inventory for your AWS accounts.
How do I find untagged AWS resources?
Ask Sherpa, "What are we running that nobody owns?" It lists resources missing an owner tag, by type, account and region.
Does Sherpa change our tags or resources?
Sherpa never applies a fix; your team does. Sherpa shows what's missing, such as an owner tag, and writes the fix. Your team decides what to change.
How often is the inventory updated?
Every day.
Still have a question?
Contact us