— Azure Cloud & DevOps Engineer
Cloud platforms, engineered from the foundations up.
I’m Tomasz Chorąży. I design, automate and maintain cloud infrastructure on Azure and AWS, using Infrastructure as Code, Kubernetes and CI/CD pipelines that treat security as part of the design.
KubestronautAll five CNCF Kubernetes certificationsAzure
Networking, identity, governance
Terraform & Bicep
Infrastructure as Code
Kubernetes
Administration, delivery, security
CI/CD
GitHub Actions, Azure DevOps
Cloud security
Access control and policy
01 / About
A systems administrator’s instincts, applied to cloud platforms.
I started in systems administration, looking after servers, operating systems and networks. That background still shapes how I work: I want to understand what is happening underneath a platform before I automate on top of it.
Over time the work moved from manual administration to automation. Infrastructure became code in Terraform and Bicep, environments became something you can recreate on demand, and deployments became pipelines that run the same way every time. Today I build and maintain cloud environments for real projects, mostly on Azure, with AWS experience alongside it.
More recently I completed all five CNCF Kubernetes certifications and earned the Kubestronaut designation. The security part of that path, KCSA and CKS, deepened how I think about protecting clusters and the workloads that run on them. It was also a reminder that this field rewards people who keep learning.
How I work
01
Foundations first
Networking, identity and access come before workloads. Platforms built on a sound base are easier to operate and to change.
02
Everything as code
If an environment matters, it should be defined in version control, reviewed like software and reproducible without tribal knowledge.
03
Security in the design
Short-lived credentials, least-privilege access and policy guardrails belong in the first version of a pipeline, not in a later hardening pass.
04
Built to be handed over
I document how to change and extend what I build, so the team that runs it next can do so safely.
02 / Expertise
Areas of professional experience.
These are the areas I have worked in most. An engagement rarely needs all of them; the value is in knowing how they fit together.
Cloud infrastructure & architecture
Designing, provisioning and standardizing cloud environments so that teams get a consistent, well-governed base to build on, from subscriptions and identity to network connectivity.
- Azure
- AWS
- VNets & peering
- ExpressRoute
- Azure Container Apps
Infrastructure as Code & automation
Modular, reusable infrastructure definitions that make environments repeatable. That includes importing resources that already exist into code, so nothing has to be rebuilt to become manageable.
- Terraform
- Bicep
- Ansible
- Reusable modules
- Resource import
DevOps & CI/CD
Automated build, test and deployment workflows that make releases routine. Pipelines authenticate with federated identity instead of stored secrets wherever the platform supports it.
- GitHub Actions
- Azure DevOps
- Jenkins
- Atlassian Bamboo
- Federated identity
Kubernetes & cloud-native engineering
Cluster administration and application delivery for containerized workloads, using GitOps practices and Kubernetes security best practices, across both Azure and AWS environments.
- Kubernetes
- Helm
- Argo CD
- Docker
Security, governance & observability
Access control, privileged access management and policy that keep environments within agreed boundaries, plus the monitoring and alerting needed to see how systems actually behave.
- Cloud identity & access
- Azure Policy
- Prometheus
- Grafana
Data & AI platform infrastructure
The infrastructure layer underneath analytics and machine learning work: provisioning workspaces, wiring up data integration and putting data governance in place.
- Azure Databricks
- Unity Catalog
- Azure Data Factory
- Azure Machine Learning
03 / Experience
Where this has been put to work.
A few examples of the kind of infrastructure work I have done, described in general terms.
01
IoT platform infrastructure
I built the infrastructure for an IoT platform that first ran on Docker Swarm, and later took it through the migration to Kubernetes.
02
From hand-built to Infrastructure as Code
I have taken infrastructure that was originally set up by hand and brought it under Infrastructure as Code, so it can be reviewed, changed and reproduced from version control.
03
Self-service analytics and AI environments
I build Azure analytics and AI environments entirely from code. Users request one in a platform UI and get a ready-to-use setup with Azure Databricks and Microsoft Foundry.
04 / Certifications
Credentials that back up the practice.
CNCF designation
Kubestronaut
The Kubestronaut designation recognizes engineers who have passed all five CNCF Kubernetes certifications, covering administration, application development and security.
View my entry in the CNCF Kubestronaut directory(opens in a new tab)The five Kubernetes certifications
CKA
Certified Kubernetes Administrator
CKAD
Certified Kubernetes Application Developer
CKS
Certified Kubernetes Security Specialist
KCNA
Kubernetes and Cloud Native Associate
KCSA
Kubernetes and Cloud Native Security Associate
Cloud, DevOps and systems
Azure Solutions Architect Expert (AZ-305)
Microsoft
DevOps Engineer Expert (AZ-400)
Microsoft
Azure Administrator Associate (AZ-104)
Microsoft
Azure Fundamentals (AZ-900)
Microsoft
NVIDIA-Certified Associate: AI Infrastructure and Operations (NCA-AIIO)
NVIDIA
HashiCorp Certified: Terraform Associate (002)
HashiCorp
GitHub Actions
GitHub
Red Hat Certified System Administrator (RHCSA)
Red Hat
05 / Contact
Have a cloud infrastructure problem worth solving?
I’m open to conversations about Azure, DevOps, Infrastructure as Code and Kubernetes work, whether that is a project or a longer consulting partnership. I provide my services on a B2B basis. A short description of what you are working on is the best place to start.