Your AWS bill —
is it really optimized?

We take your invoices and Cost Explorer and, within 2 weeks, deliver a report of your likely savings. The assessment is a fixed price. Implementation is quoted separately, or you can choose a savings-share arrangement.

Pain points

Does your AWS usage look like this?

Once monthly spend crosses a certain scale, keeping up with optimization in-house stops being realistic.

Your monthly AWS bill keeps growing, but you can’t see what is costing what.
You haven’t adopted Reserved Instances or Savings Plans, or you can’t tell whether they’re actually working.
Unused resources (stopped EC2, orphaned EBS, undeleted snapshots) are probably sitting around.
Specs set at the original estimate may now be over-provisioned for your current load.
Data transfer and NAT Gateway charges are higher than expected.
Leadership is asking for cost reductions, but you don’t have the bandwidth to do it in-house.
Reasons

The savings you can expect

Actual savings vary with your architecture and business phase. The figures below are general guidance.

−20–30%

Monthly savings (guideline)

By trimming over-provisioning and unused resources and revisiting purchase options, we can often cut 20–30% of your monthly AWS spend. The real number depends on your setup, so we show it in the report after the assessment.

30 items

Standard checklist

We check every cost-generating area — EC2 / RDS / EBS / S3 / Network / IAM and more — across 30 items, leaving nothing out.

2 weeks

Time to completion

From the moment we receive read access to your invoices and Cost Explorer, we deliver the report in as little as 10 business days.

Scope

What we cover

A systematic checklist of cost-reduction checkpoints that surfaces everything without gaps.

01 Compute

Compute

We analyze instance sizes, CPU utilization, and running hours across EC2 / ECS / Lambda / Fargate. We surface over-provisioned resources and ones left running by mistake.

  • EC2 instance right-sizing
  • Stop / start scheduling proposals
  • Room to move to Spot / Graviton
  • ECS task CPU / memory settings
  • Lambda concurrency & timeouts
  • Unused AMIs / snapshots
02 Storage

Storage & databases

Focusing on EBS / S3 / RDS / DynamoDB, we revisit storage classes, backups, and snapshot retention.

  • EBS volume-type optimization
  • S3 storage-class classification
  • Undeleted snapshots
  • RDS instances & storage
  • Backup retention periods
  • DynamoDB capacity mode
03 Network

Network & data transfer

We check the places you can cut significantly just by changing the setup — NAT Gateways, data transfer charges, CloudFront cache settings, and more.

  • Rethinking NAT Gateway routing
  • Making use of VPC Endpoints
  • Pinpointing sources of data transfer
  • CloudFront cache optimization
  • Route 53 / Global Accelerator
  • Whether multi-AZ is really needed
04 Purchase

Purchase-plan optimization

We calculate the room to use Savings Plans and Reserved Instances from your past 12 months of usage, and propose a safe range to commit.

  • Compute Savings Plans
  • EC2 Instance Savings Plans
  • RDS / ElastiCache RIs
  • Modeling 1-year & 3-year commits
  • Measuring the effect of existing plans
  • A phased purchase schedule
05 Idle

Unused & low-utilization resources

We surface resources that are “stopped but still billed” or “running but unused.” This includes proposals to tidy up your tagging.

  • Unattached EBS / IPs
  • Stopped EC2 and related resources
  • Low-utilization EC2 / RDS
  • Unused load balancers / NATs
  • Abandoned dev environments
  • Tagging-policy proposals
06 Governance

Operational governance

So costs don’t balloon again after the assessment, we propose operating rules and an alerting setup. This includes making use of Cost Anomaly Detection.

  • Budget-alert design
  • Cost Anomaly Detection
  • Account & organization structure
  • Billing visibility (Cost Explorer)
  • A FinOps process proposal
  • A monthly-review cadence
Process

How the assessment works

The only access we ask for is read-only (ReadOnly) — we never make changes to your production resources.

  • 01Request & NDA — share your monthly AWS spend with us.
  • 02Grant access — grant our dedicated IAM user ReadOnlyAccess plus billing read permission.
  • 03Assessment (up to 10 business days) — we collect and analyze data via Cost Explorer / Trusted Advisor and the relevant APIs.
  • 04Report — we present likely savings, priority, and implementation difficulty item by item, in a PDF.
  • 05Briefing & implementation talk — we share the findings in a 1-hour briefing. For implementation, you can choose in-house, our team, or a savings-share model.
Plans

Engagement formats

The assessment is a fixed price; for implementation you can choose from three models.

Implement

Implementation support

  • Implementation of the proposed items
  • Including testing of the impact
  • Measuring the effect after implementation
  • Scope agreed individually in the contract
Share

Savings-share model

  • Implementation with no upfront fee
  • Settled on the savings actually achieved
  • Terms set in an individual contract
  • Requires monthly spend above a certain scale
Comparison

Compared with the alternatives

With AWS cost optimization, how you go about it changes the result.

Option A

Doing it in-house

  • Hard to cover every savings item
  • Tough to judge RI / Savings Plans commitments
  • Stalls because it’s done between other work
  • No systematic way to measure the effect
Option B

Hiring a large AWS partner

  • A long-term contract is assumed, so an assessment-only ask is hard
  • The assigned staff’s remit is narrow
  • Fixed costs pile up
  • Report granularity depends on the vendor
SHANNON Pack

AWS Cost Reduction Assessment

  • 30-item check leaves nothing out
  • Read-only access only — no changes to production
  • You can choose to stop at the assessment
  • Choose share / one-off / recurring
FAQ

Frequently asked questions

The access for the assessment is ReadOnlyAccess plus billing read only, so we work in a state where making changes to resources is technically impossible. Before moving to an implementation phase, we agree the scope and steps in writing first.
The return on the assessment tends to show for customers whose monthly AWS spend exceeds a certain scale. Below that, the assessment fee may not be recouped, so we give you a rough estimate during the free consultation.
Yes. As long as we can see consolidated Cost Explorer from the master account, we can assess across all accounts. For a large number of accounts, we quote separately.
This package is AWS-only. For GCP / Azure cost questions, we handle them individually as spot support under infrastructure build & operations.
We deliver it in a form you can use for leadership reporting and budget approvals. For each savings item we rate risk, implementation difficulty, and expected savings on a three-point scale, structured to make internal sign-off easier.
Yes. After the assessment we offer a retainer to re-assess monthly or quarterly. It suits customers who want to shift to a more FinOps-style way of operating.
Request an assessment
Contact

Let’s talk — the first consultation is free.

Even if your requirements aren’t fixed yet, that’s fine. We reply within 2 business days.

You can also reach us by phone (050-1794-9651, automated voice; we call back on business days). For detailed enquiries with budget and timing, please use the contact form. Note: we do not accept sales solicitations.