AWS
AWS landing zone
Eight separate accounts for security, shared services, applications, and experiments, with rules set once at the top.
Jordan · Multi-Cloud Engineer
A stronger foundation for your cloud.
Secure, well-organized cloud environments on AWS, Azure, and Google Cloud, shaped around your team.
AWSMicrosoft AzureGoogle Cloud
Build with confidence
Organized foundations, written as code
Keep security in view
Clear controls and governance
See where money goes
Costs labeled and checked
Make delivery simpler
Consistent tools for your team
About
Hi, I'm Jordan.
I'm a multi-cloud engineer. I architect and build infrastructure on AWS, Microsoft Azure, and Google Cloud, following each provider's best practices and shaping the result around the business it serves.
BasedRemote, or hybrid in Chicago
Available forFull-time and contract (1099)
CertificationAWS Solutions Architect Associate
Featured solutions
A secure foundation on every major cloud.
One landing zone per provider, each built as code, deployed live, and torn down. Select one to see how it was built.
Microsoft Azure
Azure landing zone
A foundation for sensitive data where every new subscription inherits the security and tagging rules automatically.
Google Cloud
Google Cloud landing zone
A full organization built as code, where nobody holds permanent admin rights and only signed software runs.
Multicloud developer platform
Help your team get from idea to launch.
A shared platform that makes it easier to launch and manage applications across cloud providers. A developer fills in a short form and gets a code repository, a delivery pipeline, a database, and a running service, set up the approved way.
3 cloudsone request format
10 policiesmapped to SOC 2 and CIS
0 stored keysshort-lived access only
Shared platformTemplate · Review · Deploy
AWSECS Fargate · RDS
AzureContainer Apps · Postgres
Google CloudCloud Run · Cloud SQL
More solutions
Security, reliability, and cost, solved live
Select any solution to see its architecture diagram, the full case study, and the code.
Every solution, with full write-ups, is on jordandesigns.io/work.
Services
Services and practices
From moving you into the cloud to keeping it secure, affordable, and running. Each card links to a solution where you can see it in action.
Cloud migration
Moving applications and data into the cloud, or from one provider to another, with the secure foundation, access rules, and a rollback plan in place before anything moves.
See it in, , and landing zones, built to receive workloads
Cloud modernization
Updating older systems to run in containers or serverless services, so they scale on demand and cost less to run.
See it in,
Kubernetes
Clusters on all three clouds, run from Git, with network rules between services, runtime threat detection, and policies that block unsafe workloads before they start.
See it in, , ,
CI/CD
Continuous integration and delivery. Every change is tested and deployed automatically, so releases are small and routine.
See it in, ,
Infrastructure as code
Cloud resources defined in versioned files, so any environment can be rebuilt exactly, reviewed, or removed on demand.
See it inEvery solution here, written in Terraform; and
GitOps
The code repository is the source of truth. Only reviewed, approved changes reach the live system.
See it in,
DevSecOps
Security scans run inside the pipeline, catching leaked passwords and vulnerable software before release.
See it in,
Policy as code
Company rules written as automated checks that approve or reject changes on their own, mapped to standards such as CIS, SOC 2, and HIPAA.
See it in,
Least privilege
People and systems get only the access they need, often for a limited time, with no long-lived passwords or keys.
See it in,
Cost visibility
Every resource labeled with an owner and cost center, waste surfaced, and expensive changes caught before they reach the bill.
See it in,
Observability
Metrics, logs, and dashboards that show what a system is doing and why, before customers notice a problem.
See it in,
SLOs and error budgets
A reliability target, such as 99.9% uptime, with alerts that fire when the system is on track to miss it.
See it in
Automated failover
When a server, database, or region fails, traffic moves to a healthy copy without manual work.
See it in,
Incident runbooks
Written, often automated, steps for responding to known problems, so recovery does not depend on one person.
See it in, ,
Postmortems and decision records
Every failure and major choice written down with its cause and fix, so it does not happen twice.
See it in,
Golden images
Pre-hardened server templates, so every new machine starts secure and identical.
See it in and landing zones
Contact
Let's build your next foundation.
Planning a migration, modernizing what you run, getting costs under control, or hiring for a cloud role? Open to full-time roles and contract (1099) engagements, remote or hybrid in Chicago. Book a time or reach out directly.
Book a 30-minute callStart a conversation Pick a time below and I'll send a calendar invite with a video link.