Environment Activation Options
Environment activation options provides a platform where you add options mandatory to create an environment on NCache cloud. These options include providing Deployment User for auto deployment of servers and accessing Activation Key for manual deployment of servers.
Deployment User for Deployment Through Portal
A Deployment User is a user who has the rights to deploy resources in NCache cloud subscription. This user should be a part of your Azure/AWS subscription and must have a certain set of roles assigned to it. NCache Cloud Service uses this role-based user's authentication details to fetch and create resources in your NCache cloud subscription.
Important
Providing this user's information is mandatory when deploying servers through NCache Cloud Portal.
- On the Environment Activation Options page, the Creation Through Portal section adds a deployment user to configure and manage the environment created through the NCache Cloud Portal.
Link Azure Deployment User
To link an Azure Deployment User, follow these steps:
Add the name of your deployment user in the Account Name box.
If you do not have a configured deployment user, you can create one on Azure by using the following JSON file in the steps mentioned in the Microsoft's guide Create Azure Custom Roles.
Note
- The
roleName
must be kept asNCache SaaS Permissions
otherwise the user will not be recognized as a deployment user. - Add your subscription ID instead of
{subscriptionid}
placeholder under theassignableScopes
tag.
{
"properties": {
"roleName": "NCache SaaS Permissions",
"description": "Minimum set of permissions required by a deployment user on the NCache SaaS portal.",
"assignableScopes": [
"/subscriptions/{subscriptionid}"
],
"permissions": [
{
"actions": [
"Microsoft.Authorization/roleAssignments/read",
"Microsoft.Compute/virtualMachines/read",
"Microsoft.Compute/virtualMachines/write",
"Microsoft.Compute/virtualMachines/delete",
"Microsoft.Compute/virtualMachines/start/action",
"Microsoft.Compute/virtualMachines/restart/action",
"Microsoft.Compute/virtualMachines/deallocate/action",
"Microsoft.Compute/virtualMachines/instanceView/read",
"Microsoft.Compute/disks/delete",
"Microsoft.Network/networkInterfaces/read",
"Microsoft.Network/networkInterfaces/write",
"Microsoft.Network/networkInterfaces/delete",
"Microsoft.Network/networkInterfaces/join/action",
"Microsoft.Network/networkSecurityGroups/write",
"Microsoft.Network/networkSecurityGroups/delete",
"Microsoft.Network/networkSecurityGroups/join/action",
"Microsoft.Network/publicIpAddresses/read",
"Microsoft.Network/publicIpAddresses/delete",
"Microsoft.Network/publicIpAddresses/write",
"Microsoft.Network/publicIPAddresses/join/action",
"Microsoft.Network/virtualNetworks/read",
"Microsoft.Network/virtualNetworks/subnets/read",
"Microsoft.Network/virtualNetworks/subnets/join/action",
"Microsoft.Resources/subscriptions/read",
"Microsoft.Resources/subscriptions/locations/read",
"Microsoft.Resources/subscriptions/resourceGroups/read"
],
"notActions": [],
"dataActions": [],
"notDataActions": []
}
]
}
}
- Clink on the Link Azure Deployment User button to link your Azure deployment user and grant NCache the requested permissions.
Link AWS Deployment User
To link a deployment user for an AWS subscription, follow these steps:
Add a name of your deployment user (in this case, your AWS IAM user) in the Account Name textbox.
If you do not have a configured IAM user for AWS, you can create one by using the following JSON file in the steps mentioned in the AWS Create IAM User Role.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ec2Access",
"Effect": "Allow",
"Action": [
"ec2:DescribeInternetGateways",
"ec2:DescribeNetworkAcls",
"ec2:DescribeVpcs",
"ec2:DescribeSubnets",
"ec2:DescribeTags",
"ec2:DescribeSecurityGroups",
"ec2:DescribeNetworkInterfaces",
"ec2:DescribeRouteTables",
"ec2:CreateRoute",
"ec2:DeleteRoute",
"ec2:DetachInternetGateway",
"ec2:CreateTags",
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:DeleteKeyPair",
"ec2:AttachInternetGateway",
"ec2:CreateKeyPair",
"ec2:RunInstances",
"ec2:DescribeInstanceStatus",
"ec2:DescribeInstances",
"ec2:TerminateInstances",
"ec2:StopInstances",
"ec2:StartInstances",
"ec2:RebootInstances",
"ec2:DescribeImages"
],
"Resource": "*"
},
{
"Sid": "iamAccess",
"Effect": "Allow",
"Action": [
"iam:GetUser",
"iam:ListAttachedUserPolicies",
"iam:GetPolicy",
"iam:GetPolicyVersion",
"iam:ListEntitiesForPolicy",
"iam:ListPolicies",
"iam:SimulatePrincipalPolicy"
],
"Resource": "*"
}
]
}
Enter the account's access key in the IAM Access Key textbox.
Enter your account's secret key in the IAM Secret Key textbox.
Click on the Link AWS Deployment User button to link the provided AWS IAM user as a deployment user for deployment of servers through NCache Cloud Portal.
Activation Key for Manual Deployment
In case you do not want to register a role-based user with the NCache Cloud Server to prevent sharing any sensitive information, NCache allows you to manually create and deploy machines through the cloud portal of your choice.
The machines that are manually created and deployed in NCache Cloud environment do not have NCache activated on them. You will need an activation key to manually activate NCache in all of these machines. The Manual Creation section of Environment Creation Options provides you with this activation key.
Refer to Manual Activation and Manual Deactivation to know how to use this activation key to activate and deactivate your cloud machine.
You can regenerate this key by clicking the Regenerate button.
Note
- In case you regenerate the activation key, all those machines that were activated with the previous activation key will not be deactivated. The new key will only have effect on the machines to be activated.
- If you regenerate the activation key, you will have to manually reactivate all those machines whose license has expired with the new activation key.
See Also
Create New Environment
Edit Environment
Manual Activation
Manual Deactivation