Manually reactivating the environment
You learn how to reactivate the AWS or Azure environment.
Using the CDP CLI
You parameterize the CLI create-cluster command to activate the cluster, as described in the CLI documentation.
- Activate the cluster by passing the options you retrieved backing up AWS or activating
Azure.To see all options run the following command.
cdp dw create-cluster –help
Examples for shorthand and JSON syntax are available.For example, an Azure CLI activation option looks something like this:An AWS CLI activation option looks something like this:cdp dw create-cluster --environment-crn <crn:cdp:environments:us-west-1:abc:environment:123> \ --use-overlay-network --no-use-private-load-balancer \ --azure-options \ userAssignedManagedIdentity="<full managed identity identifier>",subnetId="<full subnet identifier>",enableSpotInstances=false,logAnalyticsWorkspaceId="<full log analytics workspace identifier>" \ --profile <customer profile>
cdp dw create-cluster --environment-crn <crn:cdp:environments:us-west-1:abc:environment:123> \ --use-overlay-network --use-private-load-balancer \ --aws-options \ lbSubnetIds=<list of subnet identifiers>,workerSubnetIds=<list of subnet identifiers>,enableSpotInstances=false --profile <customer profile>
- (Optional) If you need to preserve the old environment URL, specify the custom
subdomain in the dw create-cluster
command.
--custom-subdomain (string)
For example:--custom-subdomain env-qwertyu.dw
For more information about cluster URLs after reactivation, see “Cluster URLS after reactivation”. For more information about the CLI, see CDP CLI documentation.