You run a single instance application on an EC2 instance in AWS. your architecture reams are looking to make changes and convert the application to operate on multiple servers. The app runs on Linux and currently access millions of flat file data file in the /data/… folder structure.
This database is stored on an EBS volume attached to the EC2 instance. How can this be moved to work on multiple servers with as little application changes as possible? What product would you suggest?
For this use-case, you should start looking at the new Amazon Elastic File System (EFS), which is designed to be multiply attached in exactly the way you are wanting. The key difference between EFS and EBS is that they provide different abstractions: EFS exposes the NFSv4 protocol, whereas EBS provides raw block IO access.
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
3. When you select EC2 Virtual Servers in Cloud, this is what you see EC2 Dashboard
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
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.
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
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.
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.
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
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:
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.