
You can read a routing table at a glance, you have chased packet loss through three vendors' equipment, and you have kept an office or data-centre network running for years. Then the job posts you scroll past start asking for AWS, Terraform and "cloud-native" experience, and your own title begins to feel narrow.
Going from network engineer to cloud engineer is a realistic move, and your networking background is the part that takes years to build. Routing, addressing, DNS, VPNs and troubleshooting all carry over. What changes is how the network gets built (through consoles, APIs and code) and a short list of new skills around it. This guide is for working network engineers and for anyone weighing a network engineer career transition.
It maps familiar networking concepts to their cloud counterparts and shows where the comparison stops holding. It then covers the skills to add, a cloud engineering roadmap with projects, roles, resume wording and a sourced look at pay. If you need a refresher on subnets, DNS and ports first, start with our networking basics guide.
In a data centre you rack a router, cable it and configure it. In the cloud there is no box to touch. You describe the network you want (a route table, a subnet, a gateway) and the provider builds it. The first big shift is that the network is created and changed through APIs, which means it can be scripted, reviewed and repeated.
The second shift is that the network is no longer a separate world. A cloud network lives in an account with identity rules, billing and monitoring. Who is allowed to change a route is decided by IAM (Identity and Access Management), and every gateway and data transfer shows up as a cost. The provider runs the physical network; you design and secure the virtual one on top of it.
On AWS the basic unit is the VPC (Virtual Private Cloud), your own isolated virtual network inside a region. Azure calls the same idea a VNet. If you want the full design detail, our AWS VPC guide covers it, so this article stays on the career side.
These are related ideas, not exact replacements. Use the table to know where to look first, then read the next section for the places where the comparison misleads.
| On-premises concept | Cloud counterpart | What differs |
|---|---|---|
| Routers and routing tables | VPC or VNet route tables; Transit Gateway as a routing hub | You add route entries (destination and target) rather than run a routing protocol between routers. The most specific route wins. BGP appears at the edge, on VPN and Direct Connect links. |
| VLANs and segmentation | Subnets, route tables and security rules | A subnet is an IP address range inside one Availability Zone. You segment with routing and security rules, not VLAN tags. |
| Firewall rules | Security groups, network ACLs, AWS Network Firewall, Azure Firewall | Security groups are stateful and allow-only. Network ACLs are stateless and have allow and deny rules. |
| Site-to-site VPN | AWS Site-to-Site VPN, Azure VPN Gateway | The cloud end is a managed gateway; you still configure and troubleshoot your own end. |
| Leased line or MPLS to a data centre | AWS Direct Connect, Azure ExpressRoute | A private link into the provider. Direct Connect needs BGP and 802.1Q VLAN support on your side. |
| Hub-and-spoke WAN design | Transit Gateway, VPC peering | Transit Gateway connects many VPCs and on-premises networks through one hub. Peering links two VPCs directly. |
| Hardware load balancers | Elastic Load Balancing, Azure Load Balancer and Application Gateway | Managed services with health checks and target groups; you do not size a box. |
| Internal DNS servers | Amazon Route 53, Azure DNS | Private zones are tied to VPCs or VNets and configured as resources. |
| SNMP, syslog and packet capture | VPC Flow Logs, CloudWatch, Reachability Analyzer, Azure Network Watcher | Flow logs record traffic metadata, not full packets. Network Watcher includes packet capture. |
| Device access control and NAC | IAM | IAM decides who may change cloud resources through the API. It does not filter packets. |
Our networking mistakes post shows what these misunderstandings look like in production, such as treating a cloud network like a flat data-centre LAN.
A web server cannot connect to its database on port 5432. In a data centre you would ping, trace the path, check the firewall, look at the VLAN and read the routing table. The cloud checks are the same questions in different places.

