aws-sdk-transfer 1.33.0 → 1.34.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 996c86038af3aaa7227c722e3cd5354b8cdbabd132a8a36be8faac4191059588
4
- data.tar.gz: 21092ed796a8518b5992865ba1de33825c8449cbf470e17a66a51c1dcb5b48d8
3
+ metadata.gz: 115a06a68834cb675ee714dfea9ac54b95a43eb7c8c1720986ceda0c14a7fe3f
4
+ data.tar.gz: b2bbf016894bc679d1b5b1eb8e473c24e5b016fd88aafe01f69dddea76bfbeab
5
5
  SHA512:
6
- metadata.gz: b39c067e39c7125d8bac5d11be5b1275d9d11529d130bb1d693dc000d5338b985bca712c4fc9a63c1d9d18703db158ca6a59a7af691fcd86b3f3dd80a3103714
7
- data.tar.gz: a0af612b16737ff005eac0d7770203ff1251b878dec11911aff19fd9c476d15046ba18fab0a672110e96171bcebd4e37ff5f35a56e3ae477780c07e7bc5ee5ec
6
+ metadata.gz: 26db8ed0441214e7e29595e746f9d4ca36cfdebeaf0393ae6500b82abd171e0dd7eaed66d6bb5db4c264e381124fce2ffa26e9fc6321676b76c3102c974c2754
7
+ data.tar.gz: f558f493d2b8bc8e4deeb0223a0bbeb65c3e1f387bb9526b5de4e1492c1b407db804f83052e77c87c549cbfc0f399997b08e27ee667f7716a4e60abc48ce95dd
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.34.0 (2021-06-09)
5
+ ------------------
6
+
7
+ * Feature - Documentation updates for the AWS Transfer Family service.
8
+
4
9
  1.33.0 (2021-05-25)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.33.0
1
+ 1.34.0
@@ -48,6 +48,6 @@ require_relative 'aws-sdk-transfer/customizations'
48
48
  # @!group service
49
49
  module Aws::Transfer
50
50
 
51
- GEM_VERSION = '1.33.0'
51
+ GEM_VERSION = '1.34.0'
52
52
 
53
53
  end
@@ -349,15 +349,16 @@ module Aws::Transfer
349
349
  # The landing directory (folder) for a user when they log in to the
350
350
  # server using the client.
351
351
  #
352
- # A `HomeDirectory` example is `/directory_name/home/mydirectory`.
352
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
353
353
  #
354
354
  # @option params [String] :home_directory_type
355
- # The type of landing directory (folder) that you want your users' home
356
- # directory to be when they log in to the server. If you set it to
357
- # `PATH`, the user will see the absolute Amazon S3 bucket paths as is in
358
- # their file transfer protocol clients. If you set it `LOGICAL`, you
359
- # must provide mappings in the `HomeDirectoryMappings` for how you want
360
- # to make Amazon S3 paths visible to your users.
355
+ # The type of landing directory (folder) you want your users' home
356
+ # directory to be when they log into the server. If you set it to
357
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
358
+ # as is in their file transfer protocol clients. If you set it
359
+ # `LOGICAL`, you will need to provide mappings in the
360
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
361
+ # paths visible to your users.
361
362
  #
362
363
  # @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
363
364
  # Logical directory mappings that specify what Amazon S3 or Amazon EFS
@@ -398,8 +399,6 @@ module Aws::Transfer
398
399
  #
399
400
  # </note>
400
401
  #
401
- # Required: No
402
- #
403
402
  # @option params [String] :policy
404
403
  # A scope-down policy for your user so that you can use the same IAM
405
404
  # role across multiple users. This policy scopes down user access to
@@ -408,7 +407,7 @@ module Aws::Transfer
408
407
  # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
409
408
  #
410
409
  # <note markdown="1"> This only applies when domain of `ServerId` is S3. Amazon EFS does not
411
- # use scope down policy.
410
+ # use scope-down policies.
412
411
  #
413
412
  # For scope-down policies, AWS Transfer Family stores the policy as a
414
413
  # JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
@@ -437,13 +436,13 @@ module Aws::Transfer
437
436
  # out of your Amazon EFS file systems.
438
437
  #
439
438
  # @option params [required, String] :role
440
- # Specifies the IAM role that controls your users' access to your
441
- # Amazon S3 bucket or EFS file system. The policies attached to this
442
- # role determine the level of access that you want to provide your users
443
- # when transferring files into and out of your Amazon S3 bucket or EFS
444
- # file system. The IAM role should also contain a trust relationship
445
- # that allows the server to access your resources when servicing your
446
- # users' transfer requests.
439
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that controls
440
+ # your users' access to your Amazon S3 bucket or EFS file system. The
441
+ # policies attached to this role determine the level of access that you
442
+ # want to provide your users when transferring files into and out of
443
+ # your Amazon S3 bucket or EFS file system. The IAM role should also
444
+ # contain a trust relationship that allows the server to access your
445
+ # resources when servicing your users' transfer requests.
447
446
  #
448
447
  # @option params [required, String] :server_id
449
448
  # A system-assigned unique identifier for a server instance. This is the
@@ -458,7 +457,7 @@ module Aws::Transfer
458
457
  # PowerShell.
459
458
  #
460
459
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
461
- # -Properties * | Select SamaccountName,ObjectSid`
460
+ # -Properties * | Select SamAccountName,ObjectSid`
462
461
  #
463
462
  # In that command, replace *YourGroupName* with the name of your Active
464
463
  # Directory group.
@@ -580,12 +579,12 @@ module Aws::Transfer
580
579
  # choose to make it internet facing by attaching Elastic IP addresses
581
580
  # directly to it.
582
581
  #
583
- # <note markdown="1"> After March 31, 2021, you won't be able to create a server using
582
+ # <note markdown="1"> After May 19, 2021, you won't be able to create a server using
584
583
  # `EndpointType=VPC_ENDPOINT` in your AWS account if your account
585
- # hasn't already done so before March 31, 2021. If you have already
584
+ # hasn't already done so before May 19, 2021. If you have already
586
585
  # created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
