Firewall Load balanced LAMP (Linux, Apache, PHP/Perl/Python) cloud server based on CentOS 5.x, the most popular Linux distribution for web servers, with a dedicated firewall appliance.
The cloud server has a Firewall appliance customers can manage via a GUI, two Apache web servers load balanced by a High Availability Load balancer, a MySQL server component and a shared NAS storage component, allowing for rapid elastic scalability of compute and storage resources.
Internal networking is managed through a PS8 virtual switch, and a set of gateways (one IN and one OUT).
Features and Benefits
- Highly secure: a dedicated firewall appliance, configurable via a GUI, protects the application
- High Availability: The cloud server load balances between two identical Web servers
- Highly scalable: Multiple independent components allow for rapid application scaling
- Easy to use: includes a web management interface via the Cloud Control Panel
- Lightweight: built from the ground up with the minimum required components
- Runs everywhere: Compatible with all version of AppLogic from 2.4.10 to 2.9.9
- 100% open source: free from pricey and restrictive proprietary licensing
Usage
This Firewall Load Balanced LAMP Cloud server has been optimized for use as a general purpose web application platform, with the added security of a dedicated firewall appliance that customers can access and manage via a graphical user interface.
The server is delivered with preconfigured SSH and FTP access from the Internet. After buying this template, customer needs to create passwords for following users: root, webmaster and admin. Root is used for accessing ssh, webmaster is used for FTP access, and admin is used for firewall. It is necessary to configure first those parameters, through Dashboard -> Settings.
Since there are 2 WEB servers, customers can access and manage their first web server component through port 4101, (e.g. "ssh -p 4101 -l root IP"), and second one using port 4102 (e.g. "ssh -p 4102 -l root IP"). Apache default Document root is /mnt/fs/webdir/default_site.
Customers can access MySQL component via port 4201 (e.g. "ssh -p 4201 -l root IP"). Mysql server can be accessed with command "mysql", and after that user regular mysql commands (e.g. "create database", "show databases", "use database", etc).
An FTP server based on the extremely fast, stable and secure proftpd is configured for passive FTP transfers on port 21. Web files should be transfered via FTP to directory "default_site".
Customer can access and manage their firewall appliance via a web browser on port 9000 (e.g. http://217.26.122.211:9000) using username "admin" and password which he have chosen on Settings page. There is already pre-defined rule (number 1) for destination port 6201 which is actually root access to mysql server, IT SHOULD NOT BE REMOVED!
Default Resources
| Resource | Minimum | Maximum | Default |
| Memory | 512M | 12.5G | 960M |
| CPU | 0.45 | 30 | 0.9 |
| Bandwidth | 6M | 9G | 60M |
Application Components
| Component | Description |
| main.INSSL | Firewall appliance with graphical user interface for configuration and management |
| main.dbase | MySQL database server component |
| main.net | OUT gateway, forwards all traffic from the application to the outside world |
| main.PS8 | Virtual switch connecting the three server components to the IN gateway |
| main.srv1 | First Apache web server component |
| main.srv2 | Second Apache web server component |
| main.content | NAS storage component |
Components visible to end users
| Component | Visible Volumes | Filesystem | Mounted On |
| MySQL Database | boot usr mysql |
/dev/hda1 /dev/hda2 /dev/hda3 |
/ /usr /mnt/data |
| Web server1 | boot usr fs |
/dev/hda1 /dev/hda2 fs:/mnt/data |
/ /usr /mnt/fs |
| Web server2 | boot usr fs |
/dev/hda1 /dev/hda2 fs:/mnt/data |
/ /usr /mnt/fs |
| Web Content | fs |
Technical Specifications