Deployments Overview
A deployment is a group of identical engine instances deployed within an environment. A deployment defines the StreamSets engine type, version, and configuration to use. You can deploy and launch multiple instances of the configured engine.
When you create a deployment, you select an enabled environment for that deployment. You must create and enable environments before creating deployments.
A deployment allows you to manage all deployed engine instances with a single configuration change. You can update a deployment to install an additional stage library on the engine or to customize engine configuration properties. After a deployment update, you instruct Control Hub to restart all engine instances in the deployment to replicate the changes to each instance.
You can create the following types of deployments:
- Self-managed
- When you create a deployment for a self-managed environment, 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 engine type. You manually run an installation script to install and launch an engine instance on each on-premises or cloud computing machine that you have set up.
- Amazon EC2
- When you create and enable an Amazon EC2 deployment for an AWS environment, Control Hub connects to the Amazon VPC specified in the environment and provisions the AWS resources needed to run the engine type, ensuring that the resources meet engine requirements. Engine instances are then automatically deployed and launched on those resources.
- Google Compute Engine (GCE)
- When you create and enable a GCE deployment for a Google Cloud Platform (GCP) environment, Control Hub connects to the Google Cloud project and VPC network specified in the environment and provisions the Google Cloud resources needed to run the engine type, ensuring that the resources meet engine requirements. Engine instances are then automatically deployed and launched on those resources.