Servers, backups, monitoring and incident response on AWS, documented so any server can be rebuilt. I look before I touch, and I write it all down.
Set up properly, then kept boring.
Setup, patching and access control on EC2, RDS, CloudFront, S3 and Lambda.
Backups that are verified, and a rollback you have actually practised.
Health checks, logs you can read and alerts that mean something.
Read-only reviews of IAM, security groups, GuardDuty, CloudTrail and backups, in every region.
A written plan for the day something looks wrong, and the experience to follow it.
A discovery file per server, with cron and queue config and checksums, so any box can be rebuilt or audited.
A written incident plan, so an emergency does not get improvised.
Nothing is stopped, changed or deleted until you say so, so the evidence stays intact.
AWS, code hosts and databases. An answer in one place is never the whole story.
A plain report with confidence levels. Containing and cleaning up are your calls.
The audit covers your infrastructure as well as your code.
You tell me what hurts. I tell you honestly if I can help. If I can’t, I’ll say so.
I go through your code, servers, releases and risks. You get a written scope of what I’d own and what I’d fix first.
The audit fee is credited to your first month. Month to month from there. Leave any time and keep everything.
No. Reviews are read only. Nothing is stopped, changed or deleted until you decide.
EC2, RDS, Lambda, S3, CloudFront, IAM, GuardDuty and CloudTrail, plus Docker and Linux servers.
In your repositories and your accounts, so you own it from day one.
No. It is month to month. Stay because it is working.
15 minutes. You tell me what hurts. I tell you honestly whether I can help. If I can’t, I’ll say so.