AWS SDK for C++  1.9.40
AWS SDK for C++
Public Member Functions | List of all members
Aws::Transfer::Model::UpdateUserRequest Class Reference

#include <UpdateUserRequest.h>

+ Inheritance diagram for Aws::Transfer::Model::UpdateUserRequest:

Public Member Functions

 UpdateUserRequest ()
 
virtual const char * GetServiceRequestName () const override
 
Aws::String SerializePayload () const override
 
Aws::Http::HeaderValueCollection GetRequestSpecificHeaders () const override
 
const Aws::StringGetHomeDirectory () const
 
bool HomeDirectoryHasBeenSet () const
 
void SetHomeDirectory (const Aws::String &value)
 
void SetHomeDirectory (Aws::String &&value)
 
void SetHomeDirectory (const char *value)
 
UpdateUserRequestWithHomeDirectory (const Aws::String &value)
 
UpdateUserRequestWithHomeDirectory (Aws::String &&value)
 
UpdateUserRequestWithHomeDirectory (const char *value)
 
const HomeDirectoryTypeGetHomeDirectoryType () const
 
bool HomeDirectoryTypeHasBeenSet () const
 
void SetHomeDirectoryType (const HomeDirectoryType &value)
 
void SetHomeDirectoryType (HomeDirectoryType &&value)
 
UpdateUserRequestWithHomeDirectoryType (const HomeDirectoryType &value)
 
UpdateUserRequestWithHomeDirectoryType (HomeDirectoryType &&value)
 
const Aws::Vector< HomeDirectoryMapEntry > & GetHomeDirectoryMappings () const
 
bool HomeDirectoryMappingsHasBeenSet () const
 
void SetHomeDirectoryMappings (const Aws::Vector< HomeDirectoryMapEntry > &value)
 
void SetHomeDirectoryMappings (Aws::Vector< HomeDirectoryMapEntry > &&value)
 
UpdateUserRequestWithHomeDirectoryMappings (const Aws::Vector< HomeDirectoryMapEntry > &value)
 
UpdateUserRequestWithHomeDirectoryMappings (Aws::Vector< HomeDirectoryMapEntry > &&value)
 
UpdateUserRequestAddHomeDirectoryMappings (const HomeDirectoryMapEntry &value)
 
UpdateUserRequestAddHomeDirectoryMappings (HomeDirectoryMapEntry &&value)
 
const Aws::StringGetPolicy () const
 
bool PolicyHasBeenSet () const
 
void SetPolicy (const Aws::String &value)
 
void SetPolicy (Aws::String &&value)
 
void SetPolicy (const char *value)
 
UpdateUserRequestWithPolicy (const Aws::String &value)
 
UpdateUserRequestWithPolicy (Aws::String &&value)
 
UpdateUserRequestWithPolicy (const char *value)
 
const PosixProfileGetPosixProfile () const
 
bool PosixProfileHasBeenSet () const
 
void SetPosixProfile (const PosixProfile &value)
 
void SetPosixProfile (PosixProfile &&value)
 
UpdateUserRequestWithPosixProfile (const PosixProfile &value)
 
UpdateUserRequestWithPosixProfile (PosixProfile &&value)
 
const Aws::StringGetRole () const
 
bool RoleHasBeenSet () const
 
void SetRole (const Aws::String &value)
 
void SetRole (Aws::String &&value)
 
void SetRole (const char *value)
 
UpdateUserRequestWithRole (const Aws::String &value)
 
UpdateUserRequestWithRole (Aws::String &&value)
 
UpdateUserRequestWithRole (const char *value)
 
const Aws::StringGetServerId () const
 
bool ServerIdHasBeenSet () const
 
void SetServerId (const Aws::String &value)
 
void SetServerId (Aws::String &&value)
 
void SetServerId (const char *value)
 
UpdateUserRequestWithServerId (const Aws::String &value)
 
UpdateUserRequestWithServerId (Aws::String &&value)
 
UpdateUserRequestWithServerId (const char *value)
 
const Aws::StringGetUserName () const
 
bool UserNameHasBeenSet () const
 
void SetUserName (const Aws::String &value)
 
void SetUserName (Aws::String &&value)
 
void SetUserName (const char *value)
 
UpdateUserRequestWithUserName (const Aws::String &value)
 
