Hybrid Cloud Infrastructure! The Fork Between a Local and a Cloud Place.
Hybrid Cloud Infrastructure is when your local infrastructure and your cloud infrastructure create a seamless network. As an administrator you no longer view cloud and local as unique infrastructure, but rather as a single network map.
AWS, MS Azure and VMware offer solutions to allow you to begin the migration of your infrastructure to the cloud. Seamlessly located on local and cloud based solutions, as if the cloud structure is a site for the local infrastructure. Allows you to offload servers and services, low value, up to the cloud and let the cloud handle it while retaining the security and compliance with the local servers. This allows an easier migration transition. Infographic Source
Before, infrastructure was the client-server architecture model where clients would connect through a network to the server to request for sevices and information. After LANs and WANs were established, there were web services that would be able to provide services through the internet (think email servers i.e exchange, or anything more cloud based like Hotmail, Gmail, etc), however the issue was with the client-server infrastructure and how it could not really be applicable with these web services nor was it really robust and secure in case of physical and natural disasters. Cloud infrastructure was next and with it came with more ability to configure and secure the cloud and web services that were not being run locally. However, the problem is now the “cloud infrastructure” and how there was a disconnect between local and cloud systems and now hybrid cloud infrastructures help to bridge the disconnect and connect them all seamlessly without requiring configurations on both the local and cloud infrastructure.
What makes a hybrid cloud infrastructure?
-Both Virtualization (spinning up instances) and Web Services (Amazon EC2 for storage or the Azure MSSQL database compatibility) offered
-Ability to control virtual network, allows communication between all of the instances and services configured. Being able to create multi-level networks by segmenting them off so that only the necessary servers have specific networking roles.
-Ability to robustly connect to local network, configuration and security must be seamlessly done.
-Active Directory Connector, still a very common thing and both AWS and Azure both have the abilities to link the necessary Active Directory connector to synchronize and replicate the necessary policies.
Security Concerns for migrating to the cloud?
-Any server connected to a network that is connected to the Internet is on the “cloud”. Is the cloud really that unsecure? There have been many years brought into developing these cloud services so they’re not going to be “piss poor” on cyber security configurations on their end and anyone worth a salt in security configuration like a system administrator should know how to secure and harden their own servers regardless if it’s being hosted locally or on the cloud.
-Local network is vulnerable to physical damage and attack, that’s not true. The fact that someone has to know how to deal with the cloud already makes the local infrastructure much more insecure. A physical server in a physical environment can face any kind of physical problem.