I will harden your AWS cloud network, vpc, security groups and public exposure

How much of your AWS account is reachable from the internet right now?

Most accounts cannot answer. Rules were opened for a deploy and never closed, subnets made public to make something work, and nobody has drawn it since.

You are probably here because

• You do not know what is exposed and would rather find out
• A rule opened temporarily is still open
• An auditor or insurer asked about network segmentation

What I change

• Security groups open to the world on management ports, closed
• Public subnets emptied of what should not face the internet
• VPC segmented so one instance cannot reach it all
• Flow logs on, private service access, so traffic stops leaving

How it works

1. You tell me what you run and we agree a change window
2. I apply changes, confirm nothing broke, log every one
3. You get the documentation, rollback path and a walkthrough

What you can count on

Every change reversible, in a window you choose. Anything that could interrupt traffic is flagged.

Works with

AWS VPC, security groups, Route 53, load balancers, Transit Gateway.

Validated against CIS AWS Foundations and Well-Architected.

Tell me what you run and I will say which fits.