587
- # on or before March 31, 2021, you will not be affected. After this
588
- # date, use `EndpointType`=`VPC`.
586
+ # on or before May 19, 2021, you will not be affected. After this date,
587
+ # use `EndpointType`=`VPC`.
589
588
  #
590
589
  # For more information, see
591
590
  # https://docs.aws.amazon.com/transfer/latest/userguide/create-server-in-vpc.html#deprecate-vpc-endpoint.
@@ -742,10 +741,11 @@ module Aws::Transfer
742
741
  # @option params [String] :home_directory_type
743
742
  # The type of landing directory (folder) you want your users' home
744
743
  # directory to be when they log into the server. If you set it to
745
- # `PATH`, the user will see the absolute Amazon S3 bucket paths as is in
746
- # their file transfer protocol clients. If you set it `LOGICAL`, you
747
- # will need to provide mappings in the `HomeDirectoryMappings` for how
748
- # you want to make Amazon S3 paths visible to your users.
744
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
745
+ # as is in their file transfer protocol clients. If you set it
746
+ # `LOGICAL`, you will need to provide mappings in the
747
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
748
+ # paths visible to your users.
749
749
  #
750
750
  # @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
751
751
  # Logical directory mappings that specify what Amazon S3 or EFS paths
@@ -783,10 +783,10 @@ module Aws::Transfer
783
783
  # </note>
784
784
  #
785
785
  # @option params [String] :policy
786
- # A scope-down policy for your user so you can use the same IAM role
787
- # across multiple users. This policy scopes down user access to portions
788
- # of their Amazon S3 bucket. Variables that you can use inside this
789
- # policy include `$\{Transfer:UserName\}`,
786
+ # A scope-down policy for your user so that you can use the same IAM
787
+ # role across multiple users. This policy scopes down user access to
788
+ # portions of their Amazon S3 bucket. Variables that you can use inside
789
+ # this policy include `$\{Transfer:UserName\}`,
790
790
  # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
791
791
  #
792
792
  # <note markdown="1"> This only applies when domain of ServerId is S3. EFS does not use
@@ -819,13 +819,13 @@ module Aws::Transfer
819
819
  # into and out of your Amazon EFS file systems.
820
820
  #
821
821
  # @option params [required, String] :role
822
- # Specifies the IAM role that controls your users' access to your
823
- # Amazon S3 bucket or EFS file system. The policies attached to this
824
- # role will determine the level of access you want to provide your users
825
- # when transferring files into and out of your Amazon S3 bucket or EFS
826
- # file system. The IAM role should also contain a trust relationship
827
- # that allows the server to access your resources when servicing your
828
- # users' transfer requests.
822
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that controls
823
+ # your users' access to your Amazon S3 bucket or EFS file system. The
824
+ # policies attached to this role determine the level of access that you
825
+ # want to provide your users when transferring files into and out of
826
+ # your Amazon S3 bucket or EFS file system. The IAM role should also
827
+ # contain a trust relationship that allows the server to access your
828
+ # resources when servicing your users' transfer requests.
829
829
  #
830
830
  # @option params [required, String] :server_id
831
831
  # A system-assigned unique identifier for a server instance. This is the
@@ -911,7 +911,7 @@ module Aws::Transfer
911
911
  # PowerShell.
912
912
  #
913
913
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
914
- # -Properties * | Select SamaccountName,ObjectSid`
914
+ # -Properties * | Select SamAccountName,ObjectSid`
915
915
  #
916
916
  # In that command, replace *YourGroupName* with the name of your Active
917
917
  # Directory group.
@@ -1045,14 +1045,14 @@ module Aws::Transfer
1045
1045
  #
1046
1046
  # @option params [required, String] :external_id
1047
1047
  # A unique identifier that is required to identify specific groups
1048
- # within your directory. The users of the group you associate have
1048
+ # within your directory. The users of the group that you associate have
1049
1049
  # access to your Amazon S3 or Amazon EFS resources over the enabled
1050
1050
  # protocols using AWS Transfer Family. If you know the group name, you
1051
1051
  # can view the SID values by running the following command using Windows
1052
1052
  # PowerShell.
1053
1053
  #
1054
1054
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
1055
- # -Properties * | Select SamaccountName,ObjectSid`
1055
+ # -Properties * | Select SamAccountName,ObjectSid`
1056
1056
  #
1057
1057
  # In that command, replace *YourGroupName* with the name of your Active
1058
1058
  # Directory group.
@@ -1766,15 +1766,16 @@ module Aws::Transfer
1766
1766
  # The landing directory (folder) for a user when they log in to the
1767
1767
  # server using the client.
1768
1768
  #
1769
- # A `HomeDirectory` example is `/directory_name/home/mydirectory`.
1769
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
1770
1770
  #
1771
1771
  # @option params [String] :home_directory_type
1772
- # The type of landing directory (folder) that you want your users' home
1773
- # directory to be when they log in to the server. If you set it to
1774
- # `PATH`, the user will see the absolute Amazon S3 bucket paths as is in
1775
- # their file transfer protocol clients. If you set it `LOGICAL`, you
1776
- # must provide mappings in the `HomeDirectoryMappings` for how you want
1777
- # to make Amazon S3 paths visible to your users.
1772
+ # The type of landing directory (folder) you want your users' home
1773
+ # directory to be when they log into the server. If you set it to
1774
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
1775
+ # as is in their file transfer protocol clients. If you set it
1776
+ # `LOGICAL`, you will need to provide mappings in the
1777
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
1778
+ # paths visible to your users.
1778
1779
  #
1779
1780
  # @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
1780
1781
  # Logical directory mappings that specify what Amazon S3 or Amazon EFS
@@ -1815,8 +1816,6 @@ module Aws::Transfer
1815
1816
  #
1816
1817
  # </note>
1817
1818
  #
1818
- # Required: No
1819
- #
1820
1819
  # @option params [String] :policy
1821
1820
  # A scope-down policy for your user so that you can use the same IAM
1822
1821
  # role across multiple users. This policy scopes down user access to
