Accelerated windows clouds Four-step migration DMZ to EC2

As a Windows administrator, are you looking for a better way to run the server? You're not looking for a solution that's either all or nothing. You have no plans to migrate all the transactions to any place. Why are you doing this? You've run a good enough data center.

But you do appreciate it because of the nature of the cloud: it's a place where you can host some of your server infrastructure, and of course it makes sense to do so. And you probably woke up this morning and realized what really meant something.

You want to migrate your DMZ.

Why the DMZ?

The IT buzzword in recent years is "virtualization candidate", where servers provide the best return on the money spent on virtualization. Now, a lot of people talk about "cloud candidate", when the server is hosted outside the data center, Windows professionals decide which server works best.

A cloud that makes sense for a particular cloud is a suite of components that make up your DMZ. Unlike everything else in your Windows infrastructure, the network for these servers has been isolated from the internal LAN. The hardware may serve end users, and it may also make it easier for internal users to use external services. In either case, the existing network isolation of the DMZ server combined with properly placed protection (firewalls, network ACLs, service isolation, etc.) makes this group perfectly fit for your first clouds.

This article focuses on Amazon's EC2 infrastructure, but depending on your specific needs, budget, and functionality you need, your execution can easily pass through hosting.com, Rackspace, Bluelock, VM Racks or any other stable growing regional provider in the array to replace EC2.

1. Find out what instances of your server need to combine

Amazon takes its virtual machine as an example and offers a number of hardware models to match the price. Examples can be provided with a range of operating systems, including Microsoft Windows Server 2003 R2, Windows Server 2008, and Windows Server 2008 R2.

A common confusion about choosing the right EC2 instance is mainly around its three available types. Most Windows servers are provided as an optional instance or as a reserved instance. The difference here is that the selected instance is charged on an hourly basis, while the reserved instance needs to be paid off before it is used, but in the long run the price is cheaper. In short, if these Windows servers are actually short term (in the case of days), select an alternate instance; if they are actually long-term (for example, by year), then a one-time payment is more cost-effective.

The third category is the spot instance, which is typically used when the application is encoded to scale across multiple servers when it is available. Now, if you're just starting out, you can ignore the spot instance.

2. Provide shared storage (if necessary)

Each instance model is provided with a pre-configured amount of local disk space. But some DMZ workloads require access to shared storage, such as what you might provide from a SAN. For these servers, your next step will be to provide one or more resilient block storage, and EC2 's claim is essentially for a San LUN. EBS can be attached to any server or multiple servers that share available areas, and it is a configurable server suite that you have decided to access.

3. Create a private network

The DMZ in many environments is often more than just a simple subnet that is exposed to the Internet. In many cases, the DMZ is in fact a collection of subnets, and its rules, access control lists, and other connectivity features are linked together to create a coherent whole for its services. Some areas of the DMZ may return to your internal LAN, while others are generally surrounded only by Internet access.

The next step in migrating windows to EC2 requires rebuilding those subnets, connections, and LAN consolidation. You can complete this process with a EC2 virtual private cloud. Its configuration is powerful but the concept is simple, and it is intuitive to create all of these logical connections with the EC2 console. You will find that your own network of required subnets created by IP determines the plan your VM needs.

4. Migrate your Windows Server from the DMZ to the new EC2 environment

In many cases this process requires a series of commands to run through the EC2 command-line toolset. If your DMZ machine is virtualized on the vsphere platform, you can download a different and simpler "important connector" as a vcenter virtual appliance. Either way, you'll find it relatively easy to prepare servers, upload them, and verify their settings.

(Responsible editor: The good of the Legacy)