Provisioning Source Cluster for Testing - opensearch-project/opensearch-migrations GitHub Wiki

This guide walks you through the steps to provision an Elasticsearch cluster on EC2 using AWS CDK. The CDK that provisions this cluster can be found on the migration-es branch of the opensearch-cluster-cdk GitHub forked repository.

TODO ^ lewijacn seems like it should be updated?

git clone https://github.com/lewijacn/opensearch-cluster-cdk.git
cd opensearch-cluster-cdk
git checkout migration-es

npm install

Configure the desired AWS credentials ↗ for the environment, as these will dictate the region and account used for deployment.

The configuration below sets up a single-node Elasticsearch 7.10.2 cluster on EC2 and a VPC to host the cluster. Alternatively, you can specify an existing VPC by providing the vpcId parameter. The setup includes an internal load balancer, which should be used when interacting with the cluster.

Copy and paste the following configuration into a cdk.context.json file at the root of the repository. Replace the <STAGE> placeholders with the desired deployment stage, e.g., dev.

{
  "source-single-node-ec2": {
    "suffix": "ec2-source-<STAGE>",
    "networkStackSuffix": "ec2-source-<STAGE>",
    "distVersion": "7.10.2",
    "cidr": "12.0.0.0/16",
    "distributionUrl": "https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-7.10.2-linux-x86_64.tar.gz",
    "captureProxyEnabled": false,
    "securityDisabled": true,
    "minDistribution": false,
    "cpuArch": "x64",
    "isInternal": true,
    "singleNodeCluster": true,
    "networkAvailabilityZones": 2,
    "dataNodeCount": 1,
    "managerNodeCount": 0,
    "serverAccessType": "ipv4",
    "restrictServerAccessTo": "0.0.0.0/0"
  }
}

Note: You can specify other versions of Elasticsearch or OpenSearch by modifying the distributionUrl parameter.

If this is the first time you're deploying CDK in the region, you'll need to run the following command. Note: This only needs to be done once per region.

cdk bootstrap --c contextId=source-single-node-ec2 --c contextFile=cdk.context.json

Deploy the infrastructure using the following command:

cdk deploy "*" --c contextId=source-single-node-ec2 --c contextFile=cdk.context.json

Once the deployment is complete, the CDK will output the internal load balancer endpoint, which can be used within the VPC to interact with the Elasticsearch cluster:

# Stack output
opensearch-infra-stack-ec2-source-dev.loadbalancerurl = opense-clust-owiejfo2345-sdfljsd.elb.us-east-1.amazonaws.com

# Example curl command within the VPC
curl http://opense-clust-owiejfo2345-sdfljsd.elb.us-east-1.amazonaws.com:9200

When you are done using the provisioned source cluster, you can delete the resources by running the following command:

cdk destroy "*" --c contextId=source-single-node-ec2 --c contextFile=cdk.context.json

For a full list of options, refer to the CDK options in the repository documentation.

^ TODO: Are we advertising a fork? Seems like this should be fixed up