@@ -1854,13 +1853,13 @@ module Aws::Transfer
1854
1853
  # out of your Amazon EFS file systems.
1855
1854
  #
1856
1855
  # @option params [String] :role
1857
- # Specifies the IAM role that controls your users' access to your
1858
- # Amazon S3 bucket or EFS file system. The policies attached to this
1859
- # role determine the level of access that you want to provide your users
1860
- # when transferring files into and out of your Amazon S3 bucket or EFS
1861
- # file system. The IAM role should also contain a trust relationship
1862
- # that allows the server to access your resources when servicing your
1863
- # users' transfer requests.
1856
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that controls
1857
+ # your users' access to your Amazon S3 bucket or EFS file system. The
1858
+ # policies attached to this role determine the level of access that you
1859
+ # want to provide your users when transferring files into and out of
1860
+ # your Amazon S3 bucket or EFS file system. The IAM role should also
1861
+ # contain a trust relationship that allows the server to access your
1862
+ # resources when servicing your users' transfer requests.
1864
1863
  #
1865
1864
  # @option params [required, String] :server_id
1866
1865
  # A system-assigned unique identifier for a server instance. This is the
@@ -1875,7 +1874,7 @@ module Aws::Transfer
1875
1874
  # PowerShell.
1876
1875
  #
1877
1876
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
1878
- # -Properties * | Select SamaccountName,ObjectSid`
1877
+ # -Properties * | Select SamAccountName,ObjectSid`
1879
1878
  #
1880
1879
  # In that command, replace *YourGroupName* with the name of your Active
1881
1880
  # Directory group.
@@ -1986,12 +1985,12 @@ module Aws::Transfer
1986
1985
  # choose to make it internet facing by attaching Elastic IP addresses
1987
1986
  # directly to it.
1988
1987
  #
1989
- # <note markdown="1"> After March 31, 2021, you won't be able to create a server using
1988
+ # <note markdown="1"> After May 19, 2021, you won't be able to create a server using
1990
1989
  # `EndpointType=VPC_ENDPOINT` in your AWS account if your account
1991
- # hasn't already done so before March 31, 2021. If you have already
1990
+ # hasn't already done so before May 19, 2021. If you have already
1992
1991
  # created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
1993
- # on or before March 31, 2021, you will not be affected. After this
1994
- # date, use `EndpointType`=`VPC`.
1992
+ # on or before May 19, 2021, you will not be affected. After this date,
1993
+ # use `EndpointType`=`VPC`.
1995
1994
  #
1996
1995
  # For more information, see
1997
1996
  # https://docs.aws.amazon.com/transfer/latest/userguide/create-server-in-vpc.html#deprecate-vpc-endpoint.
@@ -2116,10 +2115,10 @@ module Aws::Transfer
2116
2115
  # user.
2117
2116
  #
2118
2117
  # @option params [String] :home_directory
2119
- # Specifies the landing directory (folder) for a user when they log in
2120
- # to the server using their file transfer protocol client.
2118
+ # The landing directory (folder) for a user when they log in to the
2119
+ # server using the client.
2121
2120
  #
2122
- # An example is `your-Amazon-S3-bucket-name>/home/username`.
2121
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
2123
2122
  #
2124
2123
  # @option params [String] :home_directory_type
2125
2124
  # The type of landing directory (folder) you want your users' home
@@ -2161,13 +2160,16 @@ module Aws::Transfer
2161
2160
  # </note>
2162
2161
  #
2163
2162
  # @option params [String] :policy
2164
- # Allows you to supply a scope-down policy for your user so you can use
2165
- # the same IAM role across multiple users. The policy scopes down user
2166
- # access to portions of your Amazon S3 bucket. Variables you can use
2167
- # inside this policy include `$\{Transfer:UserName\}`,
2163
+ # A scope-down policy for your user so that you can use the same IAM
2164
+ # role across multiple users. This policy scopes down user access to
2165
+ # portions of their Amazon S3 bucket. Variables that you can use inside
2166
+ # this policy include `$\{Transfer:UserName\}`,
2168
2167
  # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
2169
2168
  #
2170
- # <note markdown="1"> For scope-down policies, AWS Transfer Family stores the policy as a
2169
+ # <note markdown="1"> This only applies when domain of `ServerId` is S3. Amazon EFS does not
2170
+ # use scope-down policies.
2171
+ #
2172
+ # For scope-down policies, AWS Transfer Family stores the policy as a
2171
2173
  # JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
2172
2174
  # You save the policy as a JSON blob and pass it in the `Policy`
2173
2175
  # argument.
@@ -2194,12 +2196,13 @@ module Aws::Transfer
2194
2196
  # transferring files into and out of your Amazon EFS file systems.
2195
2197
  #
2196
2198
  # @option params [String] :role
2197
- # The IAM role that controls your users' access to your Amazon S3
2198
- # bucket. The policies attached to this role determine the level of
2199
- # access you want to provide your users when transferring files into and
2200
- # out of your S3 bucket or buckets. The IAM role should also contain a
2201
- # trust relationship that allows the server to access your resources
2202
- # when servicing your users' transfer requests.
2199
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that controls
2200
+ # your users' access to your Amazon S3 bucket or EFS file system. The
2201
+ # policies attached to this role determine the level of access that you
2202
+ # want to provide your users when transferring files into and out of
2203
+ # your Amazon S3 bucket or EFS file system. The IAM role should also
2204
+ # contain a trust relationship that allows the server to access your
2205
+ # resources when servicing your users' transfer requests.
2203
2206
  #
2204
2207
  # @option params [required, String] :server_id
2205
2208
  # A system-assigned unique identifier for a server instance that the
@@ -2267,7 +2270,7 @@ module Aws::Transfer
2267
2270
  params: params,
2268
2271
  config: config)
2269
2272
  context[:gem_name] = 'aws-sdk-transfer'
2270
- context[:gem_version] = '1.33.0'
2273
+ context[:gem_version] = '1.34.0'
2271
2274
  Seahorse::Client::Request.new(handlers, context)
2272
2275
  end
2273
2276
 
