Self-Managed Deployments

You can create a self-managed deployment for an enabled self-managed environment. When using a self-managed deployment, you take full control of procuring the resources needed to run engine instances. You must set up the machines and complete the installation prerequisites required by the StreamSets engine type.

When you create a self-managed deployment, you define the engine type, version, and configuration to deploy. You also select the installation type to use - either a tarball or a Docker image.

After you create and enable a self-managed deployment, Control Hub displays the command that you run to install and launch engine instances on the machines that you have set up.

Using a self-managed deployment is the simplest way to get started with StreamSets. After getting started, you might consider using one of the cloud service provider integrations that StreamSets provides, such as the AWS and GCP environments and deployments. With these integrations, Control Hub automatically provisions the resources needed to run the engine type in your cloud service provider account, and then deploys engine instances to those resources.

Or, you can continue using self-managed deployments when you prefer to run engine instances on on-premises machines or when you want to take full control of these machines. You can increase the number of engine instances for a self-managed deployment by simply running the command on additional machines.

Important: If your pipelines require external resources, you must set up an external resource archive that all engine instances can access before increasing the number of instances.