Creates an endpoint for a Hadoop Distributed File System (HDFS).
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
create-location-hdfs
[--subdirectory <value>]
--name-nodes <value>
[--block-size <value>]
[--replication-factor <value>]
[--kms-key-provider-uri <value>]
[--qop-configuration <value>]
--authentication-type <value>
[--simple-user <value>]
[--kerberos-principal <value>]
[--kerberos-keytab <value>]
[--kerberos-krb5-conf <value>]
--agent-arns <value>
[--tags <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
--subdirectory
(string)
A subdirectory in the HDFS cluster. This subdirectory is used to read data from or write data to the HDFS cluster. If the subdirectory isn’t specified, it will default to
/
.
--name-nodes
(list)
The NameNode that manages the HDFS namespace. The NameNode performs operations such as opening, closing, and renaming files and directories. The NameNode contains the information to map blocks of data to the DataNodes. You can use only one NameNode.
(structure)
The NameNode of the Hadoop Distributed File System (HDFS). The NameNode manages the file system’s namespace. The NameNode performs operations such as opening, closing, and renaming files and directories. The NameNode contains the information to map blocks of data to the DataNodes.
Hostname -> (string)
The hostname of the NameNode in the HDFS cluster. This value is the IP address or Domain Name Service (DNS) name of the NameNode. An agent that’s installed on-premises uses this hostname to communicate with the NameNode in the network.
Port -> (integer)
The port that the NameNode uses to listen to client requests.
Shorthand Syntax:
Hostname=string,Port=integer ...
JSON Syntax:
[
{
"Hostname": "string",
"Port": integer
}
...
]
--block-size
(integer)
The size of data blocks to write into the HDFS cluster. The block size must be a multiple of 512 bytes. The default block size is 128 mebibytes (MiB).
--replication-factor
(integer)
The number of DataNodes to replicate the data to when writing to the HDFS cluster. By default, data is replicated to three DataNodes.
--kms-key-provider-uri
(string)
The URI of the HDFS cluster’s Key Management Server (KMS).
--qop-configuration
(structure)
The Quality of Protection (QOP) configuration specifies the Remote Procedure Call (RPC) and data transfer protection settings configured on the Hadoop Distributed File System (HDFS) cluster. If
QopConfiguration
isn’t specified,RpcProtection
andDataTransferProtection
default toPRIVACY
. If you setRpcProtection
orDataTransferProtection
, the other parameter assumes the same value.RpcProtection -> (string)
The RPC protection setting configured on the HDFS cluster. This setting corresponds to your
hadoop.rpc.protection
setting in yourcore-site.xml
file on your Hadoop cluster.DataTransferProtection -> (string)
The data transfer protection setting configured on the HDFS cluster. This setting corresponds to your
dfs.data.transfer.protection
setting in thehdfs-site.xml
file on your Hadoop cluster.
Shorthand Syntax:
RpcProtection=string,DataTransferProtection=string
JSON Syntax:
{
"RpcProtection": "DISABLED"|"AUTHENTICATION"|"INTEGRITY"|"PRIVACY",
"DataTransferProtection": "DISABLED"|"AUTHENTICATION"|"INTEGRITY"|"PRIVACY"
}
--authentication-type
(string)
The type of authentication used to determine the identity of the user.
Possible values:
SIMPLE
KERBEROS
--simple-user
(string)
The user name used to identify the client on the host operating system.
Note
If
SIMPLE
is specified forAuthenticationType
, this parameter is required.
--kerberos-principal
(string)
The Kerberos principal with access to the files and folders on the HDFS cluster.
Note
If
KERBEROS
is specified forAuthenticationType
, this parameter is required.
--kerberos-keytab
(blob)
The Kerberos key table (keytab) that contains mappings between the defined Kerberos principal and the encrypted keys. You can load the keytab from a file by providing the file’s address. If you’re using the CLI, it performs base64 encoding for you. Otherwise, provide the base64-encoded text.
Note
If
KERBEROS
is specified forAuthenticationType
, this parameter is required.
--kerberos-krb5-conf
(blob)
The
krb5.conf
file that contains the Kerberos configuration information. You can load thekrb5.conf
file by providing the file’s address. If you’re using the CLI, it performs the base64 encoding for you. Otherwise, provide the base64-encoded text.Note
If
KERBEROS
is specified forAuthenticationType
, this parameter is required.
--agent-arns
(list)
The Amazon Resource Names (ARNs) of the agents that are used to connect to the HDFS cluster.
(string)
Syntax:
"string" "string" ...
--tags
(list)
The key-value pair that represents the tag that you want to add to the location. The value can be an empty string. We recommend using tags to name your resources.
(structure)
Represents a single entry in a list of Amazon Web Services resource tags.
TagListEntry
returns an array that contains a list of tasks when the ListTagsForResource operation is called.Key -> (string)
The key for an Amazon Web Services resource tag.
Value -> (string)
The value for an Amazon Web Services resource tag.
Shorthand Syntax:
Key=string,Value=string ...
JSON Syntax:
[
{
"Key": "string",
"Value": "string"
}
...
]
--cli-input-json
| --cli-input-yaml
(string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton
. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml
.
--generate-cli-skeleton
(string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input
, prints a sample input JSON that can be used as an argument for --cli-input-json
. Similarly, if provided yaml-input
it will print a sample input YAML that can be used with --cli-input-yaml
. If provided with the value output
, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.
See ‘aws help’ for descriptions of global parameters.