@@ -65,16 +65,17 @@ module Aws::Transfer
65
65
  # The landing directory (folder) for a user when they log in to the
66
66
  # server using the client.
67
67
  #
68
- # A `HomeDirectory` example is `/directory_name/home/mydirectory`.
68
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
69
69
  # @return [String]
70
70
  #
71
71
  # @!attribute [rw] home_directory_type
72
- # The type of landing directory (folder) that you want your users'
73
- # home directory to be when they log in to the server. If you set it
74
- # to `PATH`, the user will see the absolute Amazon S3 bucket paths as
75
- # is in their file transfer protocol clients. If you set it `LOGICAL`,
76
- # you must provide mappings in the `HomeDirectoryMappings` for how you
77
- # want to make Amazon S3 paths visible to your users.
72
+ # The type of landing directory (folder) you want your users' home
73
+ # directory to be when they log into the server. If you set it to
74
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
75
+ # as is in their file transfer protocol clients. If you set it
76
+ # `LOGICAL`, you will need to provide mappings in the
77
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
78
+ # paths visible to your users.
78
79
  # @return [String]
79
80
  #
80
81
  # @!attribute [rw] home_directory_mappings
@@ -115,8 +116,6 @@ module Aws::Transfer
115
116
  # folder.
116
117
  #
117
118
  # </note>
118
- #
119
- # Required: No
120
119
  # @return [Array<Types::HomeDirectoryMapEntry>]
121
120
  #
122
121
  # @!attribute [rw] policy
@@ -127,7 +126,7 @@ module Aws::Transfer
127
126
  # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
128
127
  #
129
128
  # <note markdown="1"> This only applies when domain of `ServerId` is S3. Amazon EFS does
130
- # not use scope down policy.
129
+ # not use scope-down policies.
131
130
  #
132
131
  # For scope-down policies, AWS Transfer Family stores the policy as a
133
132
  # JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
@@ -158,13 +157,14 @@ module Aws::Transfer
158
157
  # @return [Types::PosixProfile]
159
158
  #
160
159
  # @!attribute [rw] role
161
- # Specifies the IAM role that controls your users' access to your
162
- # Amazon S3 bucket or EFS file system. The policies attached to this
163
- # role determine the level of access that you want to provide your
164
- # users when transferring files into and out of your Amazon S3 bucket
165
- # or EFS file system. The IAM role should also contain a trust
166
- # relationship that allows the server to access your resources when
167
- # servicing your users' transfer requests.
160
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
161
+ # controls your users' access to your Amazon S3 bucket or EFS file
162
+ # system. The policies attached to this role determine the level of
163
+ # access that you want to provide your users when transferring files
164
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
165
+ # role should also contain a trust relationship that allows the server
166
+ # to access your resources when servicing your users' transfer
167
+ # requests.
168
168
  # @return [String]
169
169
  #
170
170
  # @!attribute [rw] server_id
@@ -181,7 +181,7 @@ module Aws::Transfer
181
181
  # using Windows PowerShell.
182
182
  #
183
183
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
184
- # -Properties * | Select SamaccountName,ObjectSid`
184
+ # -Properties * | Select SamAccountName,ObjectSid`
185
185
  #
186
186
  # In that command, replace *YourGroupName* with the name of your
187
187
  # Active Directory group.
@@ -326,11 +326,11 @@ module Aws::Transfer
326
326
  # within your VPC or choose to make it internet facing by attaching
327
327
  # Elastic IP addresses directly to it.
328
328
  #
329
- # <note markdown="1"> After March 31, 2021, you won't be able to create a server using
329
+ # <note markdown="1"> After May 19, 2021, you won't be able to create a server using
330
330
  # `EndpointType=VPC_ENDPOINT` in your AWS account if your account
331
- # hasn't already done so before March 31, 2021. If you have already
331
+ # hasn't already done so before May 19, 2021. If you have already
332
332
  # created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
333
- # on or before March 31, 2021, you will not be affected. After this
333
+ # on or before May 19, 2021, you will not be affected. After this
334
334
  # date, use `EndpointType`=`VPC`.
335
335
  #
336
336
  # For more information, see
@@ -501,10 +501,11 @@ module Aws::Transfer
501
501
  # @!attribute [rw] home_directory_type
502
502
  # The type of landing directory (folder) you want your users' home
503
503
  # directory to be when they log into the server. If you set it to
504
- # `PATH`, the user will see the absolute Amazon S3 bucket paths as is
505
- # in their file transfer protocol clients. If you set it `LOGICAL`,
506
- # you will need to provide mappings in the `HomeDirectoryMappings` for
507
- # how you want to make Amazon S3 paths visible to your users.
504
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
505
+ # as is in their file transfer protocol clients. If you set it
506
+ # `LOGICAL`, you will need to provide mappings in the
507
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
508
+ # paths visible to your users.
508
509
  # @return [String]
509
510
  #
510
511
  # @!attribute [rw] home_directory_mappings
@@ -544,8 +545,8 @@ module Aws::Transfer
544
545
  # @return [Array<Types::HomeDirectoryMapEntry>]
545
546
  #
546
547
  # @!attribute [rw] policy
547
- # A scope-down policy for your user so you can use the same IAM role
548
- # across multiple users. This policy scopes down user access to
548
+ # A scope-down policy for your user so that you can use the same IAM
549
+ # role across multiple users. This policy scopes down user access to
549
550
  # portions of their Amazon S3 bucket. Variables that you can use
550
551
  # inside this policy include `$\{Transfer:UserName\}`,
551
552
  # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
@@ -582,13 +583,14 @@ module Aws::Transfer
582
583
  # @return [Types::PosixProfile]
583
584
  #
584
585
  # @!attribute [rw] role
585
- # Specifies the IAM role that controls your users' access to your
586
- # Amazon S3 bucket or EFS file system. The policies attached to this
587
- # role will determine the level of access you want to provide your
588
- # users when transferring files into and out of your Amazon S3 bucket
589
- # or EFS file system. The IAM role should also contain a trust
590
- # relationship that allows the server to access your resources when
591
- # servicing your users' transfer requests.
586
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
587
+ # controls your users' access to your Amazon S3 bucket or EFS file
588
+ # system. The policies attached to this role determine the level of
589
+ # access that you want to provide your users when transferring files
590
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
591
+ # role should also contain a trust relationship that allows the server
592
+ # to access your resources when servicing your users' transfer
593
+ # requests.
592
594
  # @return [String]
