Manual:CHR AWS installation: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
* Click on EC2 (Virtual Servers in the Cloud) | * Click on EC2 (Virtual Servers in the Cloud) | ||
* Select 'Launch Instance' | * Select 'Launch Instance' | ||
* Go to '[https://aws.amazon.com/marketplace | * Go to '[https://aws.amazon.com/marketplace AWS Marketplace]' | ||
* Search for 'RouterOS' | * Search for 'RouterOS' | ||
* Select and launch it | * Select and launch it | ||
Revision as of 14:59, 20 July 2016
Launching CHR on Amazon Web Services (AWS)
The simplest way to launch your own CHR on AWS:
- Login into your Amazon Web Services account
- Click on EC2 (Virtual Servers in the Cloud)
- Select 'Launch Instance'
- Go to 'AWS Marketplace'
- Search for 'RouterOS'
- Select and launch it
Creating your own CHR image
Warning: Following instructions are necessary ONLY if you want to make your own CHR image. Ready to use CHR image is available from Amazon Marketplace (see above)
Tools required
To get CHR RouterOS running on Amazon AWS cloud at this moment, there are certain steps that you have to do to get this working from scratch.
- Virtual management software that works with ISOLINUX booter/installer on CHR image (KVM, VirtualBox or VMWare Workstation, VMWare Fusion, Hyper-V these tools are interchangeable);
- Tool to resize the image file prior the installation as default image is 64MB of size and in some cases, more storage is required (qemu-img, VMWare built-in tool, VirtualBox external tool);
- AWS API tools installed and configured (ec2-*).
Installation steps (long version)
- Resize the image before installing the RouterOS. Amazon AWS minimal image size is 1GB. After RouterOS is installed it will be much harder to change the available size, the following command will increase the image size to 940MB
qemu-img resize chr-6.34rc21.img +870M
- Import the image as a volume on your AWS. As a return you will get the volume ID
ec2-import-volume chr-6.34rc21.img -f raw -s 1 -b <bucket> -o <AKIAEXAMPLELALALA> -w <SECRETACCESSKEY > -z eu-west-1a
The import may take a while, it is possible to follow the progress:
ec2-describe-conversion-task <task id>
- Create a snapshot. Correct volume ID will be availabe when the previous command ends or from your AWS account
ec2-create-snapshot vol-e3c74810
- Register AWS image as an AMI
ec2-register -n CHR -s snap-a664a48e -d "6.34rc21" -a x86_64 --virtualization-type hvm
- Now you can launch the instance from your AMI.
Note: Since 6.35rc42 extra step of installation on itself is not required