question Re: AWS Access Key ID and Secret Access Key must be specified as the username or password (respectiv in Archives of Support Questions (Read Only)

AWS Access Key ID and Secret Access Key must be specified as the username or password (respectively)

Ashok — Tue, 21 Apr 2026 14:02:52 GMT

My input path in another instance of EC2 as I specified input path as

s3n://xxx-ssss/

It is showing error as:

AWS Access Key ID and Secret Access Key must be specified as the username or password (respectively) of a s3n URL, or by setting the fs.s3n.awsAccessKeyId or fs.s3n.awsSecretAccessKey properties (respectively).

Where could I configure the properties for fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in cloudera manager in web UI (HUE).

Re: AWS Access Key ID and Secret Access Key must be specified as the username or password (respectiv

dvohra — Wed, 14 Aug 2013 14:20:06 GMT

Configure fs.s3n.awsAccessKeyId and fs.s3n.awsSecretAccessKey in core-site.xml.

Re: AWS Access Key ID and Secret Access Key must be specified as the username or password (respectiv

Harsh J — Sun, 18 Aug 2013 20:38:10 GMT

For adding these properties cluster-wide into Cloudera Manager, head to CM -> HDFS -> Configuration (View and Edit) -> Search for keyword "core-site.xml safety valve" -> Edit the appropriate field by adding a list of your desired <property>…</property> configuration XML -> Save Changes. After saving, restart the cluster to propagate to all services, and also click CM -> (Cluster) Actions -> Deploy Client Configuration.

Re: AWS Access Key ID and Secret Access Key must be specified as the username or password (respectiv

herdrick — Fri, 06 Sep 2013 01:28:51 GMT

Hi Harsh,

I would think that the right order would be to "Deploy Client Configuration" first and then restart HDFS. Am I wrong?

Re: AWS Access Key ID and Secret Access Key must be specified as the username or password (respectiv

Clint — Mon, 09 Sep 2013 13:57:05 GMT

@herdrick: no it's actually just fine to do it in the order Harsh mentioned. CM will automatically deploy the configurations you specify on the Configuration tab of a service to that service's roles when you restart the service. For example, if you modify a datanode specific property in CM, save the change and restart the service, then all the datanodes will get new copies of their hdfs-site.xml files upon startup. The only reason to deploy the client configs that Harsh mentioned is for external client apps that want to utilize the cluster. If you made changes that will affect the behavior of clients, then the client configs need to be re-deployed. This can happen after the services are restarted, but before you attempt to reconnect to the cluster with your client app. I hope that clears it up.

Clint