https://community.cloudera.com/t5/Support-Questions/NoAuthWithAWSException-while-running-create-database-in-hive/m-p/305697#M222546 <P>This was resolved by enabling&nbsp;<SPAN>IMDSv1</SPAN> on the idbroker ec2 instance.&nbsp;<BR /><A href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html" target="_blank">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html</A>&nbsp;</P><LI-CODE lang="markup">aws ec2 modify-instance-metadata-options \ --instance-id [idbroker instance id] \ --http-tokens optional \ --http-endpoint enabled</LI-CODE> Mon, 09 Nov 2020 20:06:50 GMT kmc 2020-11-09T20:06:50Z https://community.cloudera.com/t5/Support-Questions/NoAuthWithAWSException-while-running-create-database-in-hive/m-p/305142#M222324 <P>While trying to create a database through hive in Hue or using jdbc, I reveive the following error.</P><LI-CODE lang="markup">Error while compiling statement: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.ddl.DDLTask. java.nio.file.AccessDeniedException: [bucket]: org.apache.hadoop.fs.s3a.auth.NoAuthWithAWSException: Missing required credential provisioning for Cloud Access Broker. It is expected that keys and secrets be provisioned as aliases or that Cloud Access Broker be running on a node with an Instance Profile attached.</LI-CODE><P>If I ssh into a node and run hdfs dfs -ls s3a://[bucket-name]/ I also see</P><LI-CODE lang="markup">20/10/29 19:42:47 INFO impl.MetricsSystemImpl: s3a-file-system metrics system started Oct 29, 2020 7:42:47 PM org.apache.knox.gateway.shell.KnoxSession createClient INFO: Using default JAAS configuration 20/10/29 19:42:48 INFO Configuration.deprecation: No unit for fs.s3a.connection.request.timeout(0) assuming SECONDS 20/10/29 19:42:48 ERROR common.DefaultRequestExecutor: Error executing request: org.apache.knox.gateway.shell.ErrorResponse: https://[broker-name]:8444/gateway/aws-cab/cab/api/v1/credentials: HTTP/1.1 500 Internal Server Error 20/10/29 19:42:48 ERROR idbroker.AbstractIDBClient: Cloud Access Broker response: { "error": "Missing required credential provisioning for Cloud Access Broker. It is expected that keys and secrets be provisioned as aliases or that Cloud Access Broker be running on a node with an Instance Profile attached." }</LI-CODE><P>&nbsp;</P> Tue, 21 Apr 2026 11:23:44 GMT https://community.cloudera.com/t5/Support-Questions/NoAuthWithAWSException-while-running-create-database-in-hive/m-p/305142#M222324 kmc 2026-04-21T11:23:44Z https://community.cloudera.com/t5/Support-Questions/NoAuthWithAWSException-while-running-create-database-in-hive/m-p/305697#M222546 <P>This was resolved by enabling&nbsp;<SPAN>IMDSv1</SPAN> on the idbroker ec2 instance.&nbsp;<BR /><A href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html" target="_blank">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html</A>&nbsp;</P><LI-CODE lang="markup">aws ec2 modify-instance-metadata-options \ --instance-id [idbroker instance id] \ --http-tokens optional \ --http-endpoint enabled</LI-CODE> Mon, 09 Nov 2020 20:06:50 GMT https://community.cloudera.com/t5/Support-Questions/NoAuthWithAWSException-while-running-create-database-in-hive/m-p/305697#M222546 kmc 2020-11-09T20:06:50Z