Hello @Faisal_555 @Hai1  The above Error happens for 2 Reasoning majorly: (I) Each Environment creates an Ozone Bucket (When the Environment is Created first) & CDE uses the concerned Ozone Bucket upon being Enabled within the Environment. 1 Top Reason is the Environment was Created when Ozone wasn't Installed or Ozone wasn't Healthy, upon which Ozone Bucket won't be Created. Hence, the Error [1] shows CDE isn't able to fetch the Ozone Info from Env (Wherein "aws_key_id" is reference to Ozone).  (II) To rule out the above, Ensure Ozone is Healthy & Create a New Environment, followed by Enabling the CDE Service. This would rule out any issues with Ozone & Environment Bucket. (III) Next, Ensure the "hive" User has Ranger Permission to Create/List Ozone Bucket as documented in [2]. Even if Ozone is Healthy, the Bucket Creation is required & the same is facilitated via "hive" User & Ranger Permission may forbade the same. If the above Action Plan doesn't resolve the Issue, Best to engage Cloudera Support for us to Collaborate further. - Smarak [1]  Log: unable to find logging configurations from environment, error: unable to retrieve aws_key_id from the env service  [2] https://docs.cloudera.com/cdp-private-cloud-data-services/1.5.3/installation/topics/cdppvc-installation-cdp-data-center.html  ... View more