593
595
  #
594
596
  # @!attribute [rw] server_id
@@ -672,7 +674,7 @@ module Aws::Transfer
672
674
  # using Windows PowerShell.
673
675
  #
674
676
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
675
- # -Properties * | Select SamaccountName,ObjectSid`
677
+ # -Properties * | Select SamAccountName,ObjectSid`
676
678
  #
677
679
  # In that command, replace *YourGroupName* with the name of your
678
680
  # Active Directory group.
@@ -786,14 +788,14 @@ module Aws::Transfer
786
788
  #
787
789
  # @!attribute [rw] external_id
788
790
  # A unique identifier that is required to identify specific groups
789
- # within your directory. The users of the group you associate have
790
- # access to your Amazon S3 or Amazon EFS resources over the enabled
791
- # protocols using AWS Transfer Family. If you know the group name, you
792
- # can view the SID values by running the following command using
793
- # Windows PowerShell.
791
+ # within your directory. The users of the group that you associate
792
+ # have access to your Amazon S3 or Amazon EFS resources over the
793
+ # enabled protocols using AWS Transfer Family. If you know the group
794
+ # name, you can view the SID values by running the following command
795
+ # using Windows PowerShell.
794
796
  #
795
797
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
796
- # -Properties * | Select SamaccountName,ObjectSid`
798
+ # -Properties * | Select SamAccountName,ObjectSid`
797
799
  #
798
800
  # In that command, replace *YourGroupName* with the name of your
799
801
  # Active Directory group.
@@ -945,9 +947,10 @@ module Aws::Transfer
945
947
  # Describes the properties of the access that was specified.
946
948
  #
947
949
  # @!attribute [rw] home_directory
948
- # Specifies the landing directory (or folder), which is the location
949
- # that files are written to or read from in an Amazon S3 bucket, for
950
- # the described access.
950
+ # The landing directory (folder) for a user when they log in to the
951
+ # server using the client.
952
+ #
953
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
951
954
  # @return [String]
952
955
  #
953
956
  # @!attribute [rw] home_directory_mappings
@@ -967,21 +970,21 @@ module Aws::Transfer
967
970
  # @return [Array<Types::HomeDirectoryMapEntry>]
968
971
  #
969
972
  # @!attribute [rw] home_directory_type
970
- # The type of landing directory (folder) that you want your users'
971
- # home directory to be when they log in to the server. If you set it
972
- # to `PATH`, the user will see the absolute Amazon S3 bucket paths as
973
- # is in their file transfer protocol clients. If you set it to
974
- # `LOGICAL`, you must provide mappings in the `HomeDirectoryMappings`
975
- # for how you want to make Amazon S3 paths visible to your users.
973
+ # The type of landing directory (folder) you want your users' home
974
+ # directory to be when they log into the server. If you set it to
975
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
976
+ # as is in their file transfer protocol clients. If you set it
977
+ # `LOGICAL`, you will need to provide mappings in the
978
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
979
+ # paths visible to your users.
976
980
  # @return [String]
977
981
  #
978
982
  # @!attribute [rw] policy
979
- # A scope-down policy for your user so that you can use the same AWS
980
- # Identity and Access Management (IAM) role across multiple users.
981
- # This policy scopes down user access to portions of their Amazon S3
982
- # bucket. Variables that you can use inside this policy include
983
- # `$\{Transfer:UserName\}`, `$\{Transfer:HomeDirectory\}`, and
984
- # `$\{Transfer:HomeBucket\}`.
983
+ # A scope-down policy for your user so that you can use the same IAM
984
+ # role across multiple users. This policy scopes down user access to
985
+ # portions of their Amazon S3 bucket. Variables that you can use
986
+ # inside this policy include `$\{Transfer:UserName\}`,
987
+ # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
985
988
  # @return [String]
986
989
  #
987
990
  # @!attribute [rw] posix_profile
@@ -994,27 +997,29 @@ module Aws::Transfer
994
997
  # @return [Types::PosixProfile]
995
998
  #
996
999
  # @!attribute [rw] role
997
- # The IAM role that controls access to your Amazon S3 bucket from the
998
- # specified associated access. The policies attached to this role will
999
- # determine the level of access that you want to provide the
1000
- # associated access when transferring files into and out of your
1001
- # Amazon S3 bucket or buckets. The IAM role should also contain a
1002
- # trust relationship that allows a server to access your resources
1003
- # when servicing transfer requests for the associated access.
1000
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
1001
+ # controls your users' access to your Amazon S3 bucket or EFS file
1002
+ # system. The policies attached to this role determine the level of
1003
+ # access that you want to provide your users when transferring files
1004
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
1005
+ # role should also contain a trust relationship that allows the server
1006
+ # to access your resources when servicing your users' transfer
1007
+ # requests.
1004
1008
  # @return [String]
1005
1009
  #
1006
1010
  # @!attribute [rw] external_id
1007
- # A unique identifier that might be required when you assume a role in
1008
- # another account. Think of the `ExternalID` as a group membership
1009
- # mechanism that uses a unique identifier (often a SID, but could be a
1010
- # group name or something else) as a basis. If the administrator of
1011
- # the account to which the role belongs provided you with an external
1012
- # ID, then provide that value in the `ExternalId` parameter. A
1013
- # cross-account role is usually set up to trust everyone in an
1014
- # account. Therefore, the administrator of the trusting account might
1015
- # send an external ID to the administrator of the trusted account.
1016
- # That way, only someone with the ID can assume the role, rather than
1017
- # everyone in the account.
1011
+ # A unique identifier that is required to identify specific groups
1012
+ # within your directory. The users of the group that you associate
1013
+ # have access to your Amazon S3 or Amazon EFS resources over the
1014
+ # enabled protocols using AWS Transfer Family. If you know the group
1015
+ # name, you can view the SID values by running the following command
1016
+ # using Windows PowerShell.
1017
+ #
1018
+ # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
1019
+ # -Properties * | Select SamAccountName,ObjectSid`
1020
+ #
1021
+ # In that command, replace *YourGroupName* with the name of your
1022
+ # Active Directory group.
1018
1023
  #
