Environments Overview
An environment defines where to deploy IBM StreamSets engines. An environment represents the resources needed to run the engines.
After you create and activate an environment, you create a deployment that defines a group of identical engine instances to launch into that environment. A single environment can host multiple deployments.
- Self-managed
- In a self-managed environment, you take full control of procuring the resources needed to run engines and deploying engine instances to those resources. A self-managed environment can represent local on-premises machines or cloud computing machines.
- Control Hub-managed
- In a Control Hub-managed environment, Control Hub connects to the external system represented by the environment, automatically provisions the resources needed to run engines, and deploys engine instances to those resources.
You can create multiple environments of the same type or of different types. For example, you might want to dedicate one AWS VPC to the designing and running of test pipelines, and another VPC to the running of production pipelines. You would create two AWS environments in Control Hub, one for the test VPC and another for the production VPC. Then you would create one deployment to provision resources and launch engine instances in the test AWS environment and another deployment to do the same in the production AWS environment.
When you create an environment, you select the feature version to use for that environment and for all deployments created for the environment.