top of page
John Perkins

John Perkins

Admin

Founder & CEO

More actions

Profile

Join date: Jan 8, 2020

About

John founded Habitat3 in 2006 and has spent more than two decades helping Australian businesses navigate the evolution of cloud infrastructure. As CEO, John leads the commercial direction of the business, working closely with customers to understand their goals, challenges and growth plans. He focuses on ensuring Habitat3 builds out service delivery and pricing models that deliver high-value, practical outcomes that align client technology investments with business objectives. John works extensively with SaaS companies, AI platforms and technology-driven businesses, helping them develop cloud strategies that support growth, reliability and operational maturity.


Connect with John on Linkedin: https://www.linkedin.com/in/habitat3cloud/

Posts (7)

Jul 2, 2026 ∙ 2 min
Your workloads look healthy, but is your AWS account?
You may be monitoring your AWS workloads. But are you monitoring the changes being made to AWS itself? When we review AWS environments, we often see good operational monitoring in place: EC2 CPU utilisation RDS storage and performance ECS task health Lambda errors Application availability That kind of monitoring is important. But it only tells part of the story. One area that is often overlooked is monitoring changes to the AWS control plane — the configuration and management layer that...
6
0
Jun 25, 2026 ∙ 2 min
Your AWS Backups Might Be Fine. Your Disaster Recovery Strategy Might Not Be
Here's a question every digital platform should be able to answer: "If our AWS production environment became unavailable today, how quickly could we recover?" Many cloud-native businesses assume that because they run entirely on AWS, disaster recovery is largely taken care of. It's a surprisingly common misconception. Having backups is important. But having backups is not a disaster recovery strategy. If a critical application became unavailable today, could your team answer the following...
0
0
Jun 25, 2026 ∙ 1 min
Is your AWS Identify Access Management (IAM) setup quietly putting your business at risk?
One of the most common things we see when reviewing AWS environments isn't a vulnerable server, an exposed database or a misconfigured firewall. It's Identity and Access Management (IAM). The permissions, users and roles that determine who can access your AWS environment and what they're allowed to do. Most AWS environments we review have at least one of these issues: ❌ Root account without MFA enabled ❌ IAM roles with unrestricted Administrator Access ❌ Shared credentials between team...
3
0
bottom of page