Windows hosting from Amazon Web Services
Hi habrovchane! 
I have told you quite a lot about AWS, but most of the articles relate exclusively to Linux and free software. Today I decided to talk about Windows and the Amazon Web Services capabilities associated with starting Windows Servers.
So, the main page about Windows on AWS is aws.amazon.com/windows . So, we are provided with the following server startup options:
In addition, you can upload your Windows images via AWS Import / Export service . We, for example, provide servers on Windows 2k3 in this way .
')
I would like to devote this article to two main points - launching a new server and licensing Microsoft products to AWS.
So, launching a server running Microsoft OS is no different from the usual Linux start.
1. Login to the console .
2. Making Launch Instance:
3. Choose the image we need:
4. Further, further, further.
So, the instance has started and is now waiting to be logged into it.
5. Verify that the Security Group contains the RDP port open:
Trace, and even MS SQL is also open to the outside.
6. Get the password from Windows:
7. Next, we will be asked to decrypt the password with your key:
8. Decrypted password and ready for login:
We can also download a .rdp file with connection parameters without a password:
Well, now we can log in and see what and how in this server:
We started the server with SQL preinstalled and we can observe this software already there:
That's it, we can also raise servers using the API / CLI.
The most terrible and sensitive issue for all users of software products from Microsoft is the correct licensing of these products. How does this happen in AWS?
First of all, AWS charges licenses for Windows Server from any instances, whether they are official AMIs or those made by us. Payment is made by the hour along with the cost of the instance type. The same goes for SQL Express / Web / Standard licenses. Pricing is separate.
Secondly, AWS provides the license migration service for the following products from other places to your cloud:
SQL Server Licensing Nuances : aws.amazon.com/windows/mslicensemobility/sql
In general, on the links I provide, you can read comprehensive licensing information for Windows @ Amazon Web Services.
One of the main advantages of using Windows in AWS is that you only pay for what you use, and you don’t need to buy a bunch of servers, you scale Windows as well as Linux and you don’t think about licenses.
I have told you quite a lot about AWS, but most of the articles relate exclusively to Linux and free software. Today I decided to talk about Windows and the Amazon Web Services capabilities associated with starting Windows Servers.
So, the main page about Windows on AWS is aws.amazon.com/windows . So, we are provided with the following server startup options:
- Microsoft Windows Server 2008 Base
- Microsoft Windows Server 2008 R2 Base
- Microsoft Windows Server 2008 R2 with SQL Server Express and IIS
- Microsoft Windows Server 2008 R2 with SQL Server Web
- Microsoft Windows Server 2008 R2 with SQL Server Standard
- Microsoft Windows Server 2012 Base
- Microsoft Windows Server 2012 with SQL Server Express
- Microsoft Windows Server 2012 with SQL Server Web
- Microsoft Windows Server 2012 with SQL Server Standard
In addition, you can upload your Windows images via AWS Import / Export service . We, for example, provide servers on Windows 2k3 in this way .
')
I would like to devote this article to two main points - launching a new server and licensing Microsoft products to AWS.
Start Windows Server
So, launching a server running Microsoft OS is no different from the usual Linux start.
1. Login to the console .
2. Making Launch Instance:
3. Choose the image we need:
4. Further, further, further.
So, the instance has started and is now waiting to be logged into it.
5. Verify that the Security Group contains the RDP port open:
Trace, and even MS SQL is also open to the outside.
6. Get the password from Windows:
7. Next, we will be asked to decrypt the password with your key:
8. Decrypted password and ready for login:
We can also download a .rdp file with connection parameters without a password:
$ cat Downloads/ec2-54-234-124-157.compute-1.amazonaws.com.rdp auto connect:i:1 full address:s:ec2-54-234-124-157.compute-1.amazonaws.com username:s:Administrator Well, now we can log in and see what and how in this server:
$ rdesktop -u Administrator -p 3ghcEhvWP6 ec2-54-234-124-157.compute-1.amazonaws.com We started the server with SQL preinstalled and we can observe this software already there:
That's it, we can also raise servers using the API / CLI.
Licensing
The most terrible and sensitive issue for all users of software products from Microsoft is the correct licensing of these products. How does this happen in AWS?
First of all, AWS charges licenses for Windows Server from any instances, whether they are official AMIs or those made by us. Payment is made by the hour along with the cost of the instance type. The same goes for SQL Express / Web / Standard licenses. Pricing is separate.
Secondly, AWS provides the license migration service for the following products from other places to your cloud:
- Microsoft Exchange Server
- Microsoft SharePoint Server
- Microsoft SQL Server Standard Edition
- Microsoft SQL Server Enterprise Edition
- Microsoft Lync Server
- Microsoft System Center Server
- Microsoft Dynamics CRM Server
SQL Server Licensing Nuances : aws.amazon.com/windows/mslicensemobility/sql
In general, on the links I provide, you can read comprehensive licensing information for Windows @ Amazon Web Services.
One of the main advantages of using Windows in AWS is that you only pay for what you use, and you don’t need to buy a bunch of servers, you scale Windows as well as Linux and you don’t think about licenses.
Source: https://habr.com/ru/post/168367/
All Articles