Known issues

This section lists known issues that you might run into while using the Management Console service.

CB-4041 CDP does not whitelist CDP CIDR

Problem: When CDP creates security groups automatically, it does not open port 9443 correctly (it opens it to your CIDR instead of opening it to CDP CIDR); As a result environment creation fails.

Workaround: The possible workarounds are:

Option 1: Create your own security groups as described in AWS environment prerequisites: Security groups documentation.

Option 2: If you would still like for CDP to create all security groups, you can initially specify 0.0.0.0/0 as your CDIR range and then update all security groups manually on AWS according to Reference: Default security group settings and AWS environment prerequisites: Security groups (This mentions the correct CDP CIDR for port 9443). You will need to do this for the environment and all Data Hub clusters.

CB-3876 Data Warehouse and Machine Learning create security groups

Problem: When during environment registration you choose to use your own security groups, the Data Warehouse and Machine Learning services do not use these security groups but create their own.

Workaround: There is no workaround.

CRB-971 Data Warehouse creates IAM, S3, and DynamoDB resources

Problem: The Data Warehouse service creates its own S3 buckets, DynamoDB tables, and IAM roles and policies. It does not use the environment's S3 bucket(s), DynamoDB table, and IAM roles and policies.

Workaround: There is no workaround.

CB-4176 Data Lake cluster repair fails after manual stop

Problem: Data Lake cluster repair fails after an instance has been stopped manually via AWS console or AWS CLI.

Workaround: After stopping a cluster instance manually, restart it manually via the AWS console or AWS CLI, and then use the Sync option in CDP to sync instance state.

CB-2813 Environment with ML workspaces in it can be deleted

Problem: When deleting an environment, there is no mechanism in place to check for any existing Ml workspaces running within the environment. As a result, an environment can be deleted when ML workspaces are currently running in it.

Workaround: Prior to deleting an environment, ensure that there are no ML workspaces running within the environment.

CDPAM-349 Classic cluster functionality does not work in Firefox

Problem: Classic cluster registration does not work in the Firefox web browser.

Workaround: If you are plannig to use classic cluster functionality, use Chrome web browser to log in to the CDP web interface.