This page describes how to add public cloud credentials and configure enterprise properties for cloud tenants.
For details of how to create and modify tenants, see Manage enterprises.
For details of how to set limits and resource access in Allowed datacenters and public cloud regions, see Configure an enterprise in a cloud location.
Add public cloud credentials for a tenant
To work with public cloud regions or obtain billing data, an enterprise can have one public cloud account or subscription per cloud provider. All the users in the tenant will work with this same account. No other enterprises can share the same account or subscription.
This section describes how to add public cloud credentials to a standard enterprise. These instructions are for users with permissions to manage enterprises.
For instructions for tenant administrators to add credentials to their own enterprises,
see Add credentials for public cloud
Privileges: Manage provider credentials, Manage enterprises, Allow user to switch enterprises, Access Users view
Before you begin:
Obtain credentials to access the cloud provider's API. For Abiquo's basic guides, see Obtain public cloud credentials. Always check your provider documentation too.
To add public cloud credentials:
Go to Users view and edit an enterprise
Go to Credentials → Public
Select the Provider. There may be a separate provider for regions requiring different credentials
To add credentials for compute with optional billing and pricing:
Enter the Access key ID:
For AWS, enter the Access key ID
For Azure standard accounts and CSP customers, the format is
subscription-id#app-id#tenant-id
For GCP the format is
project_id#client_id#client_email#private_key_id
For OCI the format is
tenancy#user#fingerprint
For the Secret access key:
For AWS, enter the Secret access key
For Azure, enter the password for the application.
For GCP, enter the private key in the correct format
For OCI enter the private key in PEM format.
Optionally, for Amazon, GCP, or OCI billing, select Also use for pricing.
For Azure, to add billing credentials, go to Pricing.
See Add public cloud pricing credentials for a tenant
To add credentials for billing only:
For a standard AWS customer account, do the steps at Add a customer AWS account for billing only
For a customer of an Azure CSP or an Amazon organization do these steps.
Enter the Access key ID as follows:
For Azure, the format is
subscription-id##tenant-id
For Amazon, the format is
account-id
For the Secret access key, enter a random string
Click Add account. Abiquo will validate your credentials with the cloud provider and save them
Finish editing the enterprise and click Save
The platform will add the cloud provider account for the enterprise, which will also require access to a public cloud region.
If you have a reseller account (Azure CSP, AWS organization), you can automatically create tenant accounts and add them to enterprises in the platform. See Create an account in public cloud for the customer of a reseller.
Create a user to access the cloud provider portal
Add enterprise properties to store tenant details and metadata
Inject enterprise properties as VM variables
Configure Azure VPNs
To create a VPN in Abiquo between a private cloud virtual datacenter and Azure, you will need the following Azure ARM configuration for the enterprise:
A Gateway Subnet in the Virtual Network that represents the VPC
A Virtual Network Gateway (VNG) using this Gateway Subnet - if this does not exist, Abiquo will try to create it in the virtual network with the supplied netmask
A Local Network Gateway (LNG) that will represent the remote VPN site, which is not managed by Azure ARM
A Virtual Network Gateway Connection that relates the VNG to the LNG
All address spaces from the Virtual Network will be exposed through the Virtual Network Gateway.
To create the Azure VPN configuration, edit each enterprise that will use Azure VPNs and set the following Properties.
Name | Description |
---|---|
azurecompute-arm.vpn.virtualnetworkgateway.type | Type of routing to use by the Virtual Network Gateway. |
azurecompute-arm.vpn.gatewaysubnet.mask | The Virtual Network Gateway requires a 'gateway subnet'. |
azurecompute-arm.vpn.virtualnetworkgateway.sku.name | Name of the Virtual Network Gateway SKU. |
abiquo.
" prefix, for example, abiquo.azurecompute-arm.vpn.gatewaysubnet.mask
.