Hybrid environment - Amazon Web Services (AWS) Tutorial

Let's talk through how you would determine connectivity needs for a hybrid environment. Many organizations have a hybrid environment, because they started off with their own physical data center and expanded to a cloud. Some environments are also a GPU centric environment where you would start in the cloud and then potentially have your own specialized hardware. One of the ways that you can do this is to use the storage gateway. And a storage gateway allows you to have your own interface that connects your data center, which is an on-premise system with, let's say, specialized storage, maybe NFS or SMB with snapshot in or some other, you know, exotic capability. And then you can connect that to AWS and access this unlimited storage with things like Amazon S3 or backup with Glacier. So it really it's the best of both worlds in these hybrid environments. Now, let's take a look at a automated patching solution. This is another thing that comes up a lot with a hybrid environment, is that you may want to have both your on-prem systems plus the cloud and have a way to patch things periodically. And so you could do this with tools like AWS systems manager. You can see here how you could create an AWS Lambda automatic patch that could go through and use all the capabilities of the AWS Cloud, but also apply those capabilities to on-prem servers.