Azure has the same toolkit under Network Watcher: IP flow verify and effective security rules for filtering, next hop for routing, and connection troubleshoot for an end-to-end test. Network Watcher also offers packet capture, which will feel familiar.
Your networking knowledge covers the network side. A cloud engineer is also expected to manage servers, automate, control access and watch costs. Start with the essentials and leave the advanced items until you are working with them.
| Skill | Priority | Why it matters |
|---|---|---|
| AWS or Azure fundamentals | Essential | Regions, Availability Zones, compute, storage and the networking services above |
| Linux administration | Essential | Most cloud servers run Linux, and many network tools run from its command line |
| Bash or Python scripting | Essential | Automating checks and repetitive tasks, and calling cloud APIs |
| IAM and cloud security | Essential | Controls who can change your network; a common cause of outages and incidents |
| Monitoring and troubleshooting | Essential | Flow logs, metrics and alarms replace many on-device checks |
| Terraform and Infrastructure as Code | Essential for infrastructure roles | Builds networks from reviewed, repeatable files instead of console clicks |
| Cloud architecture and cost awareness | Important | Gateways and data transfer cost money; see our [FinOps guide](/blog/what-is-finops-for-cloud-engineers) |
| Containers and Kubernetes networking | Advanced | Useful once you work with container platforms |
| CI/CD | Advanced | Automates delivery of applications and infrastructure |
Do you need to program? You don't need to code like a software developer, but avoiding code entirely will limit you. Some cloud networking roles need little of it, as our post on learning AWS without programming explains, yet scripting and Terraform are what make you faster than someone clicking through the console. Aim for comfortable automation, not mastery of software development.
For Linux, our guides on Linux for cloud and essential Linux commands are good places to start.
The sequence below builds on what you know. The week counts are illustrative, assuming steady part-time study alongside a full-time job. Your pace will depend on your starting point and how much hands-on practice you get, and nothing here promises a job.
Pick one provider (our AWS vs Azure vs GCP comparison can help you choose). Learn regions and Availability Zones, VPCs and subnets, route tables, internet and NAT gateways, security groups, network ACLs and the basics of EC2. Build a working network before reading about the exotic services. Add IAM at this stage too; our IAM guide explains users, roles and policies.
Practise SSH, file permissions, services and logs on a cloud server. Write small Bash or Python scripts for jobs you already do by hand, such as checking whether a port answers or whether a hostname resolves. Use real connectivity problems as your practice material.
Rebuild your Stage 1 network in Terraform: the VPC, public and private subnets, route tables and security groups. Keep credentials out of the repository. Our Terraform roadmap covers the tool in more depth.
Projects only help if you can explain them. In an interview, be ready to say why a subnet is private, what a security group blocks, and how you would find a dropped connection. More ideas are in our post on AWS projects for your resume.
You do not have to aim for a senior cloud engineer role on day one. Titles vary between companies, so read the responsibilities, not just the name.
| Role | What it usually involves | How your background helps |
|---|---|---|
| Cloud Network Engineer | VPC or VNet design, routing, VPN, DNS and hybrid links | Closest to your current work |
| Cloud Support Engineer | Diagnosing customer or internal cloud issues | Troubleshooting under pressure |
| Junior Cloud Engineer | Compute, storage, IAM and monitoring across a platform | Fundamentals, plus growth in the other areas |
| Cloud Infrastructure Engineer | Terraform, networking and automation | Strong once Infrastructure as Code is added |
| Cloud Security Engineer | Network controls, IAM and compliance | Firewall and segmentation experience |
Keep your networking history. Reword it so a reader can see the link to cloud work, and only list cloud tools you have actually used. A learning lab is fine, as long as you call it a lab and not production experience.
| Typical networking line | Cloud-aware rewrite (only if true) |
|---|---|
| Configured and maintained routers and switches | Designed and troubleshot routing and IP addressing for a multi-site network, and rebuilt the same design as a VPC with public and private subnets in a lab |
| Managed firewall policies | Managed firewall rules and segmentation; applied the same approach with security groups and network ACLs in AWS |
| Maintained site-to-site VPNs | Maintained site-to-site VPN connectivity; built a lab VPN between a simulated data centre and a VPC |
| Troubleshot connectivity issues | Troubleshot connectivity issues using packet-level evidence; used VPC Flow Logs and Reachability Analyzer for the same job in AWS |
A move into cloud does not automatically raise your pay. What you earn depends on your total experience, the role, the employer, the city and whether you can handle production infrastructure. The figures below are estimates from public salary pages read on 12 November 2026. They come from different job titles and different groups of people, so treat them as a rough guide and not as offers.
| Source and role | Experience | Reported figure (₹ LPA) | Sample |
|---|---|---|---|
| Indeed India, Network Engineer | All levels | about 2.62 (₹21,838 a month) | 63 salaries |
| Payscale, Network Engineer | All levels | about 4.85 | 396 profiles |
| Payscale, Network Engineer | 1 to 4 years | about 4.19 (total pay) | 239 salaries |
| Indeed India, Cloud Engineer | All levels | about 10.61 | 106 salaries |
| Indeed India, Cloud Engineer, Bengaluru | All levels | about 11.09 | not stated |
| Payscale, Cloud Solutions Engineer | All levels | about 7.31 | 68 profiles |
| Payscale, Cloud Solutions Engineer | 1 to 4 years | about 4.98 (total pay) | 44 salaries |
| Payscale, Cloud Solutions Engineer | 5 to 9 years | about 20.1 (total pay) | 15 salaries, a small sample |
For city and company-type detail, see our cloud engineer salary guide. Strong networking experience combined with practical cloud skills may suit specialist roles better than starting from scratch in IT. That is a judgement, and the factors above still apply.
The move from network engineer to cloud engineer works best when you treat it as an extension. You already understand addressing, routing, security zones and failure. Learn how one cloud expresses them, add Linux, scripting, IAM and Terraform, and prove it with two or three projects you can explain.
A good first step: build one VPC with a public and a private subnet, then break it and fix it.
Moving from networking to the cloud draws on several skills at once, from Linux and scripting to cloud services and automation. MicroDegree's e-learning platform lets you explore its courses together and pick the ones that fill your gaps.
Start with the one your current or target employers use, because the networking concepts transfer between them. If you have no preference, look at the job posts you want and count which platform appears more often. Our [AWS vs Azure vs GCP comparison](/blog/aws-vs-azure-vs-gcp-career-growth-2026) goes into the trade-offs.
They still show that you understand routing, switching and troubleshooting, and those fundamentals do not expire. They will not replace cloud hands-on experience, so pair them with projects and one cloud certification instead of treating them as a substitute.
An associate-level certification on your chosen cloud is a sensible first step; see our guides to the [Cloud Practitioner](/blog/ultimate-aws-cpc-guide) and [Solutions Architect Associate](/blog/aws-saa-guide) exams, or the [certification roadmap](/blog/cloud-certification-roadmap-2026). AWS also offers the CloudOps Engineer - Associate, formerly SysOps Administrator, which recommends about a year of hands-on experience. The AWS Certified Advanced Networking - Specialty is being retired; AWS lists 31 December 2026 as the last day to take it, so check the current status before you register.
Enough to automate small jobs: reading a file, looping over a list of hosts, calling an API and handling errors. A good first set of scripts checks whether ports answer, resolves a list of hostnames and lists your cloud resources through the provider's SDK. You can add more as your projects need it.
Networks do not go away; they move into code, and many companies run a mix of data centre and cloud. The work shifts towards design, automation, security and troubleshooting across both, which is why engineers who understand both sides are useful. Nobody can promise how many roles will exist, so build skills that work in either setting.