AWS Builder Center
My Journey from On-Premise Windows Server to AWS Cloud Practitioner

My Journey from On-Premise Windows Server to AWS Cloud Practitioner

Let me illustrate you my methodology for how to translate decade plus of traditional sys admin expertise to cloud. This post is covering the map of on-premise infra (e.g physical firewall or Active Directory) to AWS enterprise architecture.

The past few years of my career have been steeped in traditional on-premise infrastructure. Whether managing Windows Server environments, configuring permissions in Active Directory, or deploying endpoint security on local networks, I’ve gained a well-rounded understanding of how enterprise environments are deployed. However, I recently realized the future of enterprise-scale operations isn’t on my local server rack - it’s in the cloud.
This led me on the current path of obtaining my AWS Certified Cloud Practitioner (CLF-C02) certification.
The difficulty of the transition When you've spent years working with physical boxes, blinking lights, and network cabling, the cloud can seem like a bit of an abstract concept initially. The familiar server room environment, the physical act of checking cables, and the hardware lifecycle management were constants of my previous roles. Embracing AWS meant leaving the hardware layer of IT behind and focusing on areas such as governance, automation and architecture.
Bridging on-premise and the cloud The most impactful realization in my journey so far has been the fact that I didn't have to reinvent myself. I just had to learn the AWS terminology and translate existing experience:
  • Active Directory and AWS Directory Service Active Directory’s concepts of users, groups, permissions and OUs remain exactly the same. We are just ditching patching servers running AD.
  • Firewall/Perimeter to Security groups/NACL's The concepts that were managed by a physical firewall or edge protection appliance are replaced by security groups that control ingress and egress traffic to individual EC2 instances as well as Network Access Control Lists (NACLs) that protect a subnet.
  • Physical servers and Virtual Machines to EC2 Instances Making the leap from provisioning an EC2 instance and to understanding how EC2s are essentially virtual computers provisioned from templates (AMIs) made the compute section of the Cloud practitioner exam significantly easier to navigate.

What’s next?

Learning the Cloud Practitioner is only the first step. My next step is to bridge the disconnect between my previous life of local IT ops and building large-scale, highly available enterprise systems on the cloud.
From this foundation, I’m aiming to pursue Solutions Architect training in the near future.
Are any other on-prem sysadmins out there moving to the cloud, share how you are bridging your experience into AWS down in the comments section below!
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article