Cloudbreak Release Notes
Also available as:
PDF

New features

Cloudbreak 2.8.0 TP introduces the following new features:

Feature Description Documentation
AWS GovCloud Cloudbreak supports installing Cloudbreak and creating Cloudbreak-managed clusters on AWS GovCloud. Deploying on AWS vs AWS GovCloud
EBS volume encryption on AWS You can optionally configure encryption for EBS volumes attached to cluster instances running on EC2. Default or customer-managed encryption keys can be used. EBS encryption on AWS
GCP volume encryption By default, Compute Engine encrypts data at rest stored on disks. You can optionally configure encryption for the encryption keys used for disk encryption. Customer-supplied (CSEK) or customer-managed (CMEK) encryption keys can be used. Disk encryption on GCP
User authorization Cloudbreak introduces a new authorization model, which allows resource sharing via organizations. User authorization
Operations audit logging Cloudbreak records an audit trail of the actions performed by Cloudbreak users as well as those performed by the Cloudbreak application. Operations audit logging
Updating long-running cluster Cloudbreak supports updating base image's operating system and any third party packages that have been installed. Updating long-running clusters
Data lake HA and Atlas support Cloudbreak includes two data lake blueprints:
  • Data lake HA blueprint
  • Data lake blueprint including Atlas (HA is not supported)
Working with Data Lakes (TP)
Multiple existing security groups on AWS Multiple existing security groups can be specified when creating a cluster via CLI on AWS. Multiple existing security groups on AWS
Shebang in Python recipes Cloudbreak supports using shebang in Python scripts run as recipes. Writing recipes
HDF 3.2 Cloudbreak can be used to deploy HDF 3.2 clusters by using one of the two default HDF 3.2 blueprints:
  • Flow Management clusters with Apache NiFi
  • Messaging clusters with Apache Kafka.
Default cluster configurations