Amazon Linux Support
Even though CPanel is currently working at providing an official AMI at the Amazon marketplace i'd like CPanel to also support Amazon Linux which is a RHEL alike system.
The reasons for it are:
- Market place images tend to lag behind instance family support.
Currently the official CentOS image can't be used in recent C3 instances which provide better performance for the same cost (more than twice the performance per dollar).
I've been following the CentOS bugtrack issue and from what I've understood Amazon has some internal procedures which delay this offering.
This is common among all marketplace offering
- Marketplace images root device can't be mounted on other instances as a non-root device
This is due to a protection marketplace issues to software sellers to protect their code base from being used in other instances without fees being paid.
However this is a huge issue when recovering a system from failure as amazon provides no other means to have remote accessibility to a root device.
- Amazon Linux has more recent kernels which provide better performance and support inside the amazon ecosystem than CentOS;
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
At this time we have no current plans to support additional operating systems. Even though Amazon Linux is based upon RHEL, an operating system that we presently support, there are more than just the initial integration considerations to make. Ongoing maintenance to maintain continuous support is usually the more significant factor for something like this.
There will need to be *significant* demand for this operating system before it can even be considered for potential inclusion. The implications of supporting another OS, even if a RHEL variant, are potentially significant and ongoing.Please continue to discuss and provide feedback for this feature request.
At this time we have no current plans to support additional operating systems. Even though Amazon Linux is based upon RHEL, an operating system that we presently support, there are more than just the initial integration considerations to make. Ongoing maintenance to maintain continuous support is usually the more significant factor for something like this.
There will need to be *significant* demand for this operating system before it can even be considered for potential inclusion. The implications of supporting another OS, even if a RHEL variant, are potentially significant and ongoing.Please continue to discuss and provide feedback for this feature request.
At this time we have no current plans to support additional operating systems. Even though Amazon Linux is based upon RHEL, an operating system that we presently support, there are more than just the initial integration considerations to make. Ongoing maintenance to maintain continuous support is usually the more significant factor for something like this.
There will need to be *significant* demand for this operating system before it can even be considered for potential inclusion. The implications of supporting another OS, even if a RHEL variant, are potentially significant and ongoing.Please continue to discuss and provide feedback for this feature request.
At this time we have no current plans to support additional operating systems. Even though Amazon Linux is based upon RHEL, an operating system that we presently support, there are more than just the initial integration considerations to make. Ongoing maintenance to maintain continuous support is usually the more significant factor for something like this.
There will need to be *significant* demand for this operating system before it can even be considered for potential inclusion. The implications of supporting another OS, even if a RHEL variant, are potentially significant and ongoing.Please continue to discuss and provide feedback for this feature request.
Great news!
I run several machines on AWS and would never go back to running my own hardware again. Being able to run on the mainstream Amazon AMI's would be a plus overall. So far I've only used CentOS for my cPanel instances. But migration to new instances is a big hurdle. This is because there is a major caveat that comes with instances launched from the AWS Marketplace: the attached EBS volumes are restricted to the instance on which they were launched using a marketplace code, meaning that you cannot move the instance’s root volume to another virtual machine, even if it is a volume created from a snapshot this code will block the upgrade.
So this prevents me from doing a quick upgrade on the machine when using the Marketplace CentOS AMI's.
This technique is usually in place with purchased software/AMI's, so it riddles me why CentOS did this.
If there is anything else you want feedback on, let me know... I'll keep an eye on this thread.
Great news!
I run several machines on AWS and would never go back to running my own hardware again. Being able to run on the mainstream Amazon AMI's would be a plus overall. So far I've only used CentOS for my cPanel instances. But migration to new instances is a big hurdle. This is because there is a major caveat that comes with instances launched from the AWS Marketplace: the attached EBS volumes are restricted to the instance on which they were launched using a marketplace code, meaning that you cannot move the instance’s root volume to another virtual machine, even if it is a volume created from a snapshot this code will block the upgrade.
So this prevents me from doing a quick upgrade on the machine when using the Marketplace CentOS AMI's.
This technique is usually in place with purchased software/AMI's, so it riddles me why CentOS did this.
If there is anything else you want feedback on, let me know... I'll keep an eye on this thread.
Cool! Nice going! Any timeline on a beta installer maybe?
I'm going to install a new t2 (HVM version) with cPanel next week. I could try the Amazon AMI instead of Centos.
Cool! Nice going! Any timeline on a beta installer maybe?
I'm going to install a new t2 (HVM version) with cPanel next week. I could try the Amazon AMI instead of Centos.
Great news, as soon as you have it ready for testing just say. I'm waiting to try out cpanel with multiple php versions and if this is available by then will be 2 in 1.
Great news, as soon as you have it ready for testing just say. I'm waiting to try out cpanel with multiple php versions and if this is available by then will be 2 in 1.
Is there any kind of rough ETA on this?
Is there any kind of rough ETA on this?
Hi Eric,
I am unable to find the Official cPanel images. I searched for "cPanel" and for the specific AMI ID.
Do I need to install a regular Amazon Linux AMI and run the cPanel installer?
Also, I noticed the cPanel System requirements page is updated. Is Amazon Linux the new standard as new installations on CentOS etc. are not supported anymore?
Hi Eric,
I am unable to find the Official cPanel images. I searched for "cPanel" and for the specific AMI ID.
Do I need to install a regular Amazon Linux AMI and run the cPanel installer?
Also, I noticed the cPanel System requirements page is updated. Is Amazon Linux the new standard as new installations on CentOS etc. are not supported anymore?
Here is some feedback after setting up a server with the mentioned AMI:
- the AMI mentioned by Eric is only available in US East region. It would be nice to have trustworthy AMI's in other regions too.
- the AMI has default IP settings which are not changeable during the setupwizard. It would be best if the AMI was a ready/clean to install
- you have to reset the root password, however Amazon Linux is a sudo based system. It would be nice if (eventually) cPanel could move away from the "root" login for the WHM interface.
- The timezone settings are pre-set, don't forget to adjust them to you own preference.
I'm currently transferring a single account to test a running environment. I don't expect any problems there.
Here is some feedback after setting up a server with the mentioned AMI:
- the AMI mentioned by Eric is only available in US East region. It would be nice to have trustworthy AMI's in other regions too.
- the AMI has default IP settings which are not changeable during the setupwizard. It would be best if the AMI was a ready/clean to install
- you have to reset the root password, however Amazon Linux is a sudo based system. It would be nice if (eventually) cPanel could move away from the "root" login for the WHM interface.
- The timezone settings are pre-set, don't forget to adjust them to you own preference.
I'm currently transferring a single account to test a running environment. I don't expect any problems there.
thank you eric
thank you eric
Hi Eric,
I still can't find your AMI anywhere.
I went to Community AMIs, checked the checkbox Amazon Linux and searched for "cpanel".
I use the EU Ireland region.
How can I find your AMI?
Thanks!
Hi Eric,
I still can't find your AMI anywhere.
I went to Community AMIs, checked the checkbox Amazon Linux and searched for "cpanel".
I use the EU Ireland region.
How can I find your AMI?
Thanks!
Do not check Amazon Linux in your search. The AMI is not supplied under the official Amazon Linux flag. Instead search for "Official cPanel"
Do not check Amazon Linux in your search. The AMI is not supplied under the official Amazon Linux flag. Instead search for "Official cPanel"
I have the "Office cPanel" up and running in a VPC but I am stuck at the WHM login... I can't seem to determine the default login credentials for a new AMI. I can ssh into the instance, but I can seem to determine who to log into the AMI after a first boot... Any advice is appreciated...
I have the "Office cPanel" up and running in a VPC but I am stuck at the WHM login... I can't seem to determine the default login credentials for a new AMI. I can ssh into the instance, but I can seem to determine who to log into the AMI after a first boot... Any advice is appreciated...
Yeah, I was tired last night. For everyone who spins up the AMI on AWS (awesome by the way) remember that by default the root user is disabled and logging in thru the WHM UI requires you to edit the sshd.config file to allow root login with password - bypassing the requirement to login with a .pem key.
Steps:
1) SSH into your new EC2 instance the normal way (ssh -i <.pem> ec2-user@ipaddress)
2) vi /etc/sshd.config (remove # in front of AllowRootLogin and AllowPassword)
3) save - restart ssh (service sshd restart)
How you should be able to log into the WHM UI Via port :2087
Hope this helps. It's basic AWS knowledge, but very critical to get the AMI to work for you.
Yeah, I was tired last night. For everyone who spins up the AMI on AWS (awesome by the way) remember that by default the root user is disabled and logging in thru the WHM UI requires you to edit the sshd.config file to allow root login with password - bypassing the requirement to login with a .pem key.
Steps:
1) SSH into your new EC2 instance the normal way (ssh -i <.pem> ec2-user@ipaddress)
2) vi /etc/sshd.config (remove # in front of AllowRootLogin and AllowPassword)
3) save - restart ssh (service sshd restart)
How you should be able to log into the WHM UI Via port :2087
Hope this helps. It's basic AWS knowledge, but very critical to get the AMI to work for you.
Strange, w edisable root login and password login to ssh. Cloud it just be that your root password had expired ?
Strange, w edisable root login and password login to ssh. Cloud it just be that your root password had expired ?
Replies have been locked on this page!