CreateUser
Creates a user and associates them with an existing file transfer protocol-enabled server.
You can only create and associate users with servers that have the
IdentityProviderType
set to SERVICE_MANAGED
. Using parameters for
CreateUser
, you can specify the user name, set the home directory, store the
user's public key, and assign the user's Amazon Identity and Access Management (IAM)
role. You can also optionally add a session policy, and assign metadata with tags that can
be used to group and search for users.
Request Syntax
{
"HomeDirectory": "string
",
"HomeDirectoryMappings": [
{
"Entry": "string
",
"Target": "string
",
"Type": "string
"
}
],
"HomeDirectoryType": "string
",
"Policy": "string
",
"PosixProfile": {
"Gid": number
,
"SecondaryGids": [ number
],
"Uid": number
},
"Role": "string
",
"ServerId": "string
",
"SshPublicKeyBody": "string
",
"Tags": [
{
"Key": "string
",
"Value": "string
"
}
],
"UserName": "string
"
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- HomeDirectory
-
The landing directory (folder) for a user when they log in to the server using the client.
A
HomeDirectory
example is/bucket_name/home/mydirectory
.Note
The
HomeDirectory
parameter is only used ifHomeDirectoryType
is set toPATH
.Type: String
Length Constraints: Minimum length of 0. Maximum length of 1024.
Pattern:
(|/.*)
Required: No
- HomeDirectoryMappings
-
Logical directory mappings that specify what Amazon S3 or Amazon EFS paths and keys should be visible to your user and how you want to make them visible. You must specify the
Entry
andTarget
pair, whereEntry
shows how the path is made visible andTarget
is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it is displayed as is. You also must ensure that your Amazon Identity and Access Management (IAM) role provides access to paths inTarget
. This value can be set only whenHomeDirectoryType
is set to LOGICAL.The following is an
Entry
andTarget
pair example.[ { "Entry": "/directory1", "Target": "/bucket_name/home/mydirectory" } ]
In most cases, you can use this value instead of the session policy to lock your user down to the designated home directory ("
chroot
"). To do this, you can setEntry
to/
and setTarget
to the value the user should see for their home directory when they log in.The following is an
Entry
andTarget
pair example forchroot
.[ { "Entry": "/", "Target": "/bucket_name/home/mydirectory" } ]
Type: Array of HomeDirectoryMapEntry objects
Array Members: Minimum number of 1 item. Maximum number of 50000 items.
Required: No
- HomeDirectoryType
-
The type of landing directory (folder) that you want your users' home directory to be when they log in to the server. If you set it to
PATH
, the user will see the absolute Amazon S3 bucket or Amazon EFS path as is in their file transfer protocol clients. If you set it toLOGICAL
, you need to provide mappings in theHomeDirectoryMappings
for how you want to make Amazon S3 or Amazon EFS paths visible to your users.Note
If
HomeDirectoryType
isLOGICAL
, you must provide mappings, using theHomeDirectoryMappings
parameter. If, on the other hand,HomeDirectoryType
isPATH
, you provide an absolute path using theHomeDirectory
parameter. You cannot have bothHomeDirectory
andHomeDirectoryMappings
in your template.Type: String
Valid Values:
PATH | LOGICAL
Required: No
- Policy
-
A session policy for your user so that you can use the same Amazon Identity and Access Management (IAM) role across multiple users. This policy scopes down a user's access to portions of their Amazon S3 bucket. Variables that you can use inside this policy include
${Transfer:UserName}
,${Transfer:HomeDirectory}
, and${Transfer:HomeBucket}
.Note
This policy applies only when the domain of
ServerId
is Amazon S3. Amazon EFS does not use session policies.For session policies, Amazon Transfer Family stores the policy as a JSON blob, instead of the Amazon Resource Name (ARN) of the policy. You save the policy as a JSON blob and pass it in the
Policy
argument.For an example of a session policy, see Example session policy.
For more information, see AssumeRole in the Amazon Security Token Service API Reference.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 2048.
Required: No
- PosixProfile
-
Specifies the full POSIX identity, including user ID (
Uid
), group ID (Gid
), and any secondary groups IDs (SecondaryGids
), that controls your users' access to your Amazon EFS file systems. The POSIX permissions that are set on files and directories in Amazon EFS determine the level of access your users get when transferring files into and out of your Amazon EFS file systems.Type: PosixProfile object
Required: No
- Role
-
The Amazon Resource Name (ARN) of the Amazon Identity and Access Management (IAM) role that controls your users' access to your Amazon S3 bucket or Amazon EFS file system. The policies attached to this role determine the level of access that you want to provide your users when transferring files into and out of your Amazon S3 bucket or Amazon EFS file system. The IAM role should also contain a trust relationship that allows the server to access your resources when servicing your users' transfer requests.
Type: String
Length Constraints: Minimum length of 20. Maximum length of 2048.
Pattern:
arn:.*role/\S+
Required: Yes
- ServerId
-
A system-assigned unique identifier for a server instance. This is the specific server that you added your user to.
Type: String
Length Constraints: Fixed length of 19.
Pattern:
s-([0-9a-f]{17})
Required: Yes
- SshPublicKeyBody
-
The public portion of the Secure Shell (SSH) key used to authenticate the user to the server.
The three standard SSH public key format elements are
<key type>
,<body base64>
, and an optional<comment>
, with spaces between each element.Amazon Transfer Family accepts RSA, ECDSA, and ED25519 keys.
-
For RSA keys, the key type is
ssh-rsa
. -
For ED25519 keys, the key type is
ssh-ed25519
. -
For ECDSA keys, the key type is either
ecdsa-sha2-nistp256
,ecdsa-sha2-nistp384
, orecdsa-sha2-nistp521
, depending on the size of the key you generated.
Type: String
Length Constraints: Minimum length of 0. Maximum length of 2048.
Required: No
-
- Tags
-
Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for any purpose.
Type: Array of Tag objects
Array Members: Minimum number of 1 item. Maximum number of 50 items.
Required: No
- UserName
-
A unique string that identifies a user and is associated with a
ServerId
. This user name must be a minimum of 3 and a maximum of 100 characters long. The following are valid characters: a-z, A-Z, 0-9, underscore '_', hyphen '-', period '.', and at sign '@'. The user name can't start with a hyphen, period, or at sign.Type: String
Length Constraints: Minimum length of 3. Maximum length of 100.
Pattern:
[\w][\w@.-]{2,99}
Required: Yes
Response Syntax
{
"ServerId": "string",
"UserName": "string"
}
Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- ServerId
-
The identifier of the server that the user is attached to.
Type: String
Length Constraints: Fixed length of 19.
Pattern:
s-([0-9a-f]{17})
- UserName
-
A unique string that identifies a Transfer Family user.
Type: String
Length Constraints: Minimum length of 3. Maximum length of 100.
Pattern:
[\w][\w@.-]{2,99}
Errors
For information about the errors that are common to all actions, see Common Errors.
- InternalServiceError
-
This exception is thrown when an error occurs in the Amazon Transfer Family service.
HTTP Status Code: 500
- InvalidRequestException
-
This exception is thrown when the client submits a malformed request.
HTTP Status Code: 400
- ResourceExistsException
-
The requested resource does not exist, or exists in a region other than the one specified for the command.
HTTP Status Code: 400
- ResourceNotFoundException
-
This exception is thrown when a resource is not found by the AmazonTransfer Family service.
HTTP Status Code: 400
- ServiceUnavailableException
-
The request has failed because the AmazonTransfer Family service is not available.
HTTP Status Code: 500
Examples
Example
To create a user, you can first save the parameters into a JSON file, for example createUserParameters
, then run the create-user API command.
{ "HomeDirectory": "/amzn-s3-demo-bucket", "HomeDirectoryType": "PATH", "Role": "arn:aws:iam::111122223333:role/bob-role", "ServerId": "s-1111aaaa2222bbbb3", "SshPublicKeyBody": "ecdsa-sha2-nistp521 AAAAE2VjZHNhLXNoYTItbmlzdHA... bobusa@mycomputer.us-east-1.amazon.com", "UserName": "bobusa-API" }
Sample Request
aws transfer create-user --cli-input-json file://createUserParameters
Sample Response
{
"ServerId": ""s-1111aaaa2222bbbb3",
"UserName": "bobusa-API"
}
See Also
For more information about using this API in one of the language-specific Amazon SDKs, see the following: