See the true state of your AWS setup, then decide the next move

We find out if your applications can move yet, or how sound your current AWS environment is, and rank what to fix by how risky it is and how much work it takes.

Sound familiar?

Which of these sounds like your team?

Cloud-ready, or not yet?

Some applications might be fine on AWS and others not, and the running cost is still a guess.

Nobody wrote it down

Ask how a service is set up, and the only answer is to log in and look.

A bill nobody can explain

Each month someone asks why it went up, and no one has a firm answer.

Can you prove it's secure?

When an auditor or a customer asks, you want more than reassurance to show them.

Recovery that's only theory

If you lost a system tomorrow, nobody knows whether the backups or failover would bring it back.

Leadership is waiting on you

They want a plan, with priorities and costs, that they can approve.

Process

How we work

  1. 01

    Set the boundaries

    We settle which workloads are in the review and what you want to get out of it.

  2. 02

    Review

    Each workload is measured up to the Well-Architected Framework that AWS publishes.

  3. 03

    Write it up

    You receive the findings in priority order, with what each one would take in time and money.

  4. 04

    Fix what matters

    Your engineers act on the report, or Grootan does the work with them or for them.

Specifics

Technical details

  • Workloads are judged on all six Well-Architected pillars: reliability, security, cost optimisation, performance efficiency, sustainability and operational excellence
  • For a planned move, we check each application's dependencies, data and licences, your team's skills, and what it would cost to run on AWS
  • Every finding carries a risk rating and an estimate of the work needed
  • The review is done remotely, using read-only access to your accounts

Options

Flexible to fit you

  • Get ready for a move to AWSorCheck the AWS setup you already run
  • Look at one workload in depthorLook across your whole AWS estate
  • You take the findings and act on themorGrootan also makes the fixes
  • We review once and step backorWe come back every year to review again

Measurement

What we measure

  • How many serious risks have been fixed
  • What you spend on AWS each month
  • How long a restore really takes when you try one
  • Security issues still waiting for a fix

FAQ

Questions we hear

What will an assessment tell us?

If you haven't moved yet, you learn which applications could move to AWS now. If you're already there, you learn how well your environment is running. Either way, you get findings you can act on.

Which parts of our setup does the Well-Architected review judge?

AWS splits good architecture into six pillars, and we check your workloads against each one: security, reliability, cost, performance, sustainability and how well you operate them.

What will you need from us?

Mostly some hours of time from the people who know your systems. Beyond that, read-only rights on the AWS accounts or, if you haven't moved yet, a description of your applications.

How is the price of a review set?

By how much there is to look at and how complex it is. We go over both on the first call.

Let's review your AWS setup

Related

More Cloud & AWS services