1019
1024
  # The regex used to validate this parameter is a string of characters
1020
1025
  # consisting of uppercase and lowercase alphanumeric characters with
@@ -1224,10 +1229,10 @@ module Aws::Transfer
1224
1229
  # @return [String]
1225
1230
  #
1226
1231
  # @!attribute [rw] home_directory
1227
- # Specifies the landing directory (or folder), which is the location
1228
- # that files are written to or read from in an Amazon S3 bucket, for
1229
- # the described user. An example is <i>
1230
- # <code>your-Amazon-S3-bucket-name&gt;/home/username</code> </i>.
1232
+ # The landing directory (folder) for a user when they log in to the
1233
+ # server using the client.
1234
+ #
1235
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
1231
1236
  # @return [String]
1232
1237
  #
1233
1238
  # @!attribute [rw] home_directory_mappings
@@ -1247,17 +1252,21 @@ module Aws::Transfer
1247
1252
  # @return [Array<Types::HomeDirectoryMapEntry>]
1248
1253
  #
1249
1254
  # @!attribute [rw] home_directory_type
1250
- # Specifies the type of landing directory (folder) you mapped for your
1251
- # users to see when they log into the file transfer protocol-enabled
1252
- # server. If you set it to `PATH`, the user will see the absolute
1253
- # Amazon S3 bucket or EFS paths as is in their file transfer protocol
1254
- # clients. If you set it `LOGICAL`, you will need to provide mappings
1255
- # in the `HomeDirectoryMappings` for how you want to make Amazon S3 or
1256
- # EFS paths visible to your users.
1255
+ # The type of landing directory (folder) you want your users' home
1256
+ # directory to be when they log into the server. If you set it to
1257
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
1258
+ # as is in their file transfer protocol clients. If you set it
1259
+ # `LOGICAL`, you will need to provide mappings in the
1260
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
1261
+ # paths visible to your users.
1257
1262
  # @return [String]
1258
1263
  #
1259
1264
  # @!attribute [rw] policy
1260
- # Specifies the name of the policy in use for the described user.
1265
+ # A scope-down policy for your user so that you can use the same IAM
1266
+ # role across multiple users. This policy scopes down user access to
1267
+ # portions of their Amazon S3 bucket. Variables that you can use
1268
+ # inside this policy include `$\{Transfer:UserName\}`,
1269
+ # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
1261
1270
  # @return [String]
1262
1271
  #
1263
1272
  # @!attribute [rw] posix_profile
@@ -1271,12 +1280,14 @@ module Aws::Transfer
1271
1280
  # @return [Types::PosixProfile]
1272
1281
  #
1273
1282
  # @!attribute [rw] role
1274
- # The IAM role that controls your users' access to your Amazon S3
1275
- # bucket. The policies attached to this role will determine the level
1276
- # of access you want to provide your users when transferring files
1277
- # into and out of your Amazon S3 bucket or buckets. The IAM role
1278
- # should also contain a trust relationship that allows a server to
1279
- # access your resources when servicing your users' transfer requests.
1283
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
1284
+ # controls your users' access to your Amazon S3 bucket or EFS file
1285
+ # system. The policies attached to this role determine the level of
1286
+ # access that you want to provide your users when transferring files
1287
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
1288
+ # role should also contain a trust relationship that allows the server
1289
+ # to access your resources when servicing your users' transfer
1290
+ # requests.
1280
1291
  # @return [String]
1281
1292
  #
1282
1293
  # @!attribute [rw] ssh_public_keys
@@ -1318,12 +1329,12 @@ module Aws::Transfer
1318
1329
  # VPC. To control incoming internet traffic, invoke the `UpdateServer`
1319
1330
  # API and attach an Elastic IP address to your server's endpoint.
1320
1331
  #
1321
- # <note markdown="1"> After March 31, 2021, you won't be able to create a server using
1332
+ # <note markdown="1"> After May 19, 2021, you won't be able to create a server using
1322
1333
  # `EndpointType=VPC_ENDPOINT` in your AWS account if your account
1323
- # hasn't already done so before March 31, 2021. If you have already
1334
+ # hasn't already done so before May 19, 2021. If you have already
1324
1335
  # created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
1325
- # on or before March 31, 2021, you will not be affected. After this
1326
- # date, use `EndpointType`=`VPC`.
1336
+ # on or before May 19, 2021, you will not be affected. After this date,
1337
+ # use `EndpointType`=`VPC`.
1327
1338
  #
1328
1339
  # For more information, see
1329
1340
  # https://docs.aws.amazon.com/transfer/latest/userguide/create-server-in-vpc.html#deprecate-vpc-endpoint.
@@ -1866,43 +1877,46 @@ module Aws::Transfer
1866
1877
  # Lists the properties for one or more specified associated accesses.
1867
1878
  #
1868
1879
  # @!attribute [rw] home_directory
1869
- # Specifies the landing directory (or folder), which is the location
1870
- # that files are written to or read from in an Amazon S3 bucket, for
1871
- # the described access.
1880
+ # The landing directory (folder) for a user when they log in to the
1881
+ # server using the client.
1882
+ #
1883
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
1872
1884
  # @return [String]
1873
1885
  #
1874
1886
  # @!attribute [rw] home_directory_type
1875
- # The type of landing directory (folder) that you want your users'
1876
- # home directory to be when they log in to the server. If you set it
1877
- # to `PATH`, the user will see the absolute Amazon S3 bucket paths as
1878
- # is in their file transfer protocol clients. If you set it to
1879
- # `LOGICAL`, you must provide mappings in the `HomeDirectoryMappings`
1880
- # for how you want to make Amazon S3 paths visible to your users.
1887
+ # The type of landing directory (folder) you want your users' home
1888
+ # directory to be when they log into the server. If you set it to
1889
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
1890
+ # as is in their file transfer protocol clients. If you set it
1891
+ # `LOGICAL`, you will need to provide mappings in the
1892
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
1893
+ # paths visible to your users.
1881
1894
  # @return [String]
