"Magento + Memcached + LAMP + Webmin" Package Powered by SAIN3 (HVM)

User Guide


**Important Info**

Before you start to access the system, please make sure the "Status Checks" of the instance in AWS Console turns to "2/2 checks passed", or the initialization process might be interrupted and fails. It takes about 5-10 mins.


**Default Settings**

1.Webmin / MySQL:

Username: root

Password: <instance ID>

2. Magento:

Username: admin

Password: <instance ID>


** Step 1 : Initial Configuration **

1.Visit http:// <public DNS>.

2.Enter your instance ID and click “Continue”.

3.(Required field) Enter the backup path(Format:/mnt/). 

4.(Optional) Enter your website domain name. Format: product.sain3.com or www.example.com. The default domain name is <public DNS>.

5.(Optional) Enter your password for the "admin" user of Magento.

6.Click “Submit” to save your initial configuration.


** Step 2 : Access the System**

1. Visit your Magento frontend.

http:// <public DNS>

2. Admin interface.

http:// <public DNS>/admin

Username: admin, password: <instance ID> or the one you chose.

3. Webmin is at http:// <public DNS>:10000. You can manage MySQL through Webmin.


**Clear Cache & Session*


If you are using a small instance type like t2.micro, we highly recommend you to frequently clear the cache as small instances have insufficient resources. Low performance instances may lead to a webmin crash or a mysql crash or a Cannot Allocate Memory error. So we recommend t2.medium and the higher performance instance types.


2. Login to your magento admin panel and clear cache & session.

We highly recommend using Flush Cache Storage button if you do not configure memcached for other applications except magento.

Originally, this package uses memcached for only magento caching so that you can safely use Flush Cache Storage button to fully clear the cache.


3. There is another way to clear cache & session. Open a terminal or SSH client, using your Amazon EC2 SSH public key, SSH into the instance as the ubuntu user using the public DNS information for your instance.

Type the following commands:

$ telnet localhost 11211     #First command.

flush_all    # This is the second command, then you can see OK.

quit    #Leave telnet


** Cannot Access to Webmin**

1. After the "Status Checks" of the instance in AWS Console turns to "2/2 checks passed" can you start to access the system, or the initialization process might be interrupted and fails.

2.Make sure port 10000 is in your security group.

Type: Custom TCP Rule

Protocol: TCP

Port range: 10000



Replace the <public DNS> above with the actual ip address of the running EC2 instance.