Infrastructure Audit

An infrastructure audit is a focused assessment of your cloud environment: how it’s set up, what it’s costing you, where the security gaps are, and what’s causing the performance problems your team has been working around.

This isn’t a scan from an automated tool. I look at how your infrastructure is actually configured, how your services are connected, how your team deploys and operates things day-to-day, and where the real risks and waste are hiding. The result is a written report with specific, prioritized recommendations your team can act on.

What the Audit Covers

Security

  • IAM roles, permissions, and access patterns
  • Network configuration: VPCs, security groups, network ACLs, load balancers
  • Data protection: encryption, backup strategies, data lifecycle
  • Compliance gaps against industry standards

Cost

  • Resource utilization: are you paying for things you’re not using?
  • Pricing model analysis: are you on the right instance types, commitment levels, storage classes?
  • Data transfer costs, which are often the silent budget killer
  • Tagging and cost allocation: can you actually tell where the money is going?

Performance & Reliability

  • Architecture review: high availability, disaster recovery, scaling mechanisms
  • Bottleneck identification: what’s actually slow and why
  • Monitoring and alerting: does your team know when things break before users do?

Operations

  • Infrastructure as Code status: is your infrastructure documented and reproducible?
  • CI/CD pipeline review: how painful are deployments?
  • Environment isolation: can a dev change accidentally affect production?

What You Get

A written report with:

  • Executive summary: the key findings in plain language for stakeholders
  • Detailed technical analysis: what I found, with evidence
  • Prioritized recommendations: quick wins, medium-term improvements, and strategic initiatives
  • Implementation roadmap: realistic timelines, resource requirements, and dependencies
  • Cost analysis: current spend breakdown and specific savings opportunities

Plus two follow-up consultation sessions to walk through the findings, answer questions, and help your team plan next steps.

Timeline

Most audits follow this pattern:

  • Week 1: Discovery. Stakeholder interviews, system access, architecture mapping, data collection
  • Week 2: Analysis and report writing
  • Week 3: Report delivery and first follow-up session
  • Week 4: Second follow-up session

What I Need From You

  • Admin or read-only access to your cloud environments
  • Access to key stakeholders (30-60 minutes each)
  • Any existing documentation or architecture diagrams
  • Cost and usage reports

Pricing

The audit is a fixed-price engagement. The exact price depends on scope (a single AWS account with a handful of services is different from a multi-account, multi-region setup) but I’ll quote it upfront after our initial conversation.

If the audit reveals work that makes sense to continue with, we can discuss follow-on implementation at my standard weekly rate.

Interested?

Reach out and tell me a bit about your setup. I’ll let you know if an audit makes sense for your situation and what it would cost.