1882
1895
  #
1883
1896
  # @!attribute [rw] role
1884
- # The AWS Identity and Access Management (IAM) role that controls
1885
- # access to your Amazon S3 bucket from the specified associated
1886
- # access. The policies attached to this role will determine the level
1887
- # of access that you want to provide the associated access when
1888
- # transferring files into and out of your Amazon S3 bucket or buckets.
1889
- # The IAM role should also contain a trust relationship that allows a
1890
- # server to access your resources when servicing transfer requests for
1891
- # the associated access.
1897
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
1898
+ # controls your users' access to your Amazon S3 bucket or EFS file
1899
+ # system. The policies attached to this role determine the level of
1900
+ # access that you want to provide your users when transferring files
1901
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
1902
+ # role should also contain a trust relationship that allows the server
1903
+ # to access your resources when servicing your users' transfer
1904
+ # requests.
1892
1905
  # @return [String]
1893
1906
  #
1894
1907
  # @!attribute [rw] external_id
1895
- # A unique identifier that might be required when you assume a role in
1896
- # another account. Think of the `ExternalID` as a group membership
1897
- # mechanism that uses a unique identifier (often a SID, but could be a
1898
- # group name or something else) as a basis. If the administrator of
1899
- # the account to which the role belongs provided you with an external
1900
- # ID, then provide that value in the `ExternalId` parameter. A
1901
- # cross-account role is usually set up to trust everyone in an
1902
- # account. Therefore, the administrator of the trusting account might
1903
- # send an external ID to the administrator of the trusted account.
1904
- # That way, only someone with the ID can assume the role, rather than
1905
- # everyone in the account.
1908
+ # A unique identifier that is required to identify specific groups
1909
+ # within your directory. The users of the group that you associate
1910
+ # have access to your Amazon S3 or Amazon EFS resources over the
1911
+ # enabled protocols using AWS Transfer Family. If you know the group
1912
+ # name, you can view the SID values by running the following command
1913
+ # using Windows PowerShell.
1914
+ #
1915
+ # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
1916
+ # -Properties * | Select SamAccountName,ObjectSid`
1917
+ #
1918
+ # In that command, replace *YourGroupName* with the name of your
1919
+ # Active Directory group.
1906
1920
  #
1907
1921
  # The regex used to validate this parameter is a string of characters
1908
1922
  # consisting of uppercase and lowercase alphanumeric characters with
@@ -1997,26 +2011,31 @@ module Aws::Transfer
1997
2011
  # @return [String]
1998
2012
  #
1999
2013
  # @!attribute [rw] home_directory
2000
- # Specifies the location that files are written to or read from an
2001
- # Amazon S3 bucket for the user you specify by their ARN.
2014
+ # The landing directory (folder) for a user when they log in to the
2015
+ # server using the client.
2016
+ #
2017
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
2002
2018
  # @return [String]
2003
2019
  #
2004
2020
  # @!attribute [rw] home_directory_type
2005
- # Specifies the type of landing directory (folder) you mapped for your
2006
- # users' home directory. If you set it to `PATH`, the user will see
2007
- # the absolute Amazon S3 bucket paths as is in their file transfer
2008
- # protocol clients. If you set it `LOGICAL`, you will need to provide
2009
- # mappings in the `HomeDirectoryMappings` for how you want to make
2010
- # Amazon S3 paths visible to your users.
2021
+ # The type of landing directory (folder) you want your users' home
2022
+ # directory to be when they log into the server. If you set it to
2023
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
2024
+ # as is in their file transfer protocol clients. If you set it
2025
+ # `LOGICAL`, you will need to provide mappings in the
2026
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
2027
+ # paths visible to your users.
2011
2028
  # @return [String]
2012
2029
  #
2013
2030
  # @!attribute [rw] role
2014
- # Specifies the role that is in use by this user. A *role* is an AWS
2015
- # Identity and Access Management (IAM) entity that, in this case,
2016
- # allows a file transfer protocol-enabled server to act on a user's
2017
- # behalf. It allows the server to inherit the trust relationship that
2018
- # enables that user to perform file operations to their Amazon S3
2019
- # bucket.
2031
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
2032
+ # controls your users' access to your Amazon S3 bucket or EFS file
2033
+ # system. The policies attached to this role determine the level of
2034
+ # access that you want to provide your users when transferring files
2035
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
2036
+ # role should also contain a trust relationship that allows the server
2037
+ # to access your resources when servicing your users' transfer
2038
+ # requests.
2020
2039
  #
2021
2040
  # <note markdown="1"> The IAM role that controls your users' access to your Amazon S3
2022
2041
  # bucket for servers with `Domain=S3`, or your EFS file system for
@@ -2434,16 +2453,17 @@ module Aws::Transfer
2434
2453
  # The landing directory (folder) for a user when they log in to the
2435
2454
  # server using the client.
2436
2455
  #
2437
- # A `HomeDirectory` example is `/directory_name/home/mydirectory`.
2456
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
2438
2457
  # @return [String]
2439
2458
  #
2440
2459
  # @!attribute [rw] home_directory_type
2441
- # The type of landing directory (folder) that you want your users'
2442
- # home directory to be when they log in to the server. If you set it
2443
- # to `PATH`, the user will see the absolute Amazon S3 bucket paths as
2444
- # is in their file transfer protocol clients. If you set it `LOGICAL`,
2445
- # you must provide mappings in the `HomeDirectoryMappings` for how you
2446
- # want to make Amazon S3 paths visible to your users.
2460
+ # The type of landing directory (folder) you want your users' home
2461
+ # directory to be when they log into the server. If you set it to
2462
+ # `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
2463
+ # as is in their file transfer protocol clients. If you set it
2464
+ # `LOGICAL`, you will need to provide mappings in the
2465
+ # `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
2466
+ # paths visible to your users.
2447
2467
  # @return [String]
