@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class CreateUserRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP
Constructor and Description |
---|
CreateUserRequest() |
Modifier and Type | Method and Description |
---|---|
CreateUserRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
String |
getHomeDirectory()
The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server using the
client.
|
List<HomeDirectoryMapEntry> |
getHomeDirectoryMappings()
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible.
|
String |
getHomeDirectoryType()
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server.
|
String |
getPolicy()
A scope-down policy for your user so you can use the same IAM role across multiple users.
|
String |
getRole()
The IAM role that controls your users' access to your Amazon S3 bucket.
|
String |
getServerId()
A system-assigned unique identifier for a file transfer protocol-enabled server instance.
|
String |
getSshPublicKeyBody()
The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer
protocol-enabled server.
|
List<Tag> |
getTags()
Key-value pairs that can be used to group and search for users.
|
String |
getUserName()
A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the
ServerId . |
int |
hashCode() |
void |
setHomeDirectory(String homeDirectory)
The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server using the
client.
|
void |
setHomeDirectoryMappings(Collection<HomeDirectoryMapEntry> homeDirectoryMappings)
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible.
|
void |
setHomeDirectoryType(String homeDirectoryType)
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server.
|
void |
setPolicy(String policy)
A scope-down policy for your user so you can use the same IAM role across multiple users.
|
void |
setRole(String role)
The IAM role that controls your users' access to your Amazon S3 bucket.
|
void |
setServerId(String serverId)
A system-assigned unique identifier for a file transfer protocol-enabled server instance.
|
void |
setSshPublicKeyBody(String sshPublicKeyBody)
The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer
protocol-enabled server.
|
void |
setTags(Collection<Tag> tags)
Key-value pairs that can be used to group and search for users.
|
void |
setUserName(String userName)
A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the
ServerId . |
String |
toString()
Returns a string representation of this object.
|
CreateUserRequest |
withHomeDirectory(String homeDirectory)
The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server using the
client.
|
CreateUserRequest |
withHomeDirectoryMappings(Collection<HomeDirectoryMapEntry> homeDirectoryMappings)
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible.
|
CreateUserRequest |
withHomeDirectoryMappings(HomeDirectoryMapEntry... homeDirectoryMappings)
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible.
|
CreateUserRequest |
withHomeDirectoryType(HomeDirectoryType homeDirectoryType)
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server.
|
CreateUserRequest |
withHomeDirectoryType(String homeDirectoryType)
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server.
|
CreateUserRequest |
withPolicy(String policy)
A scope-down policy for your user so you can use the same IAM role across multiple users.
|
CreateUserRequest |
withRole(String role)
The IAM role that controls your users' access to your Amazon S3 bucket.
|
CreateUserRequest |
withServerId(String serverId)
A system-assigned unique identifier for a file transfer protocol-enabled server instance.
|
CreateUserRequest |
withSshPublicKeyBody(String sshPublicKeyBody)
The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer
protocol-enabled server.
|
CreateUserRequest |
withTags(Collection<Tag> tags)
Key-value pairs that can be used to group and search for users.
|
CreateUserRequest |
withTags(Tag... tags)
Key-value pairs that can be used to group and search for users.
|
CreateUserRequest |
withUserName(String userName)
A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the
ServerId . |
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeout
public void setHomeDirectory(String homeDirectory)
The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server using the client.
An example is your-Amazon-S3-bucket-name>/home/username
.
homeDirectory
- The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server
using the client.
An example is your-Amazon-S3-bucket-name>/home/username
.
public String getHomeDirectory()
The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server using the client.
An example is your-Amazon-S3-bucket-name>/home/username
.
An example is your-Amazon-S3-bucket-name>/home/username
.
public CreateUserRequest withHomeDirectory(String homeDirectory)
The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server using the client.
An example is your-Amazon-S3-bucket-name>/home/username
.
homeDirectory
- The landing directory (folder) for a user when they log in to the file transfer protocol-enabled server
using the client.
An example is your-Amazon-S3-bucket-name>/home/username
.
public void setHomeDirectoryType(String homeDirectoryType)
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute Amazon S3
bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
, you will need to
provide mappings in the HomeDirectoryMappings
for how you want to make Amazon S3 paths visible to
your users.
homeDirectoryType
- The type of landing directory (folder) you want your users' home directory to be when they log into the
file transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute
Amazon S3 bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
,
you will need to provide mappings in the HomeDirectoryMappings
for how you want to make
Amazon S3 paths visible to your users.HomeDirectoryType
public String getHomeDirectoryType()
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute Amazon S3
bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
, you will need to
provide mappings in the HomeDirectoryMappings
for how you want to make Amazon S3 paths visible to
your users.
PATH
, the user will see the absolute
Amazon S3 bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
,
you will need to provide mappings in the HomeDirectoryMappings
for how you want to make
Amazon S3 paths visible to your users.HomeDirectoryType
public CreateUserRequest withHomeDirectoryType(String homeDirectoryType)
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute Amazon S3
bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
, you will need to
provide mappings in the HomeDirectoryMappings
for how you want to make Amazon S3 paths visible to
your users.
homeDirectoryType
- The type of landing directory (folder) you want your users' home directory to be when they log into the
file transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute
Amazon S3 bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
,
you will need to provide mappings in the HomeDirectoryMappings
for how you want to make
Amazon S3 paths visible to your users.HomeDirectoryType
public CreateUserRequest withHomeDirectoryType(HomeDirectoryType homeDirectoryType)
The type of landing directory (folder) you want your users' home directory to be when they log into the file
transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute Amazon S3
bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
, you will need to
provide mappings in the HomeDirectoryMappings
for how you want to make Amazon S3 paths visible to
your users.
homeDirectoryType
- The type of landing directory (folder) you want your users' home directory to be when they log into the
file transfer protocol-enabled server. If you set it to PATH
, the user will see the absolute
Amazon S3 bucket paths as is in their file transfer protocol clients. If you set it LOGICAL
,
you will need to provide mappings in the HomeDirectoryMappings
for how you want to make
Amazon S3 paths visible to your users.HomeDirectoryType
public List<HomeDirectoryMapEntry> getHomeDirectoryMappings()
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible. You will need to specify the "Entry
" and "Target
" pair,
where Entry
shows how the path is made visible and Target
is the actual Amazon S3 path.
If you only specify a target, it will be displayed as is. You will need to also make sure that your AWS IAM Role
provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the designated
home directory ("chroot"). To do this, you can set Entry
to '/' and set Target
to the
HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If using
the CLI, use the s3api
call instead of s3
so you can use the put-object operation. For
example, you use the following: aws s3api put-object --bucket bucketname --key path/to/folder/
. Make
sure that the end of the key name ends in a '/' for it to be considered a folder.
Entry
" and "
Target
" pair, where Entry
shows how the path is made visible and
Target
is the actual Amazon S3 path. If you only specify a target, it will be displayed as
is. You will need to also make sure that your AWS IAM Role provides access to paths in
Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the
designated home directory ("chroot"). To do this, you can set Entry
to '/' and set
Target
to the HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory.
If using the CLI, use the s3api
call instead of s3
so you can use the
put-object operation. For example, you use the following:
aws s3api put-object --bucket bucketname --key path/to/folder/
. Make sure that the end of
the key name ends in a '/' for it to be considered a folder.
public void setHomeDirectoryMappings(Collection<HomeDirectoryMapEntry> homeDirectoryMappings)
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible. You will need to specify the "Entry
" and "Target
" pair,
where Entry
shows how the path is made visible and Target
is the actual Amazon S3 path.
If you only specify a target, it will be displayed as is. You will need to also make sure that your AWS IAM Role
provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the designated
home directory ("chroot"). To do this, you can set Entry
to '/' and set Target
to the
HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If using
the CLI, use the s3api
call instead of s3
so you can use the put-object operation. For
example, you use the following: aws s3api put-object --bucket bucketname --key path/to/folder/
. Make
sure that the end of the key name ends in a '/' for it to be considered a folder.
homeDirectoryMappings
- Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and
how you want to make them visible. You will need to specify the "Entry
" and "
Target
" pair, where Entry
shows how the path is made visible and
Target
is the actual Amazon S3 path. If you only specify a target, it will be displayed as
is. You will need to also make sure that your AWS IAM Role provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the
designated home directory ("chroot"). To do this, you can set Entry
to '/' and set
Target
to the HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If
using the CLI, use the s3api
call instead of s3
so you can use the put-object
operation. For example, you use the following:
aws s3api put-object --bucket bucketname --key path/to/folder/
. Make sure that the end of the
key name ends in a '/' for it to be considered a folder.
public CreateUserRequest withHomeDirectoryMappings(HomeDirectoryMapEntry... homeDirectoryMappings)
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible. You will need to specify the "Entry
" and "Target
" pair,
where Entry
shows how the path is made visible and Target
is the actual Amazon S3 path.
If you only specify a target, it will be displayed as is. You will need to also make sure that your AWS IAM Role
provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the designated
home directory ("chroot"). To do this, you can set Entry
to '/' and set Target
to the
HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If using
the CLI, use the s3api
call instead of s3
so you can use the put-object operation. For
example, you use the following: aws s3api put-object --bucket bucketname --key path/to/folder/
. Make
sure that the end of the key name ends in a '/' for it to be considered a folder.
NOTE: This method appends the values to the existing list (if any). Use
setHomeDirectoryMappings(java.util.Collection)
or
withHomeDirectoryMappings(java.util.Collection)
if you want to override the existing values.
homeDirectoryMappings
- Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and
how you want to make them visible. You will need to specify the "Entry
" and "
Target
" pair, where Entry
shows how the path is made visible and
Target
is the actual Amazon S3 path. If you only specify a target, it will be displayed as
is. You will need to also make sure that your AWS IAM Role provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the
designated home directory ("chroot"). To do this, you can set Entry
to '/' and set
Target
to the HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If
using the CLI, use the s3api
call instead of s3
so you can use the put-object
operation. For example, you use the following:
aws s3api put-object --bucket bucketname --key path/to/folder/
. Make sure that the end of the
key name ends in a '/' for it to be considered a folder.
public CreateUserRequest withHomeDirectoryMappings(Collection<HomeDirectoryMapEntry> homeDirectoryMappings)
Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and how you
want to make them visible. You will need to specify the "Entry
" and "Target
" pair,
where Entry
shows how the path is made visible and Target
is the actual Amazon S3 path.
If you only specify a target, it will be displayed as is. You will need to also make sure that your AWS IAM Role
provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the designated
home directory ("chroot"). To do this, you can set Entry
to '/' and set Target
to the
HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If using
the CLI, use the s3api
call instead of s3
so you can use the put-object operation. For
example, you use the following: aws s3api put-object --bucket bucketname --key path/to/folder/
. Make
sure that the end of the key name ends in a '/' for it to be considered a folder.
homeDirectoryMappings
- Logical directory mappings that specify what Amazon S3 paths and keys should be visible to your user and
how you want to make them visible. You will need to specify the "Entry
" and "
Target
" pair, where Entry
shows how the path is made visible and
Target
is the actual Amazon S3 path. If you only specify a target, it will be displayed as
is. You will need to also make sure that your AWS IAM Role provides access to paths in Target
. The following is an example.
'[ "/bucket2/documentation", { "Entry": "your-personal-report.pdf", "Target": "/bucket3/customized-reports/${transfer:UserName}.pdf" } ]'
In most cases, you can use this value instead of the scope-down policy to lock your user down to the
designated home directory ("chroot"). To do this, you can set Entry
to '/' and set
Target
to the HomeDirectory parameter value.
If the target of a logical directory entry does not exist in Amazon S3, the entry will be ignored. As a
workaround, you can use the Amazon S3 api to create 0 byte objects as place holders for your directory. If
using the CLI, use the s3api
call instead of s3
so you can use the put-object
operation. For example, you use the following:
aws s3api put-object --bucket bucketname --key path/to/folder/
. Make sure that the end of the
key name ends in a '/' for it to be considered a folder.
public void setPolicy(String policy)
A scope-down policy for your user so you can use the same IAM role across multiple users. This policy scopes down
user access to portions of their Amazon S3 bucket. Variables that you can use inside this policy include
${Transfer:UserName}
, ${Transfer:HomeDirectory}
, and
${Transfer:HomeBucket}
.
For scope-down policies, AWS 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 scope-down policy, see Creating a Scope-Down Policy.
For more information, see AssumeRole in the AWS Security Token Service API Reference.
policy
- A scope-down policy for your user so you can use the same IAM role across multiple users. This policy
scopes down user access to portions of their Amazon S3 bucket. Variables that you can use inside this
policy include ${Transfer:UserName}
, ${Transfer:HomeDirectory}
, and
${Transfer:HomeBucket}
.
For scope-down policies, AWS 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 scope-down policy, see Creating a Scope-Down Policy.
For more information, see AssumeRole in the AWS Security Token Service API Reference.
public String getPolicy()
A scope-down policy for your user so you can use the same IAM role across multiple users. This policy scopes down
user access to portions of their Amazon S3 bucket. Variables that you can use inside this policy include
${Transfer:UserName}
, ${Transfer:HomeDirectory}
, and
${Transfer:HomeBucket}
.
For scope-down policies, AWS 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 scope-down policy, see Creating a Scope-Down Policy.
For more information, see AssumeRole in the AWS Security Token Service API Reference.
${Transfer:UserName}
, ${Transfer:HomeDirectory}
, and
${Transfer:HomeBucket}
.
For scope-down policies, AWS 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 scope-down policy, see Creating a Scope-Down Policy.
For more information, see AssumeRole in the AWS Security Token Service API Reference.
public CreateUserRequest withPolicy(String policy)
A scope-down policy for your user so you can use the same IAM role across multiple users. This policy scopes down
user access to portions of their Amazon S3 bucket. Variables that you can use inside this policy include
${Transfer:UserName}
, ${Transfer:HomeDirectory}
, and
${Transfer:HomeBucket}
.
For scope-down policies, AWS 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 scope-down policy, see Creating a Scope-Down Policy.
For more information, see AssumeRole in the AWS Security Token Service API Reference.
policy
- A scope-down policy for your user so you can use the same IAM role across multiple users. This policy
scopes down user access to portions of their Amazon S3 bucket. Variables that you can use inside this
policy include ${Transfer:UserName}
, ${Transfer:HomeDirectory}
, and
${Transfer:HomeBucket}
.
For scope-down policies, AWS 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 scope-down policy, see Creating a Scope-Down Policy.
For more information, see AssumeRole in the AWS Security Token Service API Reference.
public void setRole(String role)
The IAM role that controls your users' access to your Amazon S3 bucket. The policies attached to this role will determine the level of access you want to provide your users when transferring files into and out of your Amazon S3 bucket or buckets. The IAM role should also contain a trust relationship that allows the file transfer protocol-enabled server to access your resources when servicing your users' transfer requests.
role
- The IAM role that controls your users' access to your Amazon S3 bucket. The policies attached to this role
will determine the level of access you want to provide your users when transferring files into and out of
your Amazon S3 bucket or buckets. The IAM role should also contain a trust relationship that allows the
file transfer protocol-enabled server to access your resources when servicing your users' transfer
requests.public String getRole()
The IAM role that controls your users' access to your Amazon S3 bucket. The policies attached to this role will determine the level of access you want to provide your users when transferring files into and out of your Amazon S3 bucket or buckets. The IAM role should also contain a trust relationship that allows the file transfer protocol-enabled server to access your resources when servicing your users' transfer requests.
public CreateUserRequest withRole(String role)
The IAM role that controls your users' access to your Amazon S3 bucket. The policies attached to this role will determine the level of access you want to provide your users when transferring files into and out of your Amazon S3 bucket or buckets. The IAM role should also contain a trust relationship that allows the file transfer protocol-enabled server to access your resources when servicing your users' transfer requests.
role
- The IAM role that controls your users' access to your Amazon S3 bucket. The policies attached to this role
will determine the level of access you want to provide your users when transferring files into and out of
your Amazon S3 bucket or buckets. The IAM role should also contain a trust relationship that allows the
file transfer protocol-enabled server to access your resources when servicing your users' transfer
requests.public void setServerId(String serverId)
A system-assigned unique identifier for a file transfer protocol-enabled server instance. This is the specific server that you added your user to.
serverId
- A system-assigned unique identifier for a file transfer protocol-enabled server instance. This is the
specific server that you added your user to.public String getServerId()
A system-assigned unique identifier for a file transfer protocol-enabled server instance. This is the specific server that you added your user to.
public CreateUserRequest withServerId(String serverId)
A system-assigned unique identifier for a file transfer protocol-enabled server instance. This is the specific server that you added your user to.
serverId
- A system-assigned unique identifier for a file transfer protocol-enabled server instance. This is the
specific server that you added your user to.public void setSshPublicKeyBody(String sshPublicKeyBody)
The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer protocol-enabled server.
sshPublicKeyBody
- The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer
protocol-enabled server.public String getSshPublicKeyBody()
The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer protocol-enabled server.
public CreateUserRequest withSshPublicKeyBody(String sshPublicKeyBody)
The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer protocol-enabled server.
sshPublicKeyBody
- The public portion of the Secure Shell (SSH) key used to authenticate the user to the file transfer
protocol-enabled server.public List<Tag> getTags()
Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for any purpose.
public void setTags(Collection<Tag> tags)
Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for any purpose.
tags
- Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for
any purpose.public CreateUserRequest withTags(Tag... tags)
Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for any purpose.
NOTE: This method appends the values to the existing list (if any). Use
setTags(java.util.Collection)
or withTags(java.util.Collection)
if you want to override the
existing values.
tags
- Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for
any purpose.public CreateUserRequest withTags(Collection<Tag> tags)
Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for any purpose.
tags
- Key-value pairs that can be used to group and search for users. Tags are metadata attached to users for
any purpose.public void setUserName(String userName)
A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the ServerId
. This user name must be a minimum of 3 and a maximum of 32 characters
long. The following are valid characters: a-z, A-Z, 0-9, underscore, and hyphen. The user name can't start with a
hyphen.
userName
- A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the ServerId
. This user name must be a minimum of 3 and a maximum of 32
characters long. The following are valid characters: a-z, A-Z, 0-9, underscore, and hyphen. The user name
can't start with a hyphen.public String getUserName()
A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the ServerId
. This user name must be a minimum of 3 and a maximum of 32 characters
long. The following are valid characters: a-z, A-Z, 0-9, underscore, and hyphen. The user name can't start with a
hyphen.
ServerId
. This user name must be a minimum of 3 and a maximum of 32
characters long. The following are valid characters: a-z, A-Z, 0-9, underscore, and hyphen. The user name
can't start with a hyphen.public CreateUserRequest withUserName(String userName)
A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the ServerId
. This user name must be a minimum of 3 and a maximum of 32 characters
long. The following are valid characters: a-z, A-Z, 0-9, underscore, and hyphen. The user name can't start with a
hyphen.
userName
- A unique string that identifies a user and is associated with a file transfer protocol-enabled server as
specified by the ServerId
. This user name must be a minimum of 3 and a maximum of 32
characters long. The following are valid characters: a-z, A-Z, 0-9, underscore, and hyphen. The user name
can't start with a hyphen.public String toString()
toString
in class Object
Object.toString()
public CreateUserRequest clone()
AmazonWebServiceRequest
clone
in class AmazonWebServiceRequest
Object.clone()
Copyright © 2013 Amazon Web Services, Inc. All Rights Reserved.