An environment defines where to deploy StreamSets engines. An environment represents the resources needed to run the engines.
When using 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.
When using an Amazon Web Services (AWS) environment, Control Hub connects to your AWS account, provisions the AWS resources needed to run engines, and deploys engine instances to those resources.
When using a Microsoft Azure (Azure) environment, Control Hub connects to your Azure account, provisions the Azure resources needed to run engines, and deploys engine instances to those resources.
When using a Google Cloud Platform (GCP) environment, Control Hub connects to your Google Cloud project, provisions the Google Cloud resources needed to run engines, and deploys engine instances to those resources.
When you view the list of environments in the Environments view, you can view the state of each environment.
An environment tag identifies similar environments. Use tags to easily search and filter environments when viewing them in the Environments view. For example, you might want to group environments by the team or project.
When you manage environments, you can filter the list of displayed environments, activate or deactivate environments, and edit environments.