2448
2468
  #
2449
2469
  # @!attribute [rw] home_directory_mappings
@@ -2484,8 +2504,6 @@ module Aws::Transfer
2484
2504
  # folder.
2485
2505
  #
2486
2506
  # </note>
2487
- #
2488
- # Required: No
2489
2507
  # @return [Array<Types::HomeDirectoryMapEntry>]
2490
2508
  #
2491
2509
  # @!attribute [rw] policy
@@ -2527,13 +2545,14 @@ module Aws::Transfer
2527
2545
  # @return [Types::PosixProfile]
2528
2546
  #
2529
2547
  # @!attribute [rw] role
2530
- # Specifies the IAM role that controls your users' access to your
2531
- # Amazon S3 bucket or EFS file system. The policies attached to this
2532
- # role determine the level of access that you want to provide your
2533
- # users when transferring files into and out of your Amazon S3 bucket
2534
- # or EFS file system. The IAM role should also contain a trust
2535
- # relationship that allows the server to access your resources when
2536
- # servicing your users' transfer requests.
2548
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
2549
+ # controls your users' access to your Amazon S3 bucket or EFS file
2550
+ # system. The policies attached to this role determine the level of
2551
+ # access that you want to provide your users when transferring files
2552
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
2553
+ # role should also contain a trust relationship that allows the server
2554
+ # to access your resources when servicing your users' transfer
2555
+ # requests.
2537
2556
  # @return [String]
2538
2557
  #
2539
2558
  # @!attribute [rw] server_id
@@ -2550,7 +2569,7 @@ module Aws::Transfer
2550
2569
  # using Windows PowerShell.
2551
2570
  #
2552
2571
  # `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
2553
- # -Properties * | Select SamaccountName,ObjectSid`
2572
+ # -Properties * | Select SamAccountName,ObjectSid`
2554
2573
  #
2555
2574
  # In that command, replace *YourGroupName* with the name of your
2556
2575
  # Active Directory group.
@@ -2676,11 +2695,11 @@ module Aws::Transfer
2676
2695
  # within your VPC or choose to make it internet facing by attaching
2677
2696
  # Elastic IP addresses directly to it.
2678
2697
  #
2679
- # <note markdown="1"> After March 31, 2021, you won't be able to create a server using
2698
+ # <note markdown="1"> After May 19, 2021, you won't be able to create a server using
2680
2699
  # `EndpointType=VPC_ENDPOINT` in your AWS account if your account
2681
- # hasn't already done so before March 31, 2021. If you have already
2700
+ # hasn't already done so before May 19, 2021. If you have already
2682
2701
  # created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
2683
- # on or before March 31, 2021, you will not be affected. After this
2702
+ # on or before May 19, 2021, you will not be affected. After this
2684
2703
  # date, use `EndpointType`=`VPC`.
2685
2704
  #
2686
2705
  # For more information, see
@@ -2817,10 +2836,10 @@ module Aws::Transfer
2817
2836
  # }
2818
2837
  #
2819
2838
  # @!attribute [rw] home_directory
2820
- # Specifies the landing directory (folder) for a user when they log in
2821
- # to the server using their file transfer protocol client.
2839
+ # The landing directory (folder) for a user when they log in to the
2840
+ # server using the client.
2822
2841
  #
2823
- # An example is `your-Amazon-S3-bucket-name>/home/username`.
2842
+ # A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
2824
2843
  # @return [String]
2825
2844
  #
2826
2845
  # @!attribute [rw] home_directory_type
@@ -2865,13 +2884,16 @@ module Aws::Transfer
2865
2884
  # @return [Array<Types::HomeDirectoryMapEntry>]
2866
2885
  #
2867
2886
  # @!attribute [rw] policy
2868
- # Allows you to supply a scope-down policy for your user so you can
2869
- # use the same IAM role across multiple users. The policy scopes down
2870
- # user access to portions of your Amazon S3 bucket. Variables you can
2871
- # use inside this policy include `$\{Transfer:UserName\}`,
2887
+ # A scope-down policy for your user so that you can use the same IAM
2888
+ # role across multiple users. This policy scopes down user access to
2889
+ # portions of their Amazon S3 bucket. Variables that you can use
2890
+ # inside this policy include `$\{Transfer:UserName\}`,
2872
2891
  # `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
2873
2892
  #
2874
- # <note markdown="1"> For scope-down policies, AWS Transfer Family stores the policy as a
2893
+ # <note markdown="1"> This only applies when domain of `ServerId` is S3. Amazon EFS does
2894
+ # not use scope-down policies.
2895
+ #
2896
+ # For scope-down policies, AWS Transfer Family stores the policy as a
2875
2897
  # JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
2876
2898
  # You save the policy as a JSON blob and pass it in the `Policy`
2877
2899
  # argument.
@@ -2901,12 +2923,14 @@ module Aws::Transfer
2901
2923
  # @return [Types::PosixProfile]
2902
2924
  #
2903
2925
  # @!attribute [rw] role
2904
- # The IAM role that controls your users' access to your Amazon S3
2905
- # bucket. The policies attached to this role determine the level of
2906
- # access you want to provide your users when transferring files into
2907
- # and out of your S3 bucket or buckets. The IAM role should also
2908
- # contain a trust relationship that allows the server to access your
2909
- # resources when servicing your users' transfer requests.
2926
+ # Specifies the Amazon Resource Name (ARN) of the IAM role that
2927
+ # controls your users' access to your Amazon S3 bucket or EFS file
2928
+ # system. The policies attached to this role determine the level of
2929
+ # access that you want to provide your users when transferring files
2930
+ # into and out of your Amazon S3 bucket or EFS file system. The IAM
2931
+ # role should also contain a trust relationship that allows the server
2932
+ # to access your resources when servicing your users' transfer
2933
+ # requests.
2910
2934
  # @return [String]
2911
2935
  #
2912
2936
  # @!attribute [rw] server_id
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-transfer
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.33.0
4
+ version: 1.34.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2021-05-25 00:00:00.000000000 Z
11
+ date: 2021-06-09 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core