Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 4.7

Skip to end of metadata
Go to start of metadata

This page describes how to create and launch a VM in Amazon using Abiquo

Author: Eduardo Fernandez

Requirements:

  • Access key ID & Secret access key
    • To obtain these, go to AWS, create an IAM user, add the user to a group, get the Access key ID & Secret access key. For more details, see Obtain AWS credentials

Step by step in Abiquo:

  1. Edit the Abiquo user that is going to deploy the VM to add their SSH public key. (If this is your user, put your current password on the first tab of "Edit user")
  2. Create a public cloud region (PCR) and select the provider (Amazon) and the regions that would you like to use
  3. Create a virtual datacenter, and select the previously created PCR as location
  4. Add a public IP to the virtual datacenter.
  5. Add an inbound firewall rule to the virtual datacenter to allow the SSH protocol from the desired IP (or 0.0.0.0/0 if you don't know it, but be aware of the security implications) 
  6. Create a virtual appliance
  7. Go to the Apps Library, click the import template button, and enter a name text (ubuntu, linux, aws, etc.) to speed up the search, click the search button and wait. Select a template and import it.
    • You can also find the AMI IDs of some common templates from the selection shown in the Amazon EC2 quick launch wizard 
  8. Go to the virtual datacenter and double click or drag and drop the template to create a VM, but don't deploy it.
  9. Edit the VM, on the Network tab add a private IP from the Amazon public subnet (example: subnet-0ba440367e208713c) and a public IP to the VM. 
  10. If you are not using the default firewall policy, go to Firewall and select the appropriate policy. 
  11. Save the VM.
  12. Deploy the VM.

    *In case of an error deploying the VM, check the error message and if it's something like "Virtualization type 'XXX' is required for instances of type XXX ..." try another hardware profile, usually a higher one, that can make use of the Virtualization version of the Region selected. 

To connect by SSH to the VM use the Amazon default instance user:


OS/Distro

Official AMI
ssh Username

Legacy / Community / Other AMI
ssh Usernames

Amazon Linuxec2-user
Ubuntuubunturoot
Debianadminroot
RHEL 6.4 and laterec2-user
RHEL 6.3 and earlierroot
Fedorafedoraec2-user, root
Centoscentosroot
SUSEec2-userroot
BitNamibitnami
TurnKeyroot
NanoStackubuntu
FreeBSDec2-user
OmniOSroot

If you cannot connect due to an unsecured certificate error, open a new tab in the same browser, enter the host IP of the VM, and accept the certificate.

  • No labels