Programmatic way to reboot EC2 instances

Sometimes we might have to reboot EC2 instances. If the requirement is to restart EC2 instances regularly, we can achieve it by writing a small piece of code. I also came across a similar requireme…

Source: Programmatic way to reboot EC2 instances

Create EC2 Vitual Servers in Amazon Web Services

How to create new Virtual Servers in Amazon Web Services?

1. Log in to AWS Management Console

2. In Compute & Networking section select EC2 – Virtual Servers in the cloud

AWS Virtual Servers in Cloud

3. When you select EC2 Virtual Servers in Cloud, this is what you see EC2 Dashboard

EC2 Dashboard in AWS
EC2 Dashboard in AWS

3. Click on Launch Instance

Choose an Amazon Machine Image (AMI)Cancel and Exit

An AMI is a template that contains the software configuration (operating system, application server, and applications) required to launch your instance. You can select an AMI provided by AWS, our user community, or the AWS Marketplace; or you can select one of your own AMIs.


4. Choose an Instance Type

Amazon EC2 provides a wide selection of instance types optimized to fit different use cases. Instances are virtual servers that can run applications. They have varying combinations of CPU, memory, storage, and networking capacity, and give you the flexibility to choose the appropriate mix of resources for your applications. Learn more about instance types and how they can meet your computing needs

AWS  Instance Type


5: Configure Instance Details


Configure the instance to suit your requirements. You can launch multiple instances from the same AMI, request Spot Instances to take advantage of the lower pricing, assign an access management role to the instance, and more.


– Number of Instances
You can choose to launch more than one instance at a time.


– Purchasing Option


You have the option to request Spot Instances and specify the maximum price you are willing to pay per instance hour. If you bid higher than the current Spot Price, your Spot Instance is launched and will be charged at the current Spot Price. Spot Prices often are significantly lower than On-Demand prices, so using Spot Instances for flexible, interruption-tolerant applications can lower your instance costs by up to 90%. Learn more about Spot Instances.


– Network
Launch your instance into an Amazon Virtual Private Cloud (VPC). You can create a VPC and select your own IP address range, create subnets, configure route tables, and configure network gateways. Learn more about Amazon VPC.

– Subnet
A range of IP addresses in your VPC that can be used to isolate different EC2 resources from each other or from the Internet. Each subnet resides in one Availability Zone.


– Public IP
Requests a public IP address from Amazon’s public IP address pool, to make your instance reachable from the Internet. In most cases, the public IP address is associated with the instance until it’s stopped or terminated, after which it’s no longer available for you to use. If you require a persistent public IP address that you can associate and disassociate at will, use an Elastic IP address (EIP) instead. You can allocate your own EIP, and associate it to your instance after launch.


– IAM Role
IAM roles for EC2 automatically deploys and rotates AWS credentials for you, removing the need to store your AWS access keys with your application. Learn more about IAM roles for EC2.

– Shutdown behavior
Specify the instance behavior when an OS-level shutdown is performed. Instances can be either terminated or stopped.


– Enable termination protection
You can protect instances from being accidentally terminated. Once enabled, you won’t be able to terminate this instance via the API or the AWS Management Console until termination protection has been disabled.


– Monitoring
Enables you to monitor, collect, and analyze metrics about your instances through Amazon CloudWatch. Additional charges apply if you enable this option


– Tenancy
You can run your instance on single-tenant, dedicated hardware. This is ideal where corporate policies or industry regulations require physical isolation from other customers’ instances. You must select Dedicated tenancy if you’re launching into a VPC that has a dedicated tenancy attribute. Additional charges apply if you enable dedicated tenancy. Learn more about dedicated instances

aws configure instance details


6.  Add Storage

Your instance will be launched with the following storage device settings. You can attach additional EBS volumes and instance store volumes to your instance, or edit the settings of the root volume. You can also attach additional EBS volumes after launching an instance, but not instance store volumes. Learn more about storage options in Amazon EC2.

Add storage to aws
Add storage to aws