UpdateUserRequestWithUserName (Aws::String &&value)
 
UpdateUserRequestWithUserName (const char *value)
 
- Public Member Functions inherited from Aws::Transfer::TransferRequest
virtual ~TransferRequest ()
 
void AddParametersToRequest (Aws::Http::HttpRequest &httpRequest) const
 
Aws::Http::HeaderValueCollection GetHeaders () const override
 
- Public Member Functions inherited from Aws::AmazonSerializableWebServiceRequest
 AmazonSerializableWebServiceRequest ()
 
virtual ~AmazonSerializableWebServiceRequest ()
 
std::shared_ptr< Aws::IOStreamGetBody () const override
 
- Public Member Functions inherited from Aws::AmazonWebServiceRequest
 AmazonWebServiceRequest ()
 
virtual ~AmazonWebServiceRequest ()=default
 
virtual void AddQueryStringParameters (Aws::Http::URI &uri) const
 
virtual void PutToPresignedUrl (Aws::Http::URI &uri) const
 
virtual bool IsStreaming () const
 
virtual bool IsEventStreamRequest () const
 
virtual bool SignBody () const
 
virtual bool IsChunked () const
 
virtual void SetRequestSignedHandler (const RequestSignedHandler &handler)
 
virtual const RequestSignedHandlerGetRequestSignedHandler () const
 
const Aws::IOStreamFactoryGetResponseStreamFactory () const
 
void SetResponseStreamFactory (const Aws::IOStreamFactory &factory)
 
virtual void SetDataReceivedEventHandler (const Aws::Http::DataReceivedEventHandler &dataReceivedEventHandler)
 
virtual void SetDataSentEventHandler (const Aws::Http::DataSentEventHandler &dataSentEventHandler)
 
virtual void SetContinueRequestHandler (const Aws::Http::ContinueRequestHandler &continueRequestHandler)
 
virtual void SetDataReceivedEventHandler (Aws::Http::DataReceivedEventHandler &&dataReceivedEventHandler)
 
virtual void SetDataSentEventHandler (Aws::Http::DataSentEventHandler &&dataSentEventHandler)
 
virtual void SetContinueRequestHandler (Aws::Http::ContinueRequestHandler &&continueRequestHandler)
 
virtual void SetRequestRetryHandler (const RequestRetryHandler &handler)
 
virtual void SetRequestRetryHandler (RequestRetryHandler &&handler)
 
virtual const Aws::Http::DataReceivedEventHandlerGetDataReceivedEventHandler () const
 
virtual const Aws::Http::DataSentEventHandlerGetDataSentEventHandler () const
 
virtual const Aws::Http::ContinueRequestHandlerGetContinueRequestHandler () const
 
virtual const RequestRetryHandlerGetRequestRetryHandler () const
 
virtual bool ShouldComputeContentMd5 () const
 

Additional Inherited Members

- Protected Member Functions inherited from Aws::AmazonWebServiceRequest
virtual void DumpBodyToUrl (Aws::Http::URI &uri) const
 

Detailed Description

Definition at line 25 of file UpdateUserRequest.h.

Constructor & Destructor Documentation

◆ UpdateUserRequest()

Aws::Transfer::Model::UpdateUserRequest::UpdateUserRequest ( )

Member Function Documentation

