The following tutorial covers importing any existing Elastigroup/s running an ECS cluster to Ocean.
If your cluster has only one Elastigroup, refer to Use Case 1.
To import a cluster that consists of multiple Elastigroups, refer to Use Case 2.
In case you have one Elastigroup for your ECS cluster, simply click the “Upgrade to Ocean” button at the top-right of the EG.
In case you have multiple Elastigroups for the same ECS cluster, you will need to follow the below instructions:
- Ocean manages the entirety of the ECS cluster’s container-instances. If the instances are distributed across multiple Elastigroups, all of these Elastigroups should be migrated at once.
To complete this tutorial, gather the following information:
- List the Elastigroups connected with the target ECS Cluster.
- For each of the Elastigroups, save the following data for future use:
- Autoscaler Custom Attributes.
- User-data scripts.
- AMI ID.
Step 1: Create the Ocean Cluster
- Choose one of your ECS Elastigroups and click the “Upgrade to Ocean” button on the top right corner. This will be your source Elastigroup and Ocean will take control over its management.
Step 2: Configure Ocean Custom Launch Specifications
The next step is to configure the Ocean cluster to handle all the different attribute sets configured on the current Elastigroups.
- Navigate to the Ocean cluster you created in step 2.
- Click on the Actions menu and select Launch Specifications.
- For each of the Elastigroups running container instances:
- Click “Add Launch Specification”.
- Add the Attribute sets gathered as part of the prerequisites.
- Set the matching User-Data and AMI.
- Click Update to commit changes.
Step 3: Disable Autoscaling On The Imported Elastigroups
Disable the autoscaling in the Elastigroups that were converted to Launch Specifications to allow Ocean to take over.
- For each of the groups, perform the following steps:
- Navigate to the Elastigroup.
- Under the Actions menu, click Edit Configuration.
- Scroll down to the Advanced section.
- Remove the Autoscaler selection.
- Continue to the review page and click Update to commit the changes.
Step 4: Downscale secondary Elastigroups converted to Launch Specifications
The last step is to downscale the container instances in any secondary Elastigroups (not the source Elastigroup which was used in step 2) and allow Ocean to launch the proper instances to fit the cluster needs.
- Navigate to the Elastigroups configured for your ECS cluster that were converted to matching Launch Specifications (other than the main one).
- On the Actions menu, Click Manage Capacity.
- Reduce the target capacity.
- Note: It is highly recommended to reduce the target capacity in batches of 10-20% and repeat this step until complete downscale.
- Navigate to your Ocean Cluster and verify that it is spinning up the required resources and handles the cluster tasks.
Step 5: Sit back and relax, Ocean got you covered!
In case of any issues please contact our support engineers via chat or email.