7. Tag Instance
A tag consists of a case-sensitive key-value pair. For example, you could define a tag with key = Name and value = Webserver. Learn more about tagging your Amazon EC2 resources.

Add Tag Instance
8. Configure Security Group

A security group is a set of firewall rules that control the traffic for your instance. On this page, you can add rules to allow specific traffic to reach your instance. For example, if you want to set up a web server and allow Internet traffic to reach your instance, add rules that allow unrestricted access to the HTTP and HTTPS ports. You can create a new security group or select from an existing one below. Learn more about Amazon EC2 security groups

AWS - Security Group

9. In the next window check the review of your configuration and launch 

10. Server is ready and running

11. To access your instance:

Open an SSH client. (find out how to connect using PuTTY)
Locate your private key file (intercloud.pem). The wizard automatically detects the key you used to launch the instance.
Your key must not be publicly viewable for SSH to work. Use this command if needed:

Connect to AWS Instance



Deploy a Microsoft SharePoint 2010 Server Farm in the Amazon Web Services

Deploy a Microsoft SharePoint 2010 Server Farm in the AWS Cloud in 6 Simple Steps

Learn how you can launch a Microsoft SharePoint 2010 server farm for a public facing website on Amazon Web Services (AWS) cloud infrastructure in 6 simple steps. This article provides all the necessary resources, including easy-to-launch AWS CloudFormation sample templates, and instructions on how to create Amazon Machine Images (AMIs) so that you can launch a fully functional highly-available Microsoft SharePoint 2010 server farm on AWS.

Install SharePoint 2010 in Amazon Cloud EC2

Source:  by Marek Czarzbon

– You need an EC2 Account by Amazon

2- Go to the AWS Management Console (Beta)

3- Start a new instance. Be aware about the region. I’ve started my server in Europe West.

Amazon EC2 SharePoint Installation

4- The Windows Server 2008 is not available as standard AMI Image, so switch to Community AMI and choose


P.S: Thanks to Helmut for the hint about the new version of the image ( see comment about the problems with the version 1.0). So please use the v101, in my case ami-91ebc0e5


I guess you just want to evaluate SharePoint 2010 and not to build a productive server on a beta version. So embedded SQL Express 2008 Server works for you perfect.

Installing SharePoint 2010 in Amazon EC2

5- Define the number of instances to 1 and define the security group. Here you need to allow the security group to access Remote Desktop – RDP on Port 3389

6- After you instance is running, download the password for you new server. Select you instance and click on “Get windows Admin Password”. The password is encrypted so you need you private key which you will receive from Amazon during you account activation. Please notice that it will last for about 5 minutes after start of a new instance until you will be able to get your password. Be patient :- )

7- Now you can connect to you server with Remote Desktop using the public DNS name of you server

8- Now we are on the server, so open IE and download SharePoint 2010 from the technet site. Please select the English Version!

Please select the Enterprise CAL version. To be able to download you must add this site http://* to the Trusted Sites

9- The download 0f 561 MB are very fast! So you need about 4 minutes!

10- The Amazon Image has the Power Shell Version 1.0 on it. You need to remove this feature at first. Go to control panel and click on Programs and features to remove it.

11- We also need the KB971831 Patch for Windows Server

Download and install it

12- Now we can start the installation of the SharePoint Server 2010 Beta. Click on the OfficeServer.exe which we have download before.

13- The first step: Install software prerequisites:

14- And then “Install SharePoint Server”. Please select the “Stand Alone” Version!

15- Enter your Product Key. You will find the MAK for example here:

16- And now wait for until the installation finished!

17- And start the configuration Wizard

18- Done!!!!

19- The SharePoint Server is running. An IE Site pops up. Please enter your server Administrator credentials

20- And here we go. Our first site:

Source: by Marek Czarzbon

VM Import – Bring Your VMware Images to The Cloud


If you have invested in virtualization to meet IT security, compliance, or configuration management requirements and are now looking at the cloud as the next step toward the future, I’ve got some good news for you.

VM Import lets you bring existing VMware images (VMDK files) to Amazon EC2. You can import "system disks" containing bootable operating system images as well as data disks that are not meant to be booted.