Some AWS regions are disabled by default, and we refer to them as non-default AWS regions. To onboard accounts from non-default AWS regions, do these steps.
Log in to the Remote Services server and edit the abiquo.properties file, to add the following property:
Code Block abiquo.amazon.create.account.mock=trueLog in to Abiquo as an administrator and set up the environment. Create one or more PCRs including the non-default region, for example, Bahrain. Create an empty enterprise and optionally enable the PCRs (later you will need to add them again)
Create a new account in AWS using the reseller credentials
Check that the credentials are correctly added to the new enterprise
Go to the enterprise with the new credentials and create a user
Using the portal link and the new generated user credentials, access the AWS portal. You could also access the new generated account using the switch role functionality on AWS console, using a user belonging to the root account
Go to MyAccount→ Enable the nondefault region, e.g. Bahrain region
Make sure the region is 100% enabled. It takes a few minutes for AWS to enable the region. You can check it on the AWS console, by trying to access the region in EC2.
Once the region is enabled in AWS, go back to Abiquo, and disable the region in the new enterprise.
Save the enterprise, then edit the enterprise again to allow the Bahrain region, to synch all hardware profiles and availability zones.
Once you have added the non-default region (e.g. Bahrain region), all entities will be correctly synchronized and ready to use. You can now create a VDC, deploy VMs, import templates, and so on.