Verify your email
Receive the instructions and prepare the permissions needed to run the scanner.
Run a read-only scanner with credentials you control. Receive a report with potential savings based on resource, utilization and billing data from your AWS environment.
The scanner opens on assess.cloudhero.io. A follow-up call is optional.
Review findings with the people who know the workload. Estimated opportunities need validation before changes are made.
An unattached EBS volume can continue to incur storage charges. Confirm the owner, retention requirement and recovery dependencies before taking action.
Receive the instructions and prepare the permissions needed to run the scanner.
Use your own AWS credentials and select the analysis period. Collected data is encrypted before upload.
Inspect the opportunities, share the report with your engineer and decide whether you want implementation help.
You’ll run the scanner in your own environment. Review the collection scope and permissions with your team before starting.
Read the scanner instructionsThe scanner collects selected resource metadata, utilization metrics and cost data. What a credential can access depends on its IAM policy; read-only policies vary in breadth.
Collected data is encrypted before upload. CloudHero decrypts it in the reporting environment to generate the assessment. Review processing and retention details before submitting data.
The assessment reviews resources and usage across services including EC2, RDS, S3, EBS and ElastiCache, plus Savings Plan coverage. Review the current scanner instructions for the supported collection scope and requirements.
The scan uses read APIs against the assessed AWS environment. You run it with credentials your team controls. Review the IAM policy because a broad managed read-only policy may grant more access than the scanner needs.
Choose the analysis period in the scan instructions. The current workflow supports the last complete month and a rolling 30-day period. Use the dates shown for your scan when interpreting findings.
They are potential opportunities. Validate workload needs, dependencies and pricing before implementing a recommendation. Actual savings depend on the changes made and subsequent usage.
The report workflow includes sharing functionality. Use that flow so your engineer receives the report through the supported access path.
No. A follow-up conversation is optional. If you want help, you can request support implementing the findings after reviewing the report.
Get a clearer view of potential savings and decide what deserves a closer look.