Half-day session

Cloud Architecture Review

Half a day with the engineers who would do the work, followed by a written assessment of what your architecture does well, where it will break, and the order in which to fix it.

Who this is for

Teams running on AWS, Azure or Google Cloud who suspect the architecture will not hold at the next level of scale, cost or scrutiny.

  • Half-day session
  • Written findings in five working days
  • Fixed scope, agreed before it starts

What happens in the session

We walk your architecture with whoever knows it best, on a screen share, with no preparation asked of you beyond access to read. We look at the account and network structure, how identity and permissions are granted, what happens when a component fails, where the cost actually goes, and how changes reach production today.

  • Account, subscription and project structure, and the blast radius of each
  • Network segmentation, ingress and egress, and what is reachable from where
  • Identity and permissions, and how far a compromised credential travels
  • Failure behaviour: what degrades, what falls over, and what recovers by itself
  • Cost concentration, and the three line items that dominate the bill
  • How code gets to production, and what that path cannot currently protect you from

What you get afterwards

Within five working days you receive a written assessment. It is addressed to an engineering audience, it names specific resources and configurations, and it is ordered by what would hurt most if left alone. It is yours whether or not you engage us further.

  • Findings ranked by risk, each with the evidence behind it
  • A remediation order, so the first fix is the one that matters most
  • An honest read on what is fine and should be left alone
  • Effort estimates in engineer-weeks, so you can plan or resource it yourself

Why it is worth half a day

Most architecture problems are not discovered by a tool. They are discovered by asking what happens when this fails, and following the answer. A scanner will tell you a port is open. It will not tell you that the account holding your backups shares a role with the workload that would be encrypting them. That is what the session is for.

Common questions

Do we need to prepare anything?

Read access to the console and one engineer who knows the system. Nothing else. Preparing for a review defeats the point of it.

What does it cost?

A consultant confirms the figure on the call once the scope is clear. It is a fixed price agreed before anything starts, never an open hourly engagement.

Are you going to tell us to rebuild everything?

Very rarely, and never as an opening position. Most estates need a handful of targeted changes, and the assessment says so plainly when that is the case.

Do we have to hire you afterwards?

No. The written findings are yours to act on with your own team, and they are written so that you can.

Contact

Tell us what
you are building.

A few lines is enough. We will come back with an honest view of whether we are the right people for it.

Prefer to talk? Call (888) 652-9469 or email contact@edcogroup.io, or book a call.