1. Log in to the AWS Management Console
2. Click on s3 tab
3. Create a new bucket
4. Create a custom/aws bucket policy to make it world readable
The term ‘Load Balancer’ is quite self-explanatory, it balances the load on application servers behind it. There can be ‘n’ number of application servers behind the Load Balancer (LB) which would not be directly facing the end users.
“ To produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private cloud providers regardless of size, by being simple to implement and massively scalable.”
OpenStack is a collection of open source software projects that enterprises/service providers can use to setup and run their cloud compute and storage infrastructure.Rackspace and NASA are the key initial contributors to the stack. Rackspace contributed their “Cloud Files” platform (code) to power the Object Storage part of the OpenStack, while NASA contributed their “Nebula” platform (code) to power the Compute part. OpenStack consortium has managed to have more than 150 members including Canonical, Dell, Citrix etc.
• Nova – Compute Service
• Swift – Storage Service
• Glance – Imaging Service
• Keystone – Identity Service
• Horizon – UI Service
Nova is the Computing Fabric controller for the OpenStack Cloud. All activities needed to support the life cycle of instances within the OpenStack cloud are handled by Nova. This makes Nova a Management Platform that manages compute resources, networking, authorization, and scalability needs of the OpenStack cloud. But, Nova does not provide any virtualization capabilities by itself; instead, it uses libvirt API to interact with supported hypervisors. Nova exposes all its capabilities through a web services API that is compatible with the EC2 API of Amazon Web Services.
• Instance life cycle management
• Management of compute resources
• Networking and Authorization
• REST-based API
• Asynchronous eventually consistent communication
• Hypervisor agnostic : support for Xen, XenServer/XCP, KVM, UML, VMware vSphere and Hyper-V
Swift provides a distributed, eventually consistent virtual object store for OpenStack. It is analogous to Amazon Web Services – Simple Storage Service (S3). Swift is capable of storing billions of objects distributed across nodes. Swift has built-in redundancy and fail-over management and is capable of archiving and media streaming. It is extremely scalable in terms of both size (several petabytes) and capacity (number of objects).
• Storage of large number of objects
• Storage of large sized objects
• Data Redundancy
• Archival capabilities – Work with large datasets
• Data container for virtual machines and cloud apps
• Media Streaming capabilities
• Secure storage of objects
• Backup and archival
• Extreme scalability
OpenStack Imaging Service is a lookup and retrieval system for virtual machine images. It can be configured to use any one of the following storage backends:
• Local filesystem (default)
• OpenStack Object Store to store images
• S3 storage directly
• S3 storage with Object Store as the intermediate for S3 access.
• HTTP (read-only)
• Provides imaging service
Keystone provides identity and access policy services for all components in the OpenStack family. It implements it’s own REST based API (Identity API). It provides authentication and authorization for all components of OpenStack including (but not limited to) Swift, Glance, Nova. Authentication verifies that a request actually comes from who it says it does. Authorization is verifying whether the authenticated user has access to the services he/she is requesting for.
Keystone provides two ways of authentication. One is username/password based and the other is token based. Apart from that, keystone provides the following services:
• Token Service (that carries authorization information about an authenticated user)
• Catalog Service (that contains a list of available services at the users’ disposal)
• Policy Service (that let’s keystone manage access to specific services by specific users or groups).
Horizon the web based dashboard can be used to manage /administer OpenStack services. It can be used to manage instances and images, create keypairs, attach volumes to instances, manipulate Swift containers etc. Apart from this, dashboard even gives the user access to instance console and can connect to an instance through VNC. Overall, Horizon
• Instance Management – Create or terminate instance, view console logs and connect through VNC, Attaching volumes, etc.
• Access and Security Management – Create security groups, manage keypairs, assign floating IPs, etc.
• Flavor Management – Manage different flavors or instance virtual hardware templates.
• Image Management – Edit or delete images.
• View service catalog.
• Manage users, quotas and usage for projects.
• User Management – Create user, etc.
• Volume Management – Creating Volumes and snapshots.
• Object Store Manipulation – Create, delete containers and objects.
• Downloading environment variables for a project.
We can install open stack ESSEX very easily using StackGeek script. Login to your box and install git with apt-get. We’ll become root and do an update first.
sudo su
apt-get update
apt-get install git
Now checkout the StackGeek scripts from Github:
git clone git://github.com/StackGeek/openstackgeek.git
cd openstackgeek
Be sure to take a look at the scripts before you run them. Keep in mind the scripts will periodically prompt you for input, either for confirming installation of a package, or asking you for information for configuration.
Start the installation by running the first script:
./openstack_base_1.sh
When the script finishes you’ll see instructions for manually configuring your network. You can edit the interfaces file by doing a:
vim /etc/network/interfaces
Copy and paste the network code provided by the script into the file and then edit:
auto eth0 iface eth0 inet static address 192.168.1.48 network 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255 gateway 192.168.1.124 dns-nameservers 8.8.8.8 auto eth1
Change the settings for your network configuration and then restart networking and run the next script:
/etc/init.d/networking restart Then run the second script : ./openstack_base_2.sh
After the second script finishes, you’ll need to set up a logical volume for Nova to use for creating snapshots and volumes. Nova is OpenStack’s compute controller process.
Here’s the output from the format and volume creation process:-
root@manager-System-Product-Name:/openstackgeek# fdisk /dev/sda Device contains neither a valid DOS partition table,nor Sun,SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0xb39fe7af. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) Command (m for help): n Partition type: p primary (0 primary, 0 extended, 4 free) e extended Select (default p): p Partition number (1-4, default 1): 3 First sector (2048-62914559, default 2048): Using default value 2048 Last sector,(2048-62914559,default 62914559): Using default value 62914559 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. root@manager-System-Product-Name:/openstackgeek# pvcreate -ff /dev/sda3 Physical volume "/dev/sda3" successfully created root@manager-System-Product-Name:/openstackgeek# vgcreate nova-volumes /dev/sda3 Volume group "nova-volumes" successfully created
Note: Your device names may vary.
The OpenStack components use MySQL for storing state information. Start the install script for MySQL by entering the following:
./openstack_mysql.sh You’ll be prompted for a password used for each of the components to talk to MySQL: Enter a password to be used for the OpenStack services to talk to MySQL (users nova, glance, keystone): redhat Note(Here “redhat” is the password given to nova,glance,keystone)
During the installation process you will be prompted for a root password for MySQL. In our install example we use the same password, ‘redhat’. At the end of the MySQL install you’ll be prompted for your root password again.
mysql start/running, process 8796 ################################################################################ Creating OpenStack databases and users. Use your database password when prompted. Run './openstack_keystone.sh' when the script exits. ################################################################################ Enter password: After MySQL is running, you should be able to login with any of the OpenStack users and/or the root admin account by doing the following: mysql -u root -predhat mysql -u nova -predhat nova mysql -u keystone -predhat keystone mysql -u glance -predhat glance
Keystone is OpenStack’s identity manager. Start the install of Keystone by doing:
./openstack_keystone.sh
You’ll be prompted for a token, the password you entered for OpenStack’s services, and your email address. The email address is used to populate the user’s information in the database.
Enter a token for the OpenStack services to auth wth keystone: redhattoken
Enter the password you used for the MySQL users (nova, glance, keystone):redhat
Enter the email address for accounts(nova,glance,keystone):user@company.com
You should be able to query Keystone at this point.
You’ll need to source the“stackrc” file before you talk to Keystone:
. ./stackrc
keystone user-list
Keystone should return a list of users:
+----------------------------------+---------+------------------------+--------+
| id | enabled | email | name |
+----------------------------------+---------+------------------------+--------+
| b32b9017fb954eeeacb10bebf14aceb3 | True | user@company.com | demo |
| bfcbaa1425ae4cd2b8ff1ddcf95c907a | True | user@company.com | glance |
| c1ca1604c38443f2856e3818c4ceb4d4 | True | user@company.com | nova |
| dd183fe2daac436682e0550d3c339dde | True | user@company.com | admin |
+----------------------------------+---------+------------------------+--------+
Glance is OpenStack’s image manager. Start the install of Glance by doing:
./openstack_glance.sh
The script will download an Ubuntu 12.04 LTS cloud image from StackGeek’s S3 bucket.Once it’s done, you should be able to get a list of images:
glance index
Here’s the expected output:
ID :- 71b8b5d5-a972-48b3-b940-98a74b85ed6a Name :- Ubuntu 12.04 LTS Disk Format :- qcow2 Container Format:- ovf Size :- 226426880
We’re almost done installing! The last component is the most important one as well. Nova is OpenStack’s compute and network manager. It’s responsible for starting instances, creating snapshots and volumes, and managing the network. Start the Nova install by doing:
./openstack_nova.sh
You’ll immediately be prompted for a few items, including your existing network interface’s IP address, the fixed network address, and the floating pool addresses:
###################################################### The IP address for eth0 is probably 192.168.1.48. Keep in mind you need an eth1 for this to work. ###################################################### Enter the primary ethernet interface IP: 192.168.1.48 Enter the fixed network (eg. 10.0.2.32/27): 192.168.1.0/24 Enter the fixed starting IP (eg. 10.0.2.33): 192.168.1.1 ############################################################################ The floating range can be a subset of your current network. Configure your DHCP server to block out the range before you choose it here. An example would be 10.0.1.224-255 ############################################################################ Enter the floating network (eg. 10.0.1.224/27): Enter the floating netowrk size (eg. 32):
The fixed network is a set of IP addresses which will be local to the compute nodes. Think of these addresses as being held and routed internally inside any of the compute node instances.
The floating network is a pool of addresses which can be assigned to the instances you are running. For example, you could start a web server and map an external IP to it for serving a site on the Internet.
Nova should finish installing after you enter all the network information. When it’s done, you should be able to get a list of images from Glance via Nova:
nova image-list
And get the expected output we saw earlier from Glance:
root@manager-System-Product-Name:/openstackgeek# nova image-list
+--------------------------------------+------------------+--------+--------+
| ID | Name | Status | Server |
+--------------------------------------+------------------+--------+--------+
| 71b8b5d5-a972-48b3-b940-98a74b85ed6a | Ubuntu 12.04 LTS | ACTIVE | |
+--------------------------------------+------------------+--------+--------+
Horizon is the UI and dashboard controller for OpenStack. Install it by doing:
./openstack_horizon.sh When it’s done installing, you’ll be given a URL to access the dashboard. You’ll be able to login with the user ‘admin’ and whatever you entered earlier for your password. If you’ve forgotten it, simply grep for it in your environment: env |grep OS_PASSWORD The URL will be : http://192.168.1.48
You can login the Openstack dashboard by the following credentials
USER : admin
PASSWORD : redhat
Entrusted with a project where we have to implement data protection and privacy guidelines in accordance with international regulations we found ourselves investigating ways to implement data encryption in MSSQL database in Amazon EC2. We are deploying an application which has to deployed in all the AWS availability zones and our problems like syncing between zones are still at large as fine tune MS-SQL for the cloud.
Data security and privacy
The applications which storing sensitive information like customer information, Financial information, personal health information(PHI) etc, will have to meet certain data privacy and security acts. The Health Information Portability and Accountability Act (HIPAA) of 1996 protects health information. To make applications HIPAA compliance we can use some of new security features in SQL server 2008. MSSQL Server 2008 introduce new with security feature enhancements for powerful encryption and better key management capabilities
Data security in cloud
The data in cloud is in a shared hardware environment. Therefore data segregation is one of the major security issue. All cloud providers have their own storage management. But the security and privacy of data is again an issue because the customers don’t have much control over this storage area. They don’t know the exact location where data is stored. Customers can overcome these issues by implementing their own security features based own their application.
We had 2 issues to address:
1. Encrypt data in transit
2. Encrypt data at rest
In this one we are starting by implementing encryption of data in transit for MSSQL server. MSSQL Server uses the Secure Socket Layer(SSL) to encrypt data transfer between SQL server and applications. This encryption will ensure secure data transmission over the network. This is much more important when application and database are distributed on many AWS availability zones.
1.Creating a self-singned cert using makecert
[text]
makecert -r -pe -n “CN=SERVER-FQDN” -b 01/01/2010 -e 01/01/2015 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp “SSL Providerl” -sy 12 c:\testssl.cer
[/text]
2.Install this cert
Copy c:\tesssl.cer into your client machine, run c:\testssl.cer from command window, select “Install Certificate”. -> click “Next” -> select “Place all certificates in the following store” –> click “Browser” -> select “Trusted Root Certification Authorities” -> select OK and Finish
3.Open SQL Server Configuration Manager
Expand SQL Server Network Configuration, right-click “Protocols for MSSQLSERVER” then click “properties”. On the “Certificate” tab select the certificate just installed . On the “Flags” tab, set “ForceEncryption” YES.
Now SSL is ready to use on server. You have modify your connection string to use SSL.
For Example
connectionString=”Data Source=db.server.com;Initial Catalog=mydb;User ID=user1;Password=pas@123;Encrypt=true;TrustServerCertificate=true”
You are Done!
Update: NFS should not be used as that will be a SPOF. One should use S3 or other object stores. An alternative could be multi-node GlusterFS if someone needs volumes shared across nodes.
When building an infrastructure for an eCommerce portal on Cloud, it is important to note that it should be available all the time, that it is fail safe with outages like the one we had recently in AWS EU and U.S. East Regions, survive Hardware failure or any other issues like bug in the system or deployment errors. We built an infrastructure on AWS Cloud that address all these issues with LAMP using various AWS Cloud services like EC2, S3, RDS, EBS etc. It is described in detail below:
Elastic Load Balancer (ELB)
The Elastic Loadbalancer ( ELB ) service provided by AWS tries to achieve the following:
(i) Spans across Datacenters: Loadbalance traffic across mulitple datacenters (AZ )thus providing high availability even if one datacenter goes down. So you should always make sure that when you launch instances under an ELB, you should launch it in different Availability zones. You can also launch instances in the same AZ but by default ELB will redirect request across multiple AZ in a Round Robin way.
(ii) Failover: ELB will periodically monitor the health of the instances and if any of the instance or monitored service ( e.g. Http ) goes down, ELB will stop redirecting requests to that instance and all the request will be redirected to the remaining number of instances registered under ELB. When the instance comes backup, it will again start redirecting requests to that instance.
(iii) Handling root domain ( apex / main domain ) and subdomains: ELB can loadbalance only those requests coming to alias / subdomain( www ). It cannot handle request coming to root domain. This is because when you configure DNS for enabling ELB, you can only set CNAME to ELB for subdomains. There are 2 reasons for this. One is when you configure ELB, you will only get a Public DNS name for the ELB like the following instead of a Public IP.
[bash]Test-1736333854.us-east-1.elb.amazonaws.com [/bash]
This is because AWS changes the Public IP of the ELB periodically for providing scalability for ELB itself. Another reason why you cannot redirect main domain request to ELB is that DNS protocol itself restricts the usage of CNAME or anything other than “A” record for a root domain. So you cannot CNAME root domain to ELB DNS name.
So for serving root domain requests with ELB , there are only work arounds like mentioned below:
a) We have to assign an elastic IP for an instance under ELB. But what if this instance goes down? Set heartbeat to switch EIP? This is a bit complicated setup as switching EIP to instances present across AZ takes time.
b)The other option is to have the root domain point to the IP addresses of the destination by configuring one or more “A” records (address records) for root domain. You can do that if you know the destination IP addresses are fixed, such as if you are using EC2 Elastic IP addresses. We wouldn’t recommend this because IP addresses will be cached at the client end for long time even if you set low value of TTL at the nameservers. This is because TTL value can also be configured at the the client end overriding the TTL value provided by the nameserver of the domain. e.g. with nscd ( Nameserver Caching Daemon) you can set the TTL value manually in its configuration file.
c) You can keep a separate web server not under ELB with a Redirect Rule for redirecting root domain requests to www. You should make sure that this webserver is highly available as well.
d) A better solution is to go for Domain Registrars ( DNS service providers ) who provide this feature of redirecting root domain requests to www. So this can be handled at the DNS itself. The DNS service provided by AWS “Route53” can be used for this ‘Zone apex’ ( root domain ) redirection.
(iv) SSL Termination
There is support for “SSL termination” in ELB which means you can use ELB to loadbalance HTTPS requests too. You just need to buy the SSL certificate and simply upload it to ELB. ELB will redirect all the HTTPS request to the backend servers. So you can make an eCommerce portal highly secure and highly available with ELB.
(v) Persistent Session
You can enable Sticky Session with ELB but the problem is users will be logged out if any of the instance / webserver goes down and ELB will redirect the subsequent requests from the same user to a different instance and it will prompt the user to login again. To tackle this there were few options we had considered –
a)You can either setup distributed failover memcached server or
b)You can use RDS for storing Session.
We went for RDS as our Session Management store since RDS is an excellent choice for Database Administration as well if you are using MySQL as the Database.
Your application must be configured to write session data to an RDS database. So when an instance / webserver goes down and when the ELB redirects the user request to a different instance, the user will not be asked to login again as all servers are reading session data from the same place that is RDS. The user won’t notice anything at all, even though they’ve now started talking to another server. We recommend using a Multi-AZ RDS instance and write session data into this. So if one of your EC2 instances goes down, the other instances will still have access to the RDS database, and likewise if an RDS zone goes down, Amazon fail this over to the second AZ internally, transparently to you and your application.
So the easiest and most reliable way to share sessions for failover on a multi-server environment is to use RDS, since Amazon handle the database layer’s failover for you.
So basically you can achieve two things by using RDS – Session management and Database Management.
The Autoscaling service provided by AWS allows you to scale horizontally up / down with CPU usage, RAM, Disk I/O etc.
Ideally you should use a Base AMI with Autoscaling that will pull the required packages from a Centralized location like Chef Platform and code from the Version Control System or S3. You can write a startup script to run on instance bootup for this purpose. So when Autoscaling launches a new instance it will pull all the latest updated versions of the packages, code and also any other required custom configurations from a centralized location. This will also make it easier to manage all the configuration details, code updates from a centralized location using tools like Chef Platform, Version Control System or S3 respectively.
Apart from Centralised Configuration / Code management, the reason for using Base ami with Autoscaling is that it is not possible to change the ami configured with Autoscaling service dynamically.
We came across lot of options for storing the application files. However you have to consider your priorities before you select a storage service for the code. Following are the points to consider for your application file storage system:
(i)Latency issues: All shared storage systems like NFS / GlusterFS / EBS / S3 etc have latency issues when compared to Instance store (Ephemeral Storage)
(ii)High availability: If you are using a shared storage service like NFS, it should never go down for the entire system to be available all the time.
(iii)Access to the code: How to get the latest code during incremental roll out of a new instance because if you are using a shared storage, it becomes difficult to gives access to the shared storage system when a new instance is launched
We went for instance store / ephemeral store that gives you better I/O performance. You can keep your own highly available SVN repository or go for publicly available Version Control Systems like GitHub. At the same time you can also keep a copy in S3 and sync to it whenever there is a code update. This will make it more redundant.
The problem with using shared storage service like NFS / GlusterFS with EBS / S3 is it becomes difficult to avoid single point failure for NFS / GlusterFS service. But if your site doesn’t have much hits and your priority becomes redundancy, you can go for mounting S3 as filesystem using tools like s3cmd and use that as a shared storage with NFS for multiple instance. The problem with S3 is that it is not intended to be used as a filesystem and there have been issues reported with speed and caching. Or you can use EBS volume for code storage if you have only a single instance serving the request. Even using NFS with EBS volumes ( with frequent snapshots to S3 ) gives better performance than using S3 as shared storage for files.
Not only does instance store gives you better performance, error rates very rare. with EBS volumes error rates are reported frequently. Recent outages with AWS EU & US East Regions shows that the down time was made worse due to increase in time taken to recover from EBS errors.
For automating code deployment, you can configure deployment tools like Capistrano. This will become very handy when you have multiple servers to update simultaneously. Capistrano uses Ruby language and is built for Ruby code deployment but with little changes, you can automate deployment of PHP / Perl / Python / JAVA based application.
chef-deploy is another tool that comes with chef for automating code deployment. Continuous Integration tools like Hudson / Cruise Control are excellent tools when you want to automate the Build, Deployment, Test and Rollback process.
For code deployment, we follow a Release Management process where we keep a staging environment that is an exact replica of the production environment. We push code to the production environment only when it’s been completely tested in the staging environment and approved by the Release Manager. This will further reduce the errors / bugs / and downtime time caused due to the code release.
We went for RDS across AZ for High availability. AWS will take care of Redundancy, Performance Optimisation, Scalability and Backup. You can avoid the hassle of managing a Database Server by using RDS. RDS is as an excellent distributed highly available Session Management System. You can also take regular backup from RDS and keep it in S3.
You can also use Master–Slave Replication setup instead of RDS. This is also a good option for achieving high availability for Database server. The challenging part will be to manually configure failover for both master and slave servers, achieving scalability with traffic, backup configuration and performance optimization with increasing load. With RDS, all these will be managed by AWS.
Keep all the important logs like Application logs, Syslogs, SSH log etc in EBS volume. You can either schedule regular snapshots of these EBS volume to S3 or you can even sync these log files to an S3 bucket periodically using tools like s3sync.
If you have more than one server or are planning to scale up in future or would like to automate a lot of administration / coding stuffs, you should definitely use one of the Open Source freely available Configuration Management tools like Chef / puppet / Cfengine
Chef is new and has default support for AWS / EC2. We use Chef extensively for managing our infrastructure in AWS. Chef provide a lot of readily available cookbooks ( recipes / roles ) for LAMP, JAVA app, Cassandra, Hadoop, Nagios etc which can be used readily ( or with minimum customization ) to automate the infrastructure setup and configuration. Chef also comes with a tool called Chef-deploy for automating deployment of code.
So using Chef along with tools like Hudson / Cruisecontrol, you can automate the entire setup from infrastructure setup to configuration management to building, deployment and testing of your application.
To improve performance you can implement the following:
(i)Use caching mechanisms like Memcache(DB scaling) / aiCache / Varnish.
(ii)CDN ( Content Delivery Network ) is a must if you want to provide better end-user response time. There are lot of CDN providers but we recommend AWS CloudFront or Akamai for serving static files and images. For start-up and small business, CDN might be costly but as your target audience grows larger and becomes more global, a CDN is necessary to achieve fast response times.
For monitoring, go for open source monitoring tools along with a SaaS based monitoring application.
(i)There are lot of free and open source option available in the market – Nagios, Zenoss,Zabbix etc. This can be automated with Chef in such a way that when a new server is launched in to the cluster, it will be automatically added to the Nagios list of monitored servers.
(ii)You can also use excellent SaaS based monitoring apps like Pingdom, mon.itor.us, site24x7.com etc for monitoring and alerting via email, SMS or Twitter.
(iii)Custom scripts or tools like Munin & Monit for monitoring and restarting services if it crashes.
You can keep copies of code in an S3 Bucket and sync it with tools like s3sync with every update. For DB Backup, in addition to automated RDS Backup, you can take periodical standard DB backups using mysqldump and store it in S3 bucket.You can also use EBS volumes for keeping replica of code and DB Backup with periodical snapshots to S3.
An important thing to note about S3 storage is it is only a Highly available Storage System. It is not backed up automatically. That means if you delete anything manually from s3, it will be forever gone unless you have manually backed it up with multiple copies in S3. So make sure that you have enough backups available in S3.
If you are looking forward to migrating your PostgreSQL database to AWS EC2 cloud servers, you can do so by following the simple steps we have posted below. You can make it more reliable and secure from accidental EC2 instance crashing by allowing the postgresql server to run from an EBS volume. You can also take a snapshot of the EBS volume which will be stored on AWS storage service s3 which will make it highly reliable by making it available on multiple AWS availability zones that spans across datacenters. Read more…
Elastic Load Balancing ( ELB ) is an AWS load balancer service that is readily available for users who have signed up for AWS EC2 and s3 services . ELB is configured to automatically distribute incoming application traffic across multiple Amazon EC2 instances . Recently AWS has announced support for ELB to the AWS Management Console which will give users a simple, point-and-click web interface to create and configure load balancers for the AWS EC2 instances .
Below are the simple steps to configure ELB for webserver from the command line . Read more…
"Our client who has multiple offices across the world was finding it difficult to implement a perfect VOIP solutions. We provided solutions that helped in avoiding call drops and transferring calls from geographical office to another".
"We have migrated an application with 15GB PostgreSQL database to the Amazon EC2 cloud"
"We migrated our shared hosting servers with Cpanel and another with webmin to Amazon EC2"
Cloud enablers help data centers and enterprises in moving to cloud computing. While these IaaS softwares help enterprises adopt cloud, they help service providers enter the lucrative and demanding market without hassle.More
