Enabling a semi-private network for a Cloudera Data Engineering service with AWS (Tech Preview)
Learn how to enable a semi-private network setup for a Cloudera Data Engineering service with Amazon Web Services (AWS) services in Cloudera. When you enable a Cloudera Data Engineering service with this feature, the Amazon Kubernetes Service (EKS) cluster is deployed as a private cluster but some services used by Cloudera Data Engineering such as MySQL and S3 are not provisioned as private.
Before you begin
- Ensure that you have created and enabled a Cloudera Data Engineering service. Additionally, Cloudera must communicate with the Cloudera Data Engineering service on a private network in order to manage the Cloudera Data Engineering service lifecycle. This communication occurs using the Cluster Connectivity Manager v2; therefore, to enable this feature, the Cloudera environment must be enabled with the CCMv2. Once the CCMv2 is enabled at the Cloudera environment level, the Enable Private Network option displays in the Cloudera Data Engineering user interface when you enable a service. For more information on how to enable a Cloudera Data Engineering service and set up CCMv2, refer to the links below.
UI steps for enabling a private network
- While enabling a Cloudera Data Engineering service for an AWS environment, under Network & Storage, select Enable Private Network.
- Click Enable.
You can enable a private network with the CDP CLI with the following commands:
cdp de enable-service --name dsp-private-eks-ntp-try1 --env dsp-aws-ntp-priv --instance-type m5.2xlarge --minimum-instances 0 --maximum-instances 4 --initial-instances 0 --root-volume-size 50 --no-skip-validation --enable-private-network