Migration of On-Premises to Public Cloud

When a businesses migrated from on-premises to the public cloud, you will find things done differently. As an enterprise, even if you are used to building the high performing and resilient application, when you move to a cloud, you will find that while you can build with more agility and scale, you end up having less control than you have on on-premises.
In-fact, the biggest reason enterprises move to the cloud is the agility to deploy applications with greater speed and agility. It is the application developer who led the charge on the front. They realize that with a simple swipe of a credit card, they could deploy in the cloud database or a web server or a Kubernetes cluster within minutes. Whereas on-premises, they have to work with their IT teams to get infrastructure deployed which could take a very long time and usually really requires some sort of budget approval. So Shadow IT become a thing into the cloud.
It is really a urgency of DevOps that triggered this move and networking and security teams found them slagging behind. Networking is all about routers, switches, load balancers and Layer 4 & Layer 7 firewalls and advanced protection gateways such as Intrusion Prevention System and Threat Intelligence. They don’t fit in the picture of public cloud the same way they do on on-premises. It is not one-to-one mapping when going to cloud because cloud offers its own set of infrastructure and services that provide a foundation for building an application. Well that means is from networking and security standpoint, the center of gravity in a public cloud is flipped on its end. In on-premises, for an application to be accessible from the internet or to go out through the internet, They usually have to go through DMZ where some inspection takes place for security and compliance reasons. It’s not like that in the public cloud, some CSPs you can give an application a public IP and it become immediately accessible from the internet.
This is very different model that enterprises are trying to manage. you may be thinking what’s the big deal, it turns out even something is fundamental to networking as a route table is handled differently by each CSP. Moreover, in the cloud we can see new constructs such as identity and management IAM accounts, subscriptions and tenants. Each CSP has its own unique way of IAM and each CSP has its own unique way to manage services to provide networking and security.