This table list the available flavours for Microsoft Azure.
|Flavour name||Flavour code||Service|
|HTTP/HTTPS ModProxy||Switch on the instance if an HTTP/S request is received|
|Metrics||Switch off the instance if the CPU is low|
|Schedule||Switch on or off the instance following a predefined schedule|
|SSH||Enable SSH connection (eg: git)|
Supported stop status
An instance can be disposed as described in the table below.
||The Virtual Machine instance state is
||Only instance storage is billed.|
Microsoft Azure authentication requires you to create an Azure AD application and service principal, granted with the builtin CONTRIBUTOR role.
The following informations are required to configure the CloudProvider:
- Application ID
- Application Secret
- Domain/Tenant ID
- Subscription ID
The application must be granted with the following roles
How to create an application for Hakuna Cloud
Step 1 - create an application
The CLI provides a step-by-step procedure to create a CLoudProvider credential set.
- Open a shell and execute the command
hakuna provider create
- Sign in to your Azure Account through the Azure portal.
- Select Azure Active Directory.
- Select App registrations (Preview), then new regstration and configure a new app with the following parameters:
- Take note of the Application ID and Directory (tenat) ID and paste these values in the
- Select Certificates & secrets, then generate a new Client Secret. Add any meaningfull description
Assign the application to a role
To access resources in your subscription, you must assign the application to a role. We suggest to set the role at the subscription level.
- Select All services and Subscriptions, and select the subscription for which you want to authorize Hakuna Cloud. Take note of the Subscription ID
- Select Access Control (IAM), then Add and grant Hakuna Cloud these roles:
Virtual Machine Contributorand
Assign access to:
Azure AD, user, group or application
Select: search for the application