◆ AddHomeDirectoryMappings() [1/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::AddHomeDirectoryMappings ( const HomeDirectoryMapEntry value)
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 339 of file UpdateUserRequest.h.

◆ AddHomeDirectoryMappings() [2/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::AddHomeDirectoryMappings ( HomeDirectoryMapEntry &&  value)
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 365 of file UpdateUserRequest.h.

◆ GetHomeDirectory()

const Aws::String& Aws::Transfer::Model::UpdateUserRequest::GetHomeDirectory ( ) const
inline

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.

Definition at line 46 of file UpdateUserRequest.h.

◆ GetHomeDirectoryMappings()

const Aws::Vector<HomeDirectoryMapEntry>& Aws::Transfer::Model::UpdateUserRequest::GetHomeDirectoryMappings ( ) const
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 183 of file UpdateUserRequest.h.

◆ GetHomeDirectoryType()

const HomeDirectoryType& Aws::Transfer::Model::UpdateUserRequest::GetHomeDirectoryType ( ) const
inline

The type of landing directory (folder) you want your users' home directory to be when they log into the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or EFS 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 or EFS paths visible to your users.

Definition at line 106 of file UpdateUserRequest.h.

◆ GetPolicy()

const Aws::String& Aws::Transfer::Model::UpdateUserRequest::GetPolicy ( ) const
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 384 of file UpdateUserRequest.h.

◆ GetPosixProfile()

const PosixProfile& Aws::Transfer::Model::UpdateUserRequest::GetPosixProfile ( ) const
inline

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 Elastic File Systems (Amazon EFS). The POSIX permissions that are set on files and directories in your file system determines the level of access your users get when transferring files into and out of your Amazon EFS file systems.

Definition at line 521 of file UpdateUserRequest.h.

◆ GetRequestSpecificHeaders()

Aws::Http::HeaderValueCollection Aws::Transfer::Model::UpdateUserRequest::GetRequestSpecificHeaders ( ) const
overridevirtual

Reimplemented from Aws::Transfer::TransferRequest.

◆ GetRole()

const Aws::String& Aws::Transfer::Model::UpdateUserRequest::GetRole ( ) const
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 583 of file UpdateUserRequest.h.

◆ GetServerId()

const Aws::String& Aws::Transfer::Model::UpdateUserRequest::GetServerId ( ) const
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 667 of file UpdateUserRequest.h.

◆ GetServiceRequestName()

virtual const char* Aws::Transfer::Model::UpdateUserRequest::GetServiceRequestName ( ) const
inlineoverridevirtual

Implements Aws::AmazonWebServiceRequest.

Definition at line 34 of file UpdateUserRequest.h.

◆ GetUserName()

const Aws::String& Aws::Transfer::Model::UpdateUserRequest::GetUserName ( ) const
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 719 of file UpdateUserRequest.h.

◆ HomeDirectoryHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::HomeDirectoryHasBeenSet ( ) const
inline

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.

Definition at line 53 of file UpdateUserRequest.h.

◆ HomeDirectoryMappingsHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::HomeDirectoryMappingsHasBeenSet ( ) const
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 209 of file UpdateUserRequest.h.

◆ HomeDirectoryTypeHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::HomeDirectoryTypeHasBeenSet ( ) const
inline

The type of landing directory (folder) you want your users' home directory to be when they log into the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or EFS 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 or EFS paths visible to your users.

Definition at line 116 of file UpdateUserRequest.h.

◆ PolicyHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::PolicyHasBeenSet ( ) const
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 402 of file UpdateUserRequest.h.

◆ PosixProfileHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::PosixProfileHasBeenSet ( ) const
inline

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 Elastic File Systems (Amazon EFS). The POSIX permissions that are set on files and directories in your file system determines the level of access your users get when transferring files into and out of your Amazon EFS file systems.

Definition at line 531 of file UpdateUserRequest.h.

◆ RoleHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::RoleHasBeenSet ( ) const
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 594 of file UpdateUserRequest.h.

◆ SerializePayload()

Aws::String Aws::Transfer::Model::UpdateUserRequest::SerializePayload ( ) const
overridevirtual

Convert payload into String.

Implements Aws::AmazonSerializableWebServiceRequest.

◆ ServerIdHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::ServerIdHasBeenSet ( ) const
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 673 of file UpdateUserRequest.h.

◆ SetHomeDirectory() [1/3]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectory ( Aws::String &&  value)
inline

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.

Definition at line 67 of file UpdateUserRequest.h.

◆ SetHomeDirectory() [2/3]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectory ( const Aws::String value)
inline

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.

Definition at line 60 of file UpdateUserRequest.h.

◆ SetHomeDirectory() [3/3]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectory ( const char *  value)
inline

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.

Definition at line 74 of file UpdateUserRequest.h.

◆ SetHomeDirectoryMappings() [1/2]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectoryMappings ( Aws::Vector< HomeDirectoryMapEntry > &&  value)
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 261 of file UpdateUserRequest.h.

◆ SetHomeDirectoryMappings() [2/2]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectoryMappings ( const Aws::Vector< HomeDirectoryMapEntry > &  value)
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 235 of file UpdateUserRequest.h.

◆ SetHomeDirectoryType() [1/2]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectoryType ( const HomeDirectoryType value)
inline

The type of landing directory (folder) you want your users' home directory to be when they log into the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or EFS 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 or EFS paths visible to your users.

Definition at line 126 of file UpdateUserRequest.h.

◆ SetHomeDirectoryType() [2/2]

void Aws::Transfer::Model::UpdateUserRequest::SetHomeDirectoryType ( HomeDirectoryType &&  value)
inline

The type of landing directory (folder) you want your users' home directory to be when they log into the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or EFS 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 or EFS paths visible to your users.

Definition at line 136 of file UpdateUserRequest.h.

◆ SetPolicy() [1/3]

void Aws::Transfer::Model::UpdateUserRequest::SetPolicy ( Aws::String &&  value)
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 438 of file UpdateUserRequest.h.

◆ SetPolicy() [2/3]

void Aws::Transfer::Model::UpdateUserRequest::SetPolicy ( const Aws::String value)
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 420 of file UpdateUserRequest.h.

◆ SetPolicy() [3/3]

void Aws::Transfer::Model::UpdateUserRequest::SetPolicy ( const char *  value)
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 456 of file UpdateUserRequest.h.

◆ SetPosixProfile() [1/2]

void Aws::Transfer::Model::UpdateUserRequest::SetPosixProfile ( const PosixProfile value)
inline

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 Elastic File Systems (Amazon EFS). The POSIX permissions that are set on files and directories in your file system determines the level of access your users get when transferring files into and out of your Amazon EFS file systems.

Definition at line 541 of file UpdateUserRequest.h.

◆ SetPosixProfile() [2/2]

void Aws::Transfer::Model::UpdateUserRequest::SetPosixProfile ( PosixProfile &&  value)
inline

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 Elastic File Systems (Amazon EFS). The POSIX permissions that are set on files and directories in your file system determines the level of access your users get when transferring files into and out of your Amazon EFS file systems.

Definition at line 551 of file UpdateUserRequest.h.

◆ SetRole() [1/3]

void Aws::Transfer::Model::UpdateUserRequest::SetRole ( Aws::String &&  value)
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 616 of file UpdateUserRequest.h.

◆ SetRole() [2/3]

void Aws::Transfer::Model::UpdateUserRequest::SetRole ( const Aws::String value)
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 605 of file UpdateUserRequest.h.

◆ SetRole() [3/3]

void Aws::Transfer::Model::UpdateUserRequest::SetRole ( const char *  value)
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 627 of file UpdateUserRequest.h.

◆ SetServerId() [1/3]

void Aws::Transfer::Model::UpdateUserRequest::SetServerId ( Aws::String &&  value)
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 685 of file UpdateUserRequest.h.

◆ SetServerId() [2/3]

void Aws::Transfer::Model::UpdateUserRequest::SetServerId ( const Aws::String value)
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 679 of file UpdateUserRequest.h.

◆ SetServerId() [3/3]

void Aws::Transfer::Model::UpdateUserRequest::SetServerId ( const char *  value)
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 691 of file UpdateUserRequest.h.

◆ SetUserName() [1/3]

void Aws::Transfer::Model::UpdateUserRequest::SetUserName ( Aws::String &&  value)
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 746 of file UpdateUserRequest.h.

◆ SetUserName() [2/3]

void Aws::Transfer::Model::UpdateUserRequest::SetUserName ( const Aws::String value)
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 737 of file UpdateUserRequest.h.

◆ SetUserName() [3/3]

void Aws::Transfer::Model::UpdateUserRequest::SetUserName ( const char *  value)
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 755 of file UpdateUserRequest.h.

◆ UserNameHasBeenSet()

bool Aws::Transfer::Model::UpdateUserRequest::UserNameHasBeenSet ( ) const
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 728 of file UpdateUserRequest.h.

◆ WithHomeDirectory() [1/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectory ( Aws::String &&  value)
inline

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.

Definition at line 88 of file UpdateUserRequest.h.

◆ WithHomeDirectory() [2/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectory ( const Aws::String value)
inline

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.

Definition at line 81 of file UpdateUserRequest.h.

◆ WithHomeDirectory() [3/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectory ( const char *  value)
inline

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.

Definition at line 95 of file UpdateUserRequest.h.

◆ WithHomeDirectoryMappings() [1/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectoryMappings ( Aws::Vector< HomeDirectoryMapEntry > &&  value)
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 313 of file UpdateUserRequest.h.

◆ WithHomeDirectoryMappings() [2/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectoryMappings ( const Aws::Vector< HomeDirectoryMapEntry > &  value)
inline

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 will need to specify the "<code>Entry</code>" and "<code>Target</code>" pair, where Entry shows how the path is made visible and Target is the actual Amazon S3 or Amazon EFS path. If you only specify a target, it will be displayed as is. You will need to also make sure that your 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 down your user to the designated home directory ("<code>chroot</code>"). 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 or EFS, the entry will be ignored. As a workaround, you can use the Amazon S3 API or EFS API to create 0-byte objects as place holders for your directory. If using the AWS CLI, use the s3api or efsapi call instead of s3 efs 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.

Definition at line 287 of file UpdateUserRequest.h.

◆ WithHomeDirectoryType() [1/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectoryType ( const HomeDirectoryType value)
inline

The type of landing directory (folder) you want your users' home directory to be when they log into the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or EFS 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 or EFS paths visible to your users.

Definition at line 146 of file UpdateUserRequest.h.

◆ WithHomeDirectoryType() [2/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithHomeDirectoryType ( HomeDirectoryType &&  value)
inline

The type of landing directory (folder) you want your users' home directory to be when they log into the server. If you set it to PATH, the user will see the absolute Amazon S3 bucket or EFS 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 or EFS paths visible to your users.

Definition at line 156 of file UpdateUserRequest.h.

◆ WithPolicy() [1/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithPolicy ( Aws::String &&  value)
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 492 of file UpdateUserRequest.h.

◆ WithPolicy() [2/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithPolicy ( const Aws::String value)
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 474 of file UpdateUserRequest.h.

◆ WithPolicy() [3/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithPolicy ( const char *  value)
inline

A scope-down policy for your user so that 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}.

This only applies when domain of ServerId is S3. Amazon EFS does not use scope-down policies.

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.

Definition at line 510 of file UpdateUserRequest.h.

◆ WithPosixProfile() [1/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithPosixProfile ( const PosixProfile value)
inline

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 Elastic File Systems (Amazon EFS). The POSIX permissions that are set on files and directories in your file system determines the level of access your users get when transferring files into and out of your Amazon EFS file systems.

Definition at line 561 of file UpdateUserRequest.h.

◆ WithPosixProfile() [2/2]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithPosixProfile ( PosixProfile &&  value)
inline

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 Elastic File Systems (Amazon EFS). The POSIX permissions that are set on files and directories in your file system determines the level of access your users get when transferring files into and out of your Amazon EFS file systems.

Definition at line 571 of file UpdateUserRequest.h.

◆ WithRole() [1/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithRole ( Aws::String &&  value)
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 649 of file UpdateUserRequest.h.

◆ WithRole() [2/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithRole ( const Aws::String value)
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 638 of file UpdateUserRequest.h.

◆ WithRole() [3/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithRole ( const char *  value)
inline

Specifies the Amazon Resource Name (ARN) of the IAM role that controls your users' access to your Amazon S3 bucket or 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 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.

Definition at line 660 of file UpdateUserRequest.h.

◆ WithServerId() [1/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithServerId ( Aws::String &&  value)
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 703 of file UpdateUserRequest.h.

◆ WithServerId() [2/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithServerId ( const Aws::String value)
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 697 of file UpdateUserRequest.h.

◆ WithServerId() [3/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithServerId ( const char *  value)
inline

A system-assigned unique identifier for a server instance that the user account is assigned to.

Definition at line 709 of file UpdateUserRequest.h.

◆ WithUserName() [1/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithUserName ( Aws::String &&  value)
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 773 of file UpdateUserRequest.h.

◆ WithUserName() [2/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithUserName ( const Aws::String value)
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 764 of file UpdateUserRequest.h.

◆ WithUserName() [3/3]

UpdateUserRequest& Aws::Transfer::Model::UpdateUserRequest::WithUserName ( const char *  value)
inline

A unique string that identifies a user and is associated with a server as specified by the 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.

Definition at line 782 of file UpdateUserRequest.h.


The documentation for this class was generated from the following file: