aws-sdk-transfer 1.29.0 → 1.34.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +183 -0
- data/LICENSE.txt +202 -0
- data/VERSION +1 -0
- data/lib/aws-sdk-transfer.rb +3 -3
- data/lib/aws-sdk-transfer/client.rb +680 -110
- data/lib/aws-sdk-transfer/client_api.rb +152 -1
- data/lib/aws-sdk-transfer/errors.rb +1 -1
- data/lib/aws-sdk-transfer/resource.rb +1 -1
- data/lib/aws-sdk-transfer/types.rb +997 -155
- metadata +11 -9
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 115a06a68834cb675ee714dfea9ac54b95a43eb7c8c1720986ceda0c14a7fe3f
|
|
4
|
+
data.tar.gz: b2bbf016894bc679d1b5b1eb8e473c24e5b016fd88aafe01f69dddea76bfbeab
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 26db8ed0441214e7e29595e746f9d4ca36cfdebeaf0393ae6500b82abd171e0dd7eaed66d6bb5db4c264e381124fce2ffa26e9fc6321676b76c3102c974c2754
|
|
7
|
+
data.tar.gz: f558f493d2b8bc8e4deeb0223a0bbeb65c3e1f387bb9526b5de4e1492c1b407db804f83052e77c87c549cbfc0f399997b08e27ee667f7716a4e60abc48ce95dd
|
data/CHANGELOG.md
ADDED
|
@@ -0,0 +1,183 @@
|
|
|
1
|
+
Unreleased Changes
|
|
2
|
+
------------------
|
|
3
|
+
|
|
4
|
+
1.34.0 (2021-06-09)
|
|
5
|
+
------------------
|
|
6
|
+
|
|
7
|
+
* Feature - Documentation updates for the AWS Transfer Family service.
|
|
8
|
+
|
|
9
|
+
1.33.0 (2021-05-25)
|
|
10
|
+
------------------
|
|
11
|
+
|
|
12
|
+
* Feature - AWS Transfer Family customers can now use AWS Managed Active Directory or AD Connector to authenticate their end users, enabling seamless migration of file transfer workflows that rely on AD authentication, without changing end users' credentials or needing a custom authorizer.
|
|
13
|
+
|
|
14
|
+
1.32.0 (2021-03-10)
|
|
15
|
+
------------------
|
|
16
|
+
|
|
17
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
18
|
+
|
|
19
|
+
1.31.0 (2021-02-25)
|
|
20
|
+
------------------
|
|
21
|
+
|
|
22
|
+
* Feature - Corrected the upper limit for TestIdentityProvider input lengths to 1024 characters
|
|
23
|
+
|
|
24
|
+
1.30.0 (2021-02-02)
|
|
25
|
+
------------------
|
|
26
|
+
|
|
27
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
28
|
+
|
|
29
|
+
1.29.0 (2021-01-06)
|
|
30
|
+
------------------
|
|
31
|
+
|
|
32
|
+
* Feature - This release adds support for Amazon EFS, so customers can transfer files over SFTP, FTPS and FTP in and out of Amazon S3 as well as Amazon EFS.
|
|
33
|
+
|
|
34
|
+
1.28.0 (2020-10-15)
|
|
35
|
+
------------------
|
|
36
|
+
|
|
37
|
+
* Feature - Add support to associate VPC Security Groups at server creation.
|
|
38
|
+
|
|
39
|
+
1.27.0 (2020-09-30)
|
|
40
|
+
------------------
|
|
41
|
+
|
|
42
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
43
|
+
|
|
44
|
+
1.26.0 (2020-09-15)
|
|
45
|
+
------------------
|
|
46
|
+
|
|
47
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
48
|
+
|
|
49
|
+
1.25.0 (2020-08-25)
|
|
50
|
+
------------------
|
|
51
|
+
|
|
52
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
53
|
+
|
|
54
|
+
1.24.0 (2020-08-12)
|
|
55
|
+
------------------
|
|
56
|
+
|
|
57
|
+
* Feature - Adds security policies to control cryptographic algorithms advertised by your server, additional characters in usernames and length increase, and FIPS compliant endpoints in the US and Canada regions.
|
|
58
|
+
|
|
59
|
+
1.23.0 (2020-06-23)
|
|
60
|
+
------------------
|
|
61
|
+
|
|
62
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
63
|
+
|
|
64
|
+
1.22.1 (2020-06-11)
|
|
65
|
+
------------------
|
|
66
|
+
|
|
67
|
+
* Issue - Republish previous version with correct dependency on `aws-sdk-core`.
|
|
68
|
+
|
|
69
|
+
1.22.0 (2020-06-10)
|
|
70
|
+
------------------
|
|
71
|
+
|
|
72
|
+
* Issue - This version has been yanked. (#2327).
|
|
73
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
74
|
+
|
|
75
|
+
1.21.0 (2020-06-09)
|
|
76
|
+
------------------
|
|
77
|
+
|
|
78
|
+
* Feature - This release updates the API so customers can test use of Source IP to allow, deny or limit access to data in their S3 buckets after integrating their identity provider.
|
|
79
|
+
|
|
80
|
+
1.20.0 (2020-05-28)
|
|
81
|
+
------------------
|
|
82
|
+
|
|
83
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
84
|
+
|
|
85
|
+
1.19.0 (2020-05-07)
|
|
86
|
+
------------------
|
|
87
|
+
|
|
88
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
89
|
+
|
|
90
|
+
1.18.0 (2020-04-23)
|
|
91
|
+
------------------
|
|
92
|
+
|
|
93
|
+
* Feature - This release adds support for transfers over FTPS and FTP in and out of Amazon S3, which makes it easy to migrate File Transfer Protocol over SSL (FTPS) and FTP workloads to AWS, in addition to the existing support for Secure File Transfer Protocol (SFTP).
|
|
94
|
+
|
|
95
|
+
1.17.0 (2020-03-09)
|
|
96
|
+
------------------
|
|
97
|
+
|
|
98
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
99
|
+
|
|
100
|
+
1.16.0 (2020-01-10)
|
|
101
|
+
------------------
|
|
102
|
+
|
|
103
|
+
* Feature - This release introduces a new endpoint type that allows you to attach Elastic IP addresses from your AWS account with your server's endpoint directly and whitelist access to your server by client's internet IP address(es) using VPC Security Groups.
|
|
104
|
+
|
|
105
|
+
1.15.0 (2019-10-28)
|
|
106
|
+
------------------
|
|
107
|
+
|
|
108
|
+
* Feature - This release adds logical directories support to your AWS SFTP server endpoint, so you can now create logical directory structures mapped to Amazon Simple Storage Service (Amazon S3) bucket paths for users created and stored within the service. Amazon S3 bucket names and paths can now be hidden from AWS SFTP users, providing an additional level of privacy to meet security requirements. You can lock down your SFTP users' access to designated folders (commonly referred to as 'chroot'), and simplify complex folder structures for data distribution through SFTP without replicating files across multiple users.
|
|
109
|
+
|
|
110
|
+
1.14.0 (2019-10-23)
|
|
111
|
+
------------------
|
|
112
|
+
|
|
113
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
114
|
+
|
|
115
|
+
1.13.0 (2019-08-20)
|
|
116
|
+
------------------
|
|
117
|
+
|
|
118
|
+
* Feature - New field in response of TestIdentityProvider
|
|
119
|
+
|
|
120
|
+
1.12.0 (2019-07-25)
|
|
121
|
+
------------------
|
|
122
|
+
|
|
123
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
124
|
+
|
|
125
|
+
1.11.0 (2019-07-01)
|
|
126
|
+
------------------
|
|
127
|
+
|
|
128
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
129
|
+
|
|
130
|
+
1.10.0 (2019-06-17)
|
|
131
|
+
------------------
|
|
132
|
+
|
|
133
|
+
* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
|
|
134
|
+
|
|
135
|
+
1.9.0 (2019-05-21)
|
|
136
|
+
------------------
|
|
137
|
+
|
|
138
|
+
* Feature - API update.
|
|
139
|
+
|
|
140
|
+
1.8.0 (2019-05-15)
|
|
141
|
+
------------------
|
|
142
|
+
|
|
143
|
+
* Feature - API update.
|
|
144
|
+
|
|
145
|
+
1.7.0 (2019-05-14)
|
|
146
|
+
------------------
|
|
147
|
+
|
|
148
|
+
* Feature - API update.
|
|
149
|
+
|
|
150
|
+
1.6.0 (2019-04-29)
|
|
151
|
+
------------------
|
|
152
|
+
|
|
153
|
+
* Feature - API update.
|
|
154
|
+
|
|
155
|
+
1.5.0 (2019-03-27)
|
|
156
|
+
------------------
|
|
157
|
+
|
|
158
|
+
* Feature - API update.
|
|
159
|
+
|
|
160
|
+
1.4.0 (2019-03-21)
|
|
161
|
+
------------------
|
|
162
|
+
|
|
163
|
+
* Feature - API update.
|
|
164
|
+
|
|
165
|
+
1.3.0 (2019-03-18)
|
|
166
|
+
------------------
|
|
167
|
+
|
|
168
|
+
* Feature - API update.
|
|
169
|
+
|
|
170
|
+
1.2.0 (2019-03-14)
|
|
171
|
+
------------------
|
|
172
|
+
|
|
173
|
+
* Feature - API update.
|
|
174
|
+
|
|
175
|
+
1.1.0 (2019-02-21)
|
|
176
|
+
------------------
|
|
177
|
+
|
|
178
|
+
* Feature - API update.
|
|
179
|
+
|
|
180
|
+
1.0.0 (2018-11-26)
|
|
181
|
+
------------------
|
|
182
|
+
|
|
183
|
+
* Feature - Initial release of `aws-sdk-transfer`.
|
data/LICENSE.txt
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
data/VERSION
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
1.34.0
|
data/lib/aws-sdk-transfer.rb
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
# WARNING ABOUT GENERATED CODE
|
|
4
4
|
#
|
|
5
5
|
# This file is generated. See the contributing guide for more information:
|
|
6
|
-
# https://github.com/aws/aws-sdk-ruby/blob/
|
|
6
|
+
# https://github.com/aws/aws-sdk-ruby/blob/version-3/CONTRIBUTING.md
|
|
7
7
|
#
|
|
8
8
|
# WARNING ABOUT GENERATED CODE
|
|
9
9
|
|
|
@@ -28,7 +28,7 @@ require_relative 'aws-sdk-transfer/customizations'
|
|
|
28
28
|
# structure.
|
|
29
29
|
#
|
|
30
30
|
# transfer = Aws::Transfer::Client.new
|
|
31
|
-
# resp = transfer.
|
|
31
|
+
# resp = transfer.create_access(params)
|
|
32
32
|
#
|
|
33
33
|
# See {Client} for more information.
|
|
34
34
|
#
|
|
@@ -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.
|
|
51
|
+
GEM_VERSION = '1.34.0'
|
|
52
52
|
|
|
53
53
|
end
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
# WARNING ABOUT GENERATED CODE
|
|
4
4
|
#
|
|
5
5
|
# This file is generated. See the contributing guide for more information:
|
|
6
|
-
# https://github.com/aws/aws-sdk-ruby/blob/
|
|
6
|
+
# https://github.com/aws/aws-sdk-ruby/blob/version-3/CONTRIBUTING.md
|
|
7
7
|
#
|
|
8
8
|
# WARNING ABOUT GENERATED CODE
|
|
9
9
|
|
|
@@ -337,7 +337,178 @@ module Aws::Transfer
|
|
|
337
337
|
|
|
338
338
|
# @!group API Operations
|
|
339
339
|
|
|
340
|
-
#
|
|
340
|
+
# Used by administrators to choose which groups in the directory should
|
|
341
|
+
# have access to upload and download files over the enabled protocols
|
|
342
|
+
# using AWS Transfer Family. For example, a Microsoft Active Directory
|
|
343
|
+
# might contain 50,000 users, but only a small fraction might need the
|
|
344
|
+
# ability to transfer files to the server. An administrator can use
|
|
345
|
+
# `CreateAccess` to limit the access to the correct set of users who
|
|
346
|
+
# need this ability.
|
|
347
|
+
#
|
|
348
|
+
# @option params [String] :home_directory
|
|
349
|
+
# The landing directory (folder) for a user when they log in to the
|
|
350
|
+
# server using the client.
|
|
351
|
+
#
|
|
352
|
+
# A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
|
|
353
|
+
#
|
|
354
|
+
# @option params [String] :home_directory_type
|
|
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.
|
|
362
|
+
#
|
|
363
|
+
# @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
|
|
364
|
+
# Logical directory mappings that specify what Amazon S3 or Amazon EFS
|
|
365
|
+
# paths and keys should be visible to your user and how you want to make
|
|
366
|
+
# them visible. You must specify the `Entry` and `Target` pair, where
|
|
367
|
+
# `Entry` shows how the path is made visible and `Target` is the actual
|
|
368
|
+
# Amazon S3 or Amazon EFS path. If you only specify a target, it will be
|
|
369
|
+
# displayed as is. You also must ensure that your AWS Identity and
|
|
370
|
+
# Access Management (IAM) role provides access to paths in `Target`.
|
|
371
|
+
# This value can only be set when `HomeDirectoryType` is set to
|
|
372
|
+
# *LOGICAL*.
|
|
373
|
+
#
|
|
374
|
+
# The following is an `Entry` and `Target` pair example.
|
|
375
|
+
#
|
|
376
|
+
# `[ \{ "Entry": "your-personal-report.pdf", "Target":
|
|
377
|
+
# "/bucket3/customized-reports/$\{transfer:UserName\}.pdf" \} ]`
|
|
378
|
+
#
|
|
379
|
+
# In most cases, you can use this value instead of the scope-down policy
|
|
380
|
+
# to lock down your user to the designated home directory
|
|
381
|
+
# ("`chroot`"). To do this, you can set `Entry` to `/` and set
|
|
382
|
+
# `Target` to the `HomeDirectory` parameter value.
|
|
383
|
+
#
|
|
384
|
+
# The following is an `Entry` and `Target` pair example for `chroot`.
|
|
385
|
+
#
|
|
386
|
+
# `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
|
|
387
|
+
#
|
|
388
|
+
# <note markdown="1"> If the target of a logical directory entry does not exist in Amazon S3
|
|
389
|
+
# or Amazon EFS, the entry will be ignored. As a workaround, you can use
|
|
390
|
+
# the Amazon S3 API or EFS API to create 0-byte objects as place holders
|
|
391
|
+
# for your directory. If using the AWS CLI, use the `s3api` or `efsapi`
|
|
392
|
+
# call instead of `s3` or `efs` so you can use the `put-object`
|
|
393
|
+
# operation. For example, you can use the following.
|
|
394
|
+
#
|
|
395
|
+
# `aws s3api put-object --bucket bucketname --key path/to/folder/`
|
|
396
|
+
#
|
|
397
|
+
# The end of the key name must end in a `/` for it to be considered a
|
|
398
|
+
# folder.
|
|
399
|
+
#
|
|
400
|
+
# </note>
|
|
401
|
+
#
|
|
402
|
+
# @option params [String] :policy
|
|
403
|
+
# A scope-down policy for your user so that you can use the same IAM
|
|
404
|
+
# role across multiple users. This policy scopes down user access to
|
|
405
|
+
# portions of their Amazon S3 bucket. Variables that you can use inside
|
|
406
|
+
# this policy include `$\{Transfer:UserName\}`,
|
|
407
|
+
# `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
|
|
408
|
+
#
|
|
409
|
+
# <note markdown="1"> This only applies when domain of `ServerId` is S3. Amazon EFS does not
|
|
410
|
+
# use scope-down policies.
|
|
411
|
+
#
|
|
412
|
+
# For scope-down policies, AWS Transfer Family stores the policy as a
|
|
413
|
+
# JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
|
|
414
|
+
# You save the policy as a JSON blob and pass it in the `Policy`
|
|
415
|
+
# argument.
|
|
416
|
+
#
|
|
417
|
+
# For an example of a scope-down policy, see [Example scope-down
|
|
418
|
+
# policy][1].
|
|
419
|
+
#
|
|
420
|
+
# For more information, see [AssumeRole][2] in the *AWS Security Token
|
|
421
|
+
# Service API Reference*.
|
|
422
|
+
#
|
|
423
|
+
# </note>
|
|
424
|
+
#
|
|
425
|
+
#
|
|
426
|
+
#
|
|
427
|
+
# [1]: https://docs.aws.amazon.com/transfer/latest/userguide/scope-down-policy.html
|
|
428
|
+
# [2]: https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html
|
|
429
|
+
#
|
|
430
|
+
# @option params [Types::PosixProfile] :posix_profile
|
|
431
|
+
# The full POSIX identity, including user ID (`Uid`), group ID (`Gid`),
|
|
432
|
+
# and any secondary groups IDs (`SecondaryGids`), that controls your
|
|
433
|
+
# users' access to your Amazon EFS file systems. The POSIX permissions
|
|
434
|
+
# that are set on files and directories in your file system determine
|
|
435
|
+
# the level of access your users get when transferring files into and
|
|
436
|
+
# out of your Amazon EFS file systems.
|
|
437
|
+
#
|
|
438
|
+
# @option params [required, String] :role
|
|
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.
|
|
446
|
+
#
|
|
447
|
+
# @option params [required, String] :server_id
|
|
448
|
+
# A system-assigned unique identifier for a server instance. This is the
|
|
449
|
+
# specific server that you added your user to.
|
|
450
|
+
#
|
|
451
|
+
# @option params [required, String] :external_id
|
|
452
|
+
# A unique identifier that is required to identify specific groups
|
|
453
|
+
# within your directory. The users of the group that you associate have
|
|
454
|
+
# access to your Amazon S3 or Amazon EFS resources over the enabled
|
|
455
|
+
# protocols using AWS Transfer Family. If you know the group name, you
|
|
456
|
+
# can view the SID values by running the following command using Windows
|
|
457
|
+
# PowerShell.
|
|
458
|
+
#
|
|
459
|
+
# `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
|
|
460
|
+
# -Properties * | Select SamAccountName,ObjectSid`
|
|
461
|
+
#
|
|
462
|
+
# In that command, replace *YourGroupName* with the name of your Active
|
|
463
|
+
# Directory group.
|
|
464
|
+
#
|
|
465
|
+
# The regex used to validate this parameter is a string of characters
|
|
466
|
+
# consisting of uppercase and lowercase alphanumeric characters with no
|
|
467
|
+
# spaces. You can also include underscores or any of the following
|
|
468
|
+
# characters: =,.@:/-
|
|
469
|
+
#
|
|
470
|
+
# @return [Types::CreateAccessResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
|
|
471
|
+
#
|
|
472
|
+
# * {Types::CreateAccessResponse#server_id #server_id} => String
|
|
473
|
+
# * {Types::CreateAccessResponse#external_id #external_id} => String
|
|
474
|
+
#
|
|
475
|
+
# @example Request syntax with placeholder values
|
|
476
|
+
#
|
|
477
|
+
# resp = client.create_access({
|
|
478
|
+
# home_directory: "HomeDirectory",
|
|
479
|
+
# home_directory_type: "PATH", # accepts PATH, LOGICAL
|
|
480
|
+
# home_directory_mappings: [
|
|
481
|
+
# {
|
|
482
|
+
# entry: "MapEntry", # required
|
|
483
|
+
# target: "MapTarget", # required
|
|
484
|
+
# },
|
|
485
|
+
# ],
|
|
486
|
+
# policy: "Policy",
|
|
487
|
+
# posix_profile: {
|
|
488
|
+
# uid: 1, # required
|
|
489
|
+
# gid: 1, # required
|
|
490
|
+
# secondary_gids: [1],
|
|
491
|
+
# },
|
|
492
|
+
# role: "Role", # required
|
|
493
|
+
# server_id: "ServerId", # required
|
|
494
|
+
# external_id: "ExternalId", # required
|
|
495
|
+
# })
|
|
496
|
+
#
|
|
497
|
+
# @example Response structure
|
|
498
|
+
#
|
|
499
|
+
# resp.server_id #=> String
|
|
500
|
+
# resp.external_id #=> String
|
|
501
|
+
#
|
|
502
|
+
# @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/CreateAccess AWS API Documentation
|
|
503
|
+
#
|
|
504
|
+
# @overload create_access(params = {})
|
|
505
|
+
# @param [Hash] params ({})
|
|
506
|
+
def create_access(params = {}, options = {})
|
|
507
|
+
req = build_request(:create_access, params)
|
|
508
|
+
req.send_request(options)
|
|
509
|
+
end
|
|
510
|
+
|
|
511
|
+
# Instantiates an auto-scaling virtual server based on the selected file
|
|
341
512
|
# transfer protocol in AWS. When you make updates to your file transfer
|
|
342
513
|
# protocol-enabled server or when you work with users, use the
|
|
343
514
|
# service-generated `ServerId` property that is assigned to the newly
|
|
@@ -383,22 +554,42 @@ module Aws::Transfer
|
|
|
383
554
|
# [3]: https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-private.html
|
|
384
555
|
#
|
|
385
556
|
# @option params [String] :domain
|
|
557
|
+
# The domain of the storage system that is used for file transfers.
|
|
558
|
+
# There are two domains available: Amazon Simple Storage Service (Amazon
|
|
559
|
+
# S3) and Amazon Elastic File System (Amazon EFS). The default value is
|
|
560
|
+
# S3.
|
|
561
|
+
#
|
|
562
|
+
# <note markdown="1"> After the server is created, the domain cannot be changed.
|
|
563
|
+
#
|
|
564
|
+
# </note>
|
|
386
565
|
#
|
|
387
566
|
# @option params [Types::EndpointDetails] :endpoint_details
|
|
388
567
|
# The virtual private cloud (VPC) endpoint settings that are configured
|
|
389
568
|
# for your server. When you host your endpoint within your VPC, you can
|
|
390
569
|
# make it accessible only to resources within your VPC, or you can
|
|
391
|
-
# attach Elastic
|
|
570
|
+
# attach Elastic IP addresses and make it accessible to clients over the
|
|
392
571
|
# internet. Your VPC's default security groups are automatically
|
|
393
572
|
# assigned to your endpoint.
|
|
394
573
|
#
|
|
395
574
|
# @option params [String] :endpoint_type
|
|
396
|
-
# The type of
|
|
397
|
-
#
|
|
398
|
-
# VPC endpoint
|
|
399
|
-
# only within your VPC
|
|
400
|
-
#
|
|
401
|
-
#
|
|
575
|
+
# The type of endpoint that you want your server to use. You can choose
|
|
576
|
+
# to make your server's endpoint publicly accessible (PUBLIC) or host
|
|
577
|
+
# it inside your VPC. With an endpoint that is hosted in a VPC, you can
|
|
578
|
+
# restrict access to your server and resources only within your VPC or
|
|
579
|
+
# choose to make it internet facing by attaching Elastic IP addresses
|
|
580
|
+
# directly to it.
|
|
581
|
+
#
|
|
582
|
+
# <note markdown="1"> After May 19, 2021, you won't be able to create a server using
|
|
583
|
+
# `EndpointType=VPC_ENDPOINT` in your AWS account if your account
|
|
584
|
+
# hasn't already done so before May 19, 2021. If you have already
|
|
585
|
+
# created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
|
|
586
|
+
# on or before May 19, 2021, you will not be affected. After this date,
|
|
587
|
+
# use `EndpointType`=`VPC`.
|
|
588
|
+
#
|
|
589
|
+
# For more information, see
|
|
590
|
+
# https://docs.aws.amazon.com/transfer/latest/userguide/create-server-in-vpc.html#deprecate-vpc-endpoint.
|
|
591
|
+
#
|
|
592
|
+
# It is recommended that you use `VPC` as the `EndpointType`. With this
|
|
402
593
|
# endpoint type, you have the option to directly associate up to three
|
|
403
594
|
# Elastic IPv4 addresses (BYO IP included) with your server's endpoint
|
|
404
595
|
# and use VPC security groups to restrict traffic by the client's
|
|
@@ -423,19 +614,25 @@ module Aws::Transfer
|
|
|
423
614
|
# [1]: https://docs.aws.amazon.com/transfer/latest/userguide/edit-server-config.html#configuring-servers-change-host-key
|
|
424
615
|
#
|
|
425
616
|
# @option params [Types::IdentityProviderDetails] :identity_provider_details
|
|
426
|
-
# Required when `IdentityProviderType` is set to `
|
|
427
|
-
# an array containing all of the information
|
|
617
|
+
# Required when `IdentityProviderType` is set to `AWS_DIRECTORY_SERVICE`
|
|
618
|
+
# or `API_GATEWAY`. Accepts an array containing all of the information
|
|
619
|
+
# required to use a directory in `AWS_DIRECTORY_SERVICE` or invoke a
|
|
428
620
|
# customer-supplied authentication API, including the API Gateway URL.
|
|
429
621
|
# Not required when `IdentityProviderType` is set to `SERVICE_MANAGED`.
|
|
430
622
|
#
|
|
431
623
|
# @option params [String] :identity_provider_type
|
|
432
624
|
# Specifies the mode of authentication for a server. The default value
|
|
433
625
|
# is `SERVICE_MANAGED`, which allows you to store and access user
|
|
434
|
-
# credentials within the AWS Transfer Family service. Use
|
|
435
|
-
# `
|
|
436
|
-
#
|
|
437
|
-
#
|
|
438
|
-
#
|
|
626
|
+
# credentials within the AWS Transfer Family service. Use
|
|
627
|
+
# `AWS_DIRECTORY_SERVICE` to provide access to Active Directory groups
|
|
628
|
+
# in AWS Managed Active Directory or Microsoft Active Directory in your
|
|
629
|
+
# on-premises environment or in AWS using AD Connectors. This option
|
|
630
|
+
# also requires you to provide a Directory ID using the
|
|
631
|
+
# `IdentityProviderDetails` parameter. Use the `API_GATEWAY` value to
|
|
632
|
+
# integrate with an identity provider of your choosing. The
|
|
633
|
+
# `API_GATEWAY` setting requires you to provide an API Gateway endpoint
|
|
634
|
+
# URL to call for authentication using the `IdentityProviderDetails`
|
|
635
|
+
# parameter.
|
|
439
636
|
#
|
|
440
637
|
# @option params [String] :logging_role
|
|
441
638
|
# Allows the service to write your users' activity to your Amazon
|
|
@@ -459,7 +656,8 @@ module Aws::Transfer
|
|
|
459
656
|
# when clients connect to it over FTPS.
|
|
460
657
|
#
|
|
461
658
|
# If `Protocol` includes either `FTP` or `FTPS`, then the `EndpointType`
|
|
462
|
-
# must be `VPC` and the `IdentityProviderType` must be
|
|
659
|
+
# must be `VPC` and the `IdentityProviderType` must be
|
|
660
|
+
# `AWS_DIRECTORY_SERVICE` or `API_GATEWAY`.
|
|
463
661
|
#
|
|
464
662
|
# If `Protocol` includes `FTP`, then `AddressAllocationIds` cannot be
|
|
465
663
|
# associated.
|
|
@@ -498,8 +696,9 @@ module Aws::Transfer
|
|
|
498
696
|
# identity_provider_details: {
|
|
499
697
|
# url: "Url",
|
|
500
698
|
# invocation_role: "Role",
|
|
699
|
+
# directory_id: "DirectoryId",
|
|
501
700
|
# },
|
|
502
|
-
# identity_provider_type: "SERVICE_MANAGED", # accepts SERVICE_MANAGED, API_GATEWAY
|
|
701
|
+
# identity_provider_type: "SERVICE_MANAGED", # accepts SERVICE_MANAGED, API_GATEWAY, AWS_DIRECTORY_SERVICE
|
|
503
702
|
# logging_role: "Role",
|
|
504
703
|
# protocols: ["SFTP"], # accepts SFTP, FTP, FTPS
|
|
505
704
|
# security_policy_name: "SecurityPolicyName",
|
|
@@ -537,59 +736,68 @@ module Aws::Transfer
|
|
|
537
736
|
# The landing directory (folder) for a user when they log in to the
|
|
538
737
|
# server using the client.
|
|
539
738
|
#
|
|
540
|
-
#
|
|
541
|
-
# <code>your-Amazon-S3-bucket-name>/home/username</code> </i>.
|
|
739
|
+
# A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
|
|
542
740
|
#
|
|
543
741
|
# @option params [String] :home_directory_type
|
|
544
742
|
# The type of landing directory (folder) you want your users' home
|
|
545
743
|
# directory to be when they log into the server. If you set it to
|
|
546
|
-
# `PATH`, the user will see the absolute Amazon S3 bucket
|
|
547
|
-
# their file transfer protocol clients. If you set it
|
|
548
|
-
# will need to provide mappings in the
|
|
549
|
-
# you want to make Amazon S3
|
|
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.
|
|
550
749
|
#
|
|
551
750
|
# @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
|
|
552
|
-
# Logical directory mappings that specify what Amazon S3
|
|
553
|
-
# should be visible to your user and how you want to make them
|
|
554
|
-
# You will need to specify the
|
|
751
|
+
# Logical directory mappings that specify what Amazon S3 or EFS paths
|
|
752
|
+
# and keys should be visible to your user and how you want to make them
|
|
753
|
+
# visible. You will need to specify the `Entry` and `Target` pair, where
|
|
555
754
|
# `Entry` shows how the path is made visible and `Target` is the actual
|
|
556
|
-
# Amazon S3 path. If you only specify a target, it will be
|
|
557
|
-
# is. You will need to also make sure that your IAM role
|
|
558
|
-
# to paths in `Target`.
|
|
755
|
+
# Amazon S3 or EFS path. If you only specify a target, it will be
|
|
756
|
+
# displayed as is. You will need to also make sure that your IAM role
|
|
757
|
+
# provides access to paths in `Target`. This value can only be set when
|
|
758
|
+
# `HomeDirectoryType` is set to `LOGICAL`.
|
|
559
759
|
#
|
|
560
|
-
#
|
|
561
|
-
#
|
|
562
|
-
#
|
|
760
|
+
# The following is an `Entry` and `Target` pair example.
|
|
761
|
+
#
|
|
762
|
+
# `[ \{ "Entry": "your-personal-report.pdf", "Target":
|
|
763
|
+
# "/bucket3/customized-reports/$\{transfer:UserName\}.pdf" \} ]`
|
|
563
764
|
#
|
|
564
765
|
# In most cases, you can use this value instead of the scope-down policy
|
|
565
|
-
# to lock your user down to the designated home directory
|
|
566
|
-
# To do this, you can set `Entry` to
|
|
567
|
-
# HomeDirectory parameter value.
|
|
568
|
-
#
|
|
569
|
-
#
|
|
570
|
-
#
|
|
571
|
-
#
|
|
572
|
-
#
|
|
573
|
-
# the
|
|
574
|
-
#
|
|
575
|
-
#
|
|
576
|
-
#
|
|
766
|
+
# to lock your user down to the designated home directory
|
|
767
|
+
# ("`chroot`"). To do this, you can set `Entry` to `/` and set
|
|
768
|
+
# `Target` to the HomeDirectory parameter value.
|
|
769
|
+
#
|
|
770
|
+
# The following is an `Entry` and `Target` pair example for `chroot`.
|
|
771
|
+
#
|
|
772
|
+
# `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
|
|
773
|
+
#
|
|
774
|
+
# <note markdown="1"> If the target of a logical directory entry does not exist in Amazon S3
|
|
775
|
+
# or EFS, the entry will be ignored. As a workaround, you can use the
|
|
776
|
+
# Amazon S3 API or EFS API to create 0 byte objects as place holders for
|
|
777
|
+
# your directory. If using the CLI, use the `s3api` or `efsapi` call
|
|
778
|
+
# instead of `s3` or `efs` so you can use the put-object operation. For
|
|
779
|
+
# example, you use the following: `aws s3api put-object --bucket
|
|
780
|
+
# bucketname --key path/to/folder/`. Make sure that the end of the key
|
|
781
|
+
# name ends in a `/` for it to be considered a folder.
|
|
577
782
|
#
|
|
578
783
|
# </note>
|
|
579
784
|
#
|
|
580
785
|
# @option params [String] :policy
|
|
581
|
-
# A scope-down policy for your user so you can use the same IAM
|
|
582
|
-
# across multiple users. This policy scopes down user access to
|
|
583
|
-
# of their Amazon S3 bucket. Variables that you can use inside
|
|
584
|
-
# 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\}`,
|
|
585
790
|
# `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
|
|
586
791
|
#
|
|
587
|
-
# <note markdown="1">
|
|
792
|
+
# <note markdown="1"> This only applies when domain of ServerId is S3. EFS does not use
|
|
793
|
+
# scope down policy.
|
|
794
|
+
#
|
|
795
|
+
# For scope-down policies, AWS Transfer Family stores the policy as a
|
|
588
796
|
# JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
|
|
589
797
|
# You save the policy as a JSON blob and pass it in the `Policy`
|
|
590
798
|
# argument.
|
|
591
799
|
#
|
|
592
|
-
# For an example of a scope-down policy, see [
|
|
800
|
+
# For an example of a scope-down policy, see [Example scope-down
|
|
593
801
|
# policy][1].
|
|
594
802
|
#
|
|
595
803
|
# For more information, see [AssumeRole][2] in the *AWS Security Token
|
|
@@ -599,16 +807,23 @@ module Aws::Transfer
|
|
|
599
807
|
#
|
|
600
808
|
#
|
|
601
809
|
#
|
|
602
|
-
# [1]: https://docs.aws.amazon.com/transfer/latest/userguide/
|
|
810
|
+
# [1]: https://docs.aws.amazon.com/transfer/latest/userguide/scope-down-policy.html
|
|
603
811
|
# [2]: https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html
|
|
604
812
|
#
|
|
605
813
|
# @option params [Types::PosixProfile] :posix_profile
|
|
814
|
+
# Specifies the full POSIX identity, including user ID (`Uid`), group ID
|
|
815
|
+
# (`Gid`), and any secondary groups IDs (`SecondaryGids`), that controls
|
|
816
|
+
# your users' access to your Amazon EFS file systems. The POSIX
|
|
817
|
+
# permissions that are set on files and directories in Amazon EFS
|
|
818
|
+
# determine the level of access your users get when transferring files
|
|
819
|
+
# into and out of your Amazon EFS file systems.
|
|
606
820
|
#
|
|
607
821
|
# @option params [required, String] :role
|
|
608
|
-
#
|
|
609
|
-
#
|
|
610
|
-
#
|
|
611
|
-
#
|
|
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
|
|
612
827
|
# contain a trust relationship that allows the server to access your
|
|
613
828
|
# resources when servicing your users' transfer requests.
|
|
614
829
|
#
|
|
@@ -680,6 +895,50 @@ module Aws::Transfer
|
|
|
680
895
|
req.send_request(options)
|
|
681
896
|
end
|
|
682
897
|
|
|
898
|
+
# Allows you to delete the access specified in the `ServerID` and
|
|
899
|
+
# `ExternalID` parameters.
|
|
900
|
+
#
|
|
901
|
+
# @option params [required, String] :server_id
|
|
902
|
+
# A system-assigned unique identifier for a server that has this user
|
|
903
|
+
# assigned.
|
|
904
|
+
#
|
|
905
|
+
# @option params [required, String] :external_id
|
|
906
|
+
# A unique identifier that is required to identify specific groups
|
|
907
|
+
# within your directory. The users of the group that you associate have
|
|
908
|
+
# access to your Amazon S3 or Amazon EFS resources over the enabled
|
|
909
|
+
# protocols using AWS Transfer Family. If you know the group name, you
|
|
910
|
+
# can view the SID values by running the following command using Windows
|
|
911
|
+
# PowerShell.
|
|
912
|
+
#
|
|
913
|
+
# `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
|
|
914
|
+
# -Properties * | Select SamAccountName,ObjectSid`
|
|
915
|
+
#
|
|
916
|
+
# In that command, replace *YourGroupName* with the name of your Active
|
|
917
|
+
# Directory group.
|
|
918
|
+
#
|
|
919
|
+
# The regex used to validate this parameter is a string of characters
|
|
920
|
+
# consisting of uppercase and lowercase alphanumeric characters with no
|
|
921
|
+
# spaces. You can also include underscores or any of the following
|
|
922
|
+
# characters: =,.@:/-
|
|
923
|
+
#
|
|
924
|
+
# @return [Struct] Returns an empty {Seahorse::Client::Response response}.
|
|
925
|
+
#
|
|
926
|
+
# @example Request syntax with placeholder values
|
|
927
|
+
#
|
|
928
|
+
# resp = client.delete_access({
|
|
929
|
+
# server_id: "ServerId", # required
|
|
930
|
+
# external_id: "ExternalId", # required
|
|
931
|
+
# })
|
|
932
|
+
#
|
|
933
|
+
# @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/DeleteAccess AWS API Documentation
|
|
934
|
+
#
|
|
935
|
+
# @overload delete_access(params = {})
|
|
936
|
+
# @param [Hash] params ({})
|
|
937
|
+
def delete_access(params = {}, options = {})
|
|
938
|
+
req = build_request(:delete_access, params)
|
|
939
|
+
req.send_request(options)
|
|
940
|
+
end
|
|
941
|
+
|
|
683
942
|
# Deletes the file transfer protocol-enabled server that you specify.
|
|
684
943
|
#
|
|
685
944
|
# No response returns from this operation.
|
|
@@ -773,6 +1032,73 @@ module Aws::Transfer
|
|
|
773
1032
|
req.send_request(options)
|
|
774
1033
|
end
|
|
775
1034
|
|
|
1035
|
+
# Describes the access that is assigned to the specific file transfer
|
|
1036
|
+
# protocol-enabled server, as identified by its `ServerId` property and
|
|
1037
|
+
# its `ExternalID`.
|
|
1038
|
+
#
|
|
1039
|
+
# The response from this call returns the properties of the access that
|
|
1040
|
+
# is associated with the `ServerId` value that was specified.
|
|
1041
|
+
#
|
|
1042
|
+
# @option params [required, String] :server_id
|
|
1043
|
+
# A system-assigned unique identifier for a server that has this access
|
|
1044
|
+
# assigned.
|
|
1045
|
+
#
|
|
1046
|
+
# @option params [required, String] :external_id
|
|
1047
|
+
# A unique identifier that is required to identify specific groups
|
|
1048
|
+
# within your directory. The users of the group that you associate have
|
|
1049
|
+
# access to your Amazon S3 or Amazon EFS resources over the enabled
|
|
1050
|
+
# protocols using AWS Transfer Family. If you know the group name, you
|
|
1051
|
+
# can view the SID values by running the following command using Windows
|
|
1052
|
+
# PowerShell.
|
|
1053
|
+
#
|
|
1054
|
+
# `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
|
|
1055
|
+
# -Properties * | Select SamAccountName,ObjectSid`
|
|
1056
|
+
#
|
|
1057
|
+
# In that command, replace *YourGroupName* with the name of your Active
|
|
1058
|
+
# Directory group.
|
|
1059
|
+
#
|
|
1060
|
+
# The regex used to validate this parameter is a string of characters
|
|
1061
|
+
# consisting of uppercase and lowercase alphanumeric characters with no
|
|
1062
|
+
# spaces. You can also include underscores or any of the following
|
|
1063
|
+
# characters: =,.@:/-
|
|
1064
|
+
#
|
|
1065
|
+
# @return [Types::DescribeAccessResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
|
|
1066
|
+
#
|
|
1067
|
+
# * {Types::DescribeAccessResponse#server_id #server_id} => String
|
|
1068
|
+
# * {Types::DescribeAccessResponse#access #access} => Types::DescribedAccess
|
|
1069
|
+
#
|
|
1070
|
+
# @example Request syntax with placeholder values
|
|
1071
|
+
#
|
|
1072
|
+
# resp = client.describe_access({
|
|
1073
|
+
# server_id: "ServerId", # required
|
|
1074
|
+
# external_id: "ExternalId", # required
|
|
1075
|
+
# })
|
|
1076
|
+
#
|
|
1077
|
+
# @example Response structure
|
|
1078
|
+
#
|
|
1079
|
+
# resp.server_id #=> String
|
|
1080
|
+
# resp.access.home_directory #=> String
|
|
1081
|
+
# resp.access.home_directory_mappings #=> Array
|
|
1082
|
+
# resp.access.home_directory_mappings[0].entry #=> String
|
|
1083
|
+
# resp.access.home_directory_mappings[0].target #=> String
|
|
1084
|
+
# resp.access.home_directory_type #=> String, one of "PATH", "LOGICAL"
|
|
1085
|
+
# resp.access.policy #=> String
|
|
1086
|
+
# resp.access.posix_profile.uid #=> Integer
|
|
1087
|
+
# resp.access.posix_profile.gid #=> Integer
|
|
1088
|
+
# resp.access.posix_profile.secondary_gids #=> Array
|
|
1089
|
+
# resp.access.posix_profile.secondary_gids[0] #=> Integer
|
|
1090
|
+
# resp.access.role #=> String
|
|
1091
|
+
# resp.access.external_id #=> String
|
|
1092
|
+
#
|
|
1093
|
+
# @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/DescribeAccess AWS API Documentation
|
|
1094
|
+
#
|
|
1095
|
+
# @overload describe_access(params = {})
|
|
1096
|
+
# @param [Hash] params ({})
|
|
1097
|
+
def describe_access(params = {}, options = {})
|
|
1098
|
+
req = build_request(:describe_access, params)
|
|
1099
|
+
req.send_request(options)
|
|
1100
|
+
end
|
|
1101
|
+
|
|
776
1102
|
# Describes the security policy that is attached to your file transfer
|
|
777
1103
|
# protocol-enabled server. The response contains a description of the
|
|
778
1104
|
# security policy's properties. For more information about security
|
|
@@ -855,7 +1181,8 @@ module Aws::Transfer
|
|
|
855
1181
|
# resp.server.host_key_fingerprint #=> String
|
|
856
1182
|
# resp.server.identity_provider_details.url #=> String
|
|
857
1183
|
# resp.server.identity_provider_details.invocation_role #=> String
|
|
858
|
-
# resp.server.
|
|
1184
|
+
# resp.server.identity_provider_details.directory_id #=> String
|
|
1185
|
+
# resp.server.identity_provider_type #=> String, one of "SERVICE_MANAGED", "API_GATEWAY", "AWS_DIRECTORY_SERVICE"
|
|
859
1186
|
# resp.server.logging_role #=> String
|
|
860
1187
|
# resp.server.protocols #=> Array
|
|
861
1188
|
# resp.server.protocols[0] #=> String, one of "SFTP", "FTP", "FTPS"
|
|
@@ -981,6 +1308,56 @@ module Aws::Transfer
|
|
|
981
1308
|
req.send_request(options)
|
|
982
1309
|
end
|
|
983
1310
|
|
|
1311
|
+
# Lists the details for all the accesses you have on your server.
|
|
1312
|
+
#
|
|
1313
|
+
# @option params [Integer] :max_results
|
|
1314
|
+
# Specifies the maximum number of access SIDs to return.
|
|
1315
|
+
#
|
|
1316
|
+
# @option params [String] :next_token
|
|
1317
|
+
# When you can get additional results from the `ListAccesses` call, a
|
|
1318
|
+
# `NextToken` parameter is returned in the output. You can then pass in
|
|
1319
|
+
# a subsequent command to the `NextToken` parameter to continue listing
|
|
1320
|
+
# additional accesses.
|
|
1321
|
+
#
|
|
1322
|
+
# @option params [required, String] :server_id
|
|
1323
|
+
# A system-assigned unique identifier for a server that has users
|
|
1324
|
+
# assigned to it.
|
|
1325
|
+
#
|
|
1326
|
+
# @return [Types::ListAccessesResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
|
|
1327
|
+
#
|
|
1328
|
+
# * {Types::ListAccessesResponse#next_token #next_token} => String
|
|
1329
|
+
# * {Types::ListAccessesResponse#server_id #server_id} => String
|
|
1330
|
+
# * {Types::ListAccessesResponse#accesses #accesses} => Array<Types::ListedAccess>
|
|
1331
|
+
#
|
|
1332
|
+
# The returned {Seahorse::Client::Response response} is a pageable response and is Enumerable. For details on usage see {Aws::PageableResponse PageableResponse}.
|
|
1333
|
+
#
|
|
1334
|
+
# @example Request syntax with placeholder values
|
|
1335
|
+
#
|
|
1336
|
+
# resp = client.list_accesses({
|
|
1337
|
+
# max_results: 1,
|
|
1338
|
+
# next_token: "NextToken",
|
|
1339
|
+
# server_id: "ServerId", # required
|
|
1340
|
+
# })
|
|
1341
|
+
#
|
|
1342
|
+
# @example Response structure
|
|
1343
|
+
#
|
|
1344
|
+
# resp.next_token #=> String
|
|
1345
|
+
# resp.server_id #=> String
|
|
1346
|
+
# resp.accesses #=> Array
|
|
1347
|
+
# resp.accesses[0].home_directory #=> String
|
|
1348
|
+
# resp.accesses[0].home_directory_type #=> String, one of "PATH", "LOGICAL"
|
|
1349
|
+
# resp.accesses[0].role #=> String
|
|
1350
|
+
# resp.accesses[0].external_id #=> String
|
|
1351
|
+
#
|
|
1352
|
+
# @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/ListAccesses AWS API Documentation
|
|
1353
|
+
#
|
|
1354
|
+
# @overload list_accesses(params = {})
|
|
1355
|
+
# @param [Hash] params ({})
|
|
1356
|
+
def list_accesses(params = {}, options = {})
|
|
1357
|
+
req = build_request(:list_accesses, params)
|
|
1358
|
+
req.send_request(options)
|
|
1359
|
+
end
|
|
1360
|
+
|
|
984
1361
|
# Lists the security policies that are attached to your file transfer
|
|
985
1362
|
# protocol-enabled servers.
|
|
986
1363
|
#
|
|
@@ -1056,7 +1433,7 @@ module Aws::Transfer
|
|
|
1056
1433
|
# resp.servers #=> Array
|
|
1057
1434
|
# resp.servers[0].arn #=> String
|
|
1058
1435
|
# resp.servers[0].domain #=> String, one of "S3", "EFS"
|
|
1059
|
-
# resp.servers[0].identity_provider_type #=> String, one of "SERVICE_MANAGED", "API_GATEWAY"
|
|
1436
|
+
# resp.servers[0].identity_provider_type #=> String, one of "SERVICE_MANAGED", "API_GATEWAY", "AWS_DIRECTORY_SERVICE"
|
|
1060
1437
|
# resp.servers[0].endpoint_type #=> String, one of "PUBLIC", "VPC", "VPC_ENDPOINT"
|
|
1061
1438
|
# resp.servers[0].logging_role #=> String
|
|
1062
1439
|
# resp.servers[0].server_id #=> String
|
|
@@ -1072,8 +1449,8 @@ module Aws::Transfer
|
|
|
1072
1449
|
req.send_request(options)
|
|
1073
1450
|
end
|
|
1074
1451
|
|
|
1075
|
-
# Lists all of the tags associated with the Amazon Resource
|
|
1076
|
-
# you specify. The resource can be a user, server, or role.
|
|
1452
|
+
# Lists all of the tags associated with the Amazon Resource Name (ARN)
|
|
1453
|
+
# that you specify. The resource can be a user, server, or role.
|
|
1077
1454
|
#
|
|
1078
1455
|
# @option params [required, String] :arn
|
|
1079
1456
|
# Requests the tags associated with a particular Amazon Resource Name
|
|
@@ -1284,11 +1661,12 @@ module Aws::Transfer
|
|
|
1284
1661
|
end
|
|
1285
1662
|
|
|
1286
1663
|
# If the `IdentityProviderType` of a file transfer protocol-enabled
|
|
1287
|
-
# server is `API_Gateway`, tests whether your
|
|
1288
|
-
# successfully. We highly recommend that you
|
|
1289
|
-
# your authentication method as soon as you
|
|
1290
|
-
# so, you can troubleshoot issues with the
|
|
1291
|
-
# ensure that your users can
|
|
1664
|
+
# server is `AWS_DIRECTORY_SERVICE` or `API_Gateway`, tests whether your
|
|
1665
|
+
# identity provider is set up successfully. We highly recommend that you
|
|
1666
|
+
# call this operation to test your authentication method as soon as you
|
|
1667
|
+
# create your server. By doing so, you can troubleshoot issues with the
|
|
1668
|
+
# identity provider integration to ensure that your users can
|
|
1669
|
+
# successfully use the service.
|
|
1292
1670
|
#
|
|
1293
1671
|
# @option params [required, String] :server_id
|
|
1294
1672
|
# A system-assigned identifier for a specific server. That server's
|
|
@@ -1381,6 +1759,172 @@ module Aws::Transfer
|
|
|
1381
1759
|
req.send_request(options)
|
|
1382
1760
|
end
|
|
1383
1761
|
|
|
1762
|
+
# Allows you to update parameters for the access specified in the
|
|
1763
|
+
# `ServerID` and `ExternalID` parameters.
|
|
1764
|
+
#
|
|
1765
|
+
# @option params [String] :home_directory
|
|
1766
|
+
# The landing directory (folder) for a user when they log in to the
|
|
1767
|
+
# server using the client.
|
|
1768
|
+
#
|
|
1769
|
+
# A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
|
|
1770
|
+
#
|
|
1771
|
+
# @option params [String] :home_directory_type
|
|
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.
|
|
1779
|
+
#
|
|
1780
|
+
# @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
|
|
1781
|
+
# Logical directory mappings that specify what Amazon S3 or Amazon EFS
|
|
1782
|
+
# paths and keys should be visible to your user and how you want to make
|
|
1783
|
+
# them visible. You must specify the `Entry` and `Target` pair, where
|
|
1784
|
+
# `Entry` shows how the path is made visible and `Target` is the actual
|
|
1785
|
+
# Amazon S3 or Amazon EFS path. If you only specify a target, it will be
|
|
1786
|
+
# displayed as is. You also must ensure that your AWS Identity and
|
|
1787
|
+
# Access Management (IAM) role provides access to paths in `Target`.
|
|
1788
|
+
# This value can only be set when `HomeDirectoryType` is set to
|
|
1789
|
+
# *LOGICAL*.
|
|
1790
|
+
#
|
|
1791
|
+
# The following is an `Entry` and `Target` pair example.
|
|
1792
|
+
#
|
|
1793
|
+
# `[ \{ "Entry": "your-personal-report.pdf", "Target":
|
|
1794
|
+
# "/bucket3/customized-reports/$\{transfer:UserName\}.pdf" \} ]`
|
|
1795
|
+
#
|
|
1796
|
+
# In most cases, you can use this value instead of the scope-down policy
|
|
1797
|
+
# to lock down your user to the designated home directory
|
|
1798
|
+
# ("`chroot`"). To do this, you can set `Entry` to `/` and set
|
|
1799
|
+
# `Target` to the `HomeDirectory` parameter value.
|
|
1800
|
+
#
|
|
1801
|
+
# The following is an `Entry` and `Target` pair example for `chroot`.
|
|
1802
|
+
#
|
|
1803
|
+
# `[ \{ "Entry": "/", "Target": "/bucket_name/home/mydirectory" \} ]`
|
|
1804
|
+
#
|
|
1805
|
+
# <note markdown="1"> If the target of a logical directory entry does not exist in Amazon S3
|
|
1806
|
+
# or Amazon EFS, the entry will be ignored. As a workaround, you can use
|
|
1807
|
+
# the Amazon S3 API or EFS API to create 0-byte objects as place holders
|
|
1808
|
+
# for your directory. If using the AWS CLI, use the `s3api` or `efsapi`
|
|
1809
|
+
# call instead of `s3` or `efs` so you can use the `put-object`
|
|
1810
|
+
# operation. For example, you can use the following.
|
|
1811
|
+
#
|
|
1812
|
+
# `aws s3api put-object --bucket bucketname --key path/to/folder/`
|
|
1813
|
+
#
|
|
1814
|
+
# The end of the key name must end in a `/` for it to be considered a
|
|
1815
|
+
# folder.
|
|
1816
|
+
#
|
|
1817
|
+
# </note>
|
|
1818
|
+
#
|
|
1819
|
+
# @option params [String] :policy
|
|
1820
|
+
# A scope-down policy for your user so that you can use the same IAM
|
|
1821
|
+
# role across multiple users. This policy scopes down user access to
|
|
1822
|
+
# portions of their Amazon S3 bucket. Variables that you can use inside
|
|
1823
|
+
# this policy include `$\{Transfer:UserName\}`,
|
|
1824
|
+
# `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
|
|
1825
|
+
#
|
|
1826
|
+
# <note markdown="1"> This only applies when domain of `ServerId` is S3. Amazon EFS does not
|
|
1827
|
+
# use scope down policy.
|
|
1828
|
+
#
|
|
1829
|
+
# For scope-down policies, AWS Transfer Family stores the policy as a
|
|
1830
|
+
# JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
|
|
1831
|
+
# You save the policy as a JSON blob and pass it in the `Policy`
|
|
1832
|
+
# argument.
|
|
1833
|
+
#
|
|
1834
|
+
# For an example of a scope-down policy, see [Example scope-down
|
|
1835
|
+
# policy][1].
|
|
1836
|
+
#
|
|
1837
|
+
# For more information, see [AssumeRole][2] in the *AWS Security Token
|
|
1838
|
+
# Service API Reference*.
|
|
1839
|
+
#
|
|
1840
|
+
# </note>
|
|
1841
|
+
#
|
|
1842
|
+
#
|
|
1843
|
+
#
|
|
1844
|
+
# [1]: https://docs.aws.amazon.com/transfer/latest/userguide/scope-down-policy.html
|
|
1845
|
+
# [2]: https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html
|
|
1846
|
+
#
|
|
1847
|
+
# @option params [Types::PosixProfile] :posix_profile
|
|
1848
|
+
# The full POSIX identity, including user ID (`Uid`), group ID (`Gid`),
|
|
1849
|
+
# and any secondary groups IDs (`SecondaryGids`), that controls your
|
|
1850
|
+
# users' access to your Amazon EFS file systems. The POSIX permissions
|
|
1851
|
+
# that are set on files and directories in your file system determine
|
|
1852
|
+
# the level of access your users get when transferring files into and
|
|
1853
|
+
# out of your Amazon EFS file systems.
|
|
1854
|
+
#
|
|
1855
|
+
# @option params [String] :role
|
|
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.
|
|
1863
|
+
#
|
|
1864
|
+
# @option params [required, String] :server_id
|
|
1865
|
+
# A system-assigned unique identifier for a server instance. This is the
|
|
1866
|
+
# specific server that you added your user to.
|
|
1867
|
+
#
|
|
1868
|
+
# @option params [required, String] :external_id
|
|
1869
|
+
# A unique identifier that is required to identify specific groups
|
|
1870
|
+
# within your directory. The users of the group that you associate have
|
|
1871
|
+
# access to your Amazon S3 or Amazon EFS resources over the enabled
|
|
1872
|
+
# protocols using AWS Transfer Family. If you know the group name, you
|
|
1873
|
+
# can view the SID values by running the following command using Windows
|
|
1874
|
+
# PowerShell.
|
|
1875
|
+
#
|
|
1876
|
+
# `Get-ADGroup -Filter \{samAccountName -like "YourGroupName*"\}
|
|
1877
|
+
# -Properties * | Select SamAccountName,ObjectSid`
|
|
1878
|
+
#
|
|
1879
|
+
# In that command, replace *YourGroupName* with the name of your Active
|
|
1880
|
+
# Directory group.
|
|
1881
|
+
#
|
|
1882
|
+
# The regex used to validate this parameter is a string of characters
|
|
1883
|
+
# consisting of uppercase and lowercase alphanumeric characters with no
|
|
1884
|
+
# spaces. You can also include underscores or any of the following
|
|
1885
|
+
# characters: =,.@:/-
|
|
1886
|
+
#
|
|
1887
|
+
# @return [Types::UpdateAccessResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
|
|
1888
|
+
#
|
|
1889
|
+
# * {Types::UpdateAccessResponse#server_id #server_id} => String
|
|
1890
|
+
# * {Types::UpdateAccessResponse#external_id #external_id} => String
|
|
1891
|
+
#
|
|
1892
|
+
# @example Request syntax with placeholder values
|
|
1893
|
+
#
|
|
1894
|
+
# resp = client.update_access({
|
|
1895
|
+
# home_directory: "HomeDirectory",
|
|
1896
|
+
# home_directory_type: "PATH", # accepts PATH, LOGICAL
|
|
1897
|
+
# home_directory_mappings: [
|
|
1898
|
+
# {
|
|
1899
|
+
# entry: "MapEntry", # required
|
|
1900
|
+
# target: "MapTarget", # required
|
|
1901
|
+
# },
|
|
1902
|
+
# ],
|
|
1903
|
+
# policy: "Policy",
|
|
1904
|
+
# posix_profile: {
|
|
1905
|
+
# uid: 1, # required
|
|
1906
|
+
# gid: 1, # required
|
|
1907
|
+
# secondary_gids: [1],
|
|
1908
|
+
# },
|
|
1909
|
+
# role: "Role",
|
|
1910
|
+
# server_id: "ServerId", # required
|
|
1911
|
+
# external_id: "ExternalId", # required
|
|
1912
|
+
# })
|
|
1913
|
+
#
|
|
1914
|
+
# @example Response structure
|
|
1915
|
+
#
|
|
1916
|
+
# resp.server_id #=> String
|
|
1917
|
+
# resp.external_id #=> String
|
|
1918
|
+
#
|
|
1919
|
+
# @see http://docs.aws.amazon.com/goto/WebAPI/transfer-2018-11-05/UpdateAccess AWS API Documentation
|
|
1920
|
+
#
|
|
1921
|
+
# @overload update_access(params = {})
|
|
1922
|
+
# @param [Hash] params ({})
|
|
1923
|
+
def update_access(params = {}, options = {})
|
|
1924
|
+
req = build_request(:update_access, params)
|
|
1925
|
+
req.send_request(options)
|
|
1926
|
+
end
|
|
1927
|
+
|
|
1384
1928
|
# Updates the file transfer protocol-enabled server's properties after
|
|
1385
1929
|
# that server has been created.
|
|
1386
1930
|
#
|
|
@@ -1434,12 +1978,24 @@ module Aws::Transfer
|
|
|
1434
1978
|
# with your server's endpoint.
|
|
1435
1979
|
#
|
|
1436
1980
|
# @option params [String] :endpoint_type
|
|
1437
|
-
# The type of endpoint that you want your server to
|
|
1438
|
-
#
|
|
1439
|
-
#
|
|
1440
|
-
# within your VPC
|
|
1441
|
-
#
|
|
1442
|
-
#
|
|
1981
|
+
# The type of endpoint that you want your server to use. You can choose
|
|
1982
|
+
# to make your server's endpoint publicly accessible (PUBLIC) or host
|
|
1983
|
+
# it inside your VPC. With an endpoint that is hosted in a VPC, you can
|
|
1984
|
+
# restrict access to your server and resources only within your VPC or
|
|
1985
|
+
# choose to make it internet facing by attaching Elastic IP addresses
|
|
1986
|
+
# directly to it.
|
|
1987
|
+
#
|
|
1988
|
+
# <note markdown="1"> After May 19, 2021, you won't be able to create a server using
|
|
1989
|
+
# `EndpointType=VPC_ENDPOINT` in your AWS account if your account
|
|
1990
|
+
# hasn't already done so before May 19, 2021. If you have already
|
|
1991
|
+
# created servers with `EndpointType=VPC_ENDPOINT` in your AWS account
|
|
1992
|
+
# on or before May 19, 2021, you will not be affected. After this date,
|
|
1993
|
+
# use `EndpointType`=`VPC`.
|
|
1994
|
+
#
|
|
1995
|
+
# For more information, see
|
|
1996
|
+
# https://docs.aws.amazon.com/transfer/latest/userguide/create-server-in-vpc.html#deprecate-vpc-endpoint.
|
|
1997
|
+
#
|
|
1998
|
+
# It is recommended that you use `VPC` as the `EndpointType`. With this
|
|
1443
1999
|
# endpoint type, you have the option to directly associate up to three
|
|
1444
2000
|
# Elastic IPv4 addresses (BYO IP included) with your server's endpoint
|
|
1445
2001
|
# and use VPC security groups to restrict traffic by the client's
|
|
@@ -1469,8 +2025,8 @@ module Aws::Transfer
|
|
|
1469
2025
|
#
|
|
1470
2026
|
# @option params [String] :logging_role
|
|
1471
2027
|
# Changes the AWS Identity and Access Management (IAM) role that allows
|
|
1472
|
-
# Amazon S3 events to be logged in Amazon CloudWatch,
|
|
1473
|
-
# or off.
|
|
2028
|
+
# Amazon S3 or Amazon EFS events to be logged in Amazon CloudWatch,
|
|
2029
|
+
# turning logging on or off.
|
|
1474
2030
|
#
|
|
1475
2031
|
# @option params [Array<String>] :protocols
|
|
1476
2032
|
# Specifies the file transfer protocol or protocols over which your file
|
|
@@ -1490,7 +2046,8 @@ module Aws::Transfer
|
|
|
1490
2046
|
# when clients connect to it over FTPS.
|
|
1491
2047
|
#
|
|
1492
2048
|
# If `Protocol` includes either `FTP` or `FTPS`, then the `EndpointType`
|
|
1493
|
-
# must be `VPC` and the `IdentityProviderType` must be
|
|
2049
|
+
# must be `VPC` and the `IdentityProviderType` must be
|
|
2050
|
+
# `AWS_DIRECTORY_SERVICE` or `API_GATEWAY`.
|
|
1494
2051
|
#
|
|
1495
2052
|
# If `Protocol` includes `FTP`, then `AddressAllocationIds` cannot be
|
|
1496
2053
|
# associated.
|
|
@@ -1529,6 +2086,7 @@ module Aws::Transfer
|
|
|
1529
2086
|
# identity_provider_details: {
|
|
1530
2087
|
# url: "Url",
|
|
1531
2088
|
# invocation_role: "Role",
|
|
2089
|
+
# directory_id: "DirectoryId",
|
|
1532
2090
|
# },
|
|
1533
2091
|
# logging_role: "NullableRole",
|
|
1534
2092
|
# protocols: ["SFTP"], # accepts SFTP, FTP, FTPS
|
|
@@ -1557,56 +2115,61 @@ module Aws::Transfer
|
|
|
1557
2115
|
# user.
|
|
1558
2116
|
#
|
|
1559
2117
|
# @option params [String] :home_directory
|
|
1560
|
-
#
|
|
1561
|
-
#
|
|
2118
|
+
# The landing directory (folder) for a user when they log in to the
|
|
2119
|
+
# server using the client.
|
|
1562
2120
|
#
|
|
1563
|
-
#
|
|
2121
|
+
# A `HomeDirectory` example is `/bucket_name/home/mydirectory`.
|
|
1564
2122
|
#
|
|
1565
2123
|
# @option params [String] :home_directory_type
|
|
1566
2124
|
# The type of landing directory (folder) you want your users' home
|
|
1567
2125
|
# directory to be when they log into the server. If you set it to
|
|
1568
|
-
# `PATH`, the user will see the absolute Amazon S3 bucket
|
|
1569
|
-
# their file transfer protocol clients. If you set it
|
|
1570
|
-
# will need to provide mappings in the
|
|
1571
|
-
# you want to make Amazon S3
|
|
2126
|
+
# `PATH`, the user will see the absolute Amazon S3 bucket or EFS paths
|
|
2127
|
+
# as is in their file transfer protocol clients. If you set it
|
|
2128
|
+
# `LOGICAL`, you will need to provide mappings in the
|
|
2129
|
+
# `HomeDirectoryMappings` for how you want to make Amazon S3 or EFS
|
|
2130
|
+
# paths visible to your users.
|
|
1572
2131
|
#
|
|
1573
2132
|
# @option params [Array<Types::HomeDirectoryMapEntry>] :home_directory_mappings
|
|
1574
|
-
# Logical directory mappings that specify what Amazon S3
|
|
1575
|
-
# should be visible to your user and how you want to make
|
|
1576
|
-
# You will need to specify the "`Entry`" and
|
|
1577
|
-
# `Entry` shows how the path is made visible
|
|
1578
|
-
#
|
|
1579
|
-
#
|
|
1580
|
-
# to paths in `Target`. The
|
|
2133
|
+
# Logical directory mappings that specify what Amazon S3 or Amazon EFS
|
|
2134
|
+
# paths and keys should be visible to your user and how you want to make
|
|
2135
|
+
# them visible. You will need to specify the "`Entry`" and
|
|
2136
|
+
# "`Target`" pair, where `Entry` shows how the path is made visible
|
|
2137
|
+
# and `Target` is the actual Amazon S3 or Amazon EFS path. If you only
|
|
2138
|
+
# specify a target, it will be displayed as is. You will need to also
|
|
2139
|
+
# make sure that your IAM role provides access to paths in `Target`. The
|
|
2140
|
+
# following is an example.
|
|
1581
2141
|
#
|
|
1582
2142
|
# `'[ "/bucket2/documentation", \{ "Entry": "your-personal-report.pdf",
|
|
1583
2143
|
# "Target": "/bucket3/customized-reports/$\{transfer:UserName\}.pdf" \}
|
|
1584
2144
|
# ]'`
|
|
1585
2145
|
#
|
|
1586
2146
|
# In most cases, you can use this value instead of the scope-down policy
|
|
1587
|
-
# to lock your user
|
|
1588
|
-
# To do this, you can set `Entry` to '/' and set
|
|
1589
|
-
# HomeDirectory parameter value.
|
|
1590
|
-
#
|
|
1591
|
-
# <note markdown="1"> If the target of a logical directory entry does not exist in Amazon
|
|
1592
|
-
#
|
|
1593
|
-
# S3 API to create 0
|
|
1594
|
-
# If using the CLI, use the `s3api`
|
|
1595
|
-
#
|
|
1596
|
-
# s3api put-object --bucket
|
|
1597
|
-
# that the end of the key
|
|
1598
|
-
# folder.
|
|
2147
|
+
# to lock down your user to the designated home directory
|
|
2148
|
+
# ("`chroot`"). To do this, you can set `Entry` to '/' and set
|
|
2149
|
+
# `Target` to the HomeDirectory parameter value.
|
|
2150
|
+
#
|
|
2151
|
+
# <note markdown="1"> If the target of a logical directory entry does not exist in Amazon S3
|
|
2152
|
+
# or EFS, the entry will be ignored. As a workaround, you can use the
|
|
2153
|
+
# Amazon S3 API or EFS API to create 0-byte objects as place holders for
|
|
2154
|
+
# your directory. If using the AWS CLI, use the `s3api` or `efsapi` call
|
|
2155
|
+
# instead of `s3` `efs` so you can use the put-object operation. For
|
|
2156
|
+
# example, you use the following: `aws s3api put-object --bucket
|
|
2157
|
+
# bucketname --key path/to/folder/`. Make sure that the end of the key
|
|
2158
|
+
# name ends in a / for it to be considered a folder.
|
|
1599
2159
|
#
|
|
1600
2160
|
# </note>
|
|
1601
2161
|
#
|
|
1602
2162
|
# @option params [String] :policy
|
|
1603
|
-
#
|
|
1604
|
-
#
|
|
1605
|
-
#
|
|
1606
|
-
#
|
|
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\}`,
|
|
1607
2167
|
# `$\{Transfer:HomeDirectory\}`, and `$\{Transfer:HomeBucket\}`.
|
|
1608
2168
|
#
|
|
1609
|
-
# <note markdown="1">
|
|
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
|
|
1610
2173
|
# JSON blob, instead of the Amazon Resource Name (ARN) of the policy.
|
|
1611
2174
|
# You save the policy as a JSON blob and pass it in the `Policy`
|
|
1612
2175
|
# argument.
|
|
@@ -1625,12 +2188,19 @@ module Aws::Transfer
|
|
|
1625
2188
|
# [2]: https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html
|
|
1626
2189
|
#
|
|
1627
2190
|
# @option params [Types::PosixProfile] :posix_profile
|
|
2191
|
+
# Specifies the full POSIX identity, including user ID (`Uid`), group ID
|
|
2192
|
+
# (`Gid`), and any secondary groups IDs (`SecondaryGids`), that controls
|
|
2193
|
+
# your users' access to your Amazon Elastic File Systems (Amazon EFS).
|
|
2194
|
+
# The POSIX permissions that are set on files and directories in your
|
|
2195
|
+
# file system determines the level of access your users get when
|
|
2196
|
+
# transferring files into and out of your Amazon EFS file systems.
|
|
1628
2197
|
#
|
|
1629
2198
|
# @option params [String] :role
|
|
1630
|
-
#
|
|
1631
|
-
#
|
|
1632
|
-
#
|
|
1633
|
-
#
|
|
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
|
|
1634
2204
|
# contain a trust relationship that allows the server to access your
|
|
1635
2205
|
# resources when servicing your users' transfer requests.
|
|
1636
2206
|
#
|
|
@@ -1700,7 +2270,7 @@ module Aws::Transfer
|
|
|
1700
2270
|
params: params,
|
|
1701
2271
|
config: config)
|
|
1702
2272
|
context[:gem_name] = 'aws-sdk-transfer'
|
|
1703
|
-
context[:gem_version] = '1.
|
|
2273
|
+
context[:gem_version] = '1.34.0'
|
|
1704
2274
|
Seahorse::Client::Request.new(handlers, context)
|
|
1705
2275
|
end
|
|
1706
2276
|
|