@aws-sdk/client-efs 3.245.0 → 3.253.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.
@@ -47,9 +47,10 @@ export declare class EFS extends EFSClient {
47
47
  * the application's own directory and any subdirectories. To learn more, see <a href="https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html">Mounting a file system using EFS access
48
48
  * points</a>.</p>
49
49
  * <note>
50
- * <p>If multiple requests to create access points on the same file system are sent in quick succession, and the file system is
51
- * near the limit of 120 access points, you may experience a throttling response for these requests. This
52
- * is to ensure that the file system does not exceed the stated access point limit.</p>
50
+ * <p>If multiple requests to create access points on the same file system are sent in quick
51
+ * succession, and the file system is near the limit of 1000 access points, you may experience
52
+ * a throttling response for these requests. This is to ensure that the file system does not
53
+ * exceed the stated access point limit.</p>
53
54
  * </note>
54
55
  * <p>This operation requires permissions for the <code>elasticfilesystem:CreateAccessPoint</code> action.</p>
55
56
  */
@@ -86,14 +87,12 @@ export declare class EFS extends EFSClient {
86
87
  * <p>For more information, see
87
88
  * <a href="https://docs.aws.amazon.com/efs/latest/ug/creating-using-create-fs.html#creating-using-create-fs-part1">Creating a file system</a>
88
89
  * in the <i>Amazon EFS User Guide</i>.</p>
89
- *
90
90
  * <note>
91
91
  * <p>The <code>CreateFileSystem</code> call returns while the file system's lifecycle
92
92
  * state is still <code>creating</code>. You can check the file system creation status by
93
93
  * calling the <a>DescribeFileSystems</a> operation, which among other things returns the file
94
94
  * system state.</p>
95
95
  * </note>
96
- *
97
96
  * <p>This operation accepts an optional <code>PerformanceMode</code> parameter that you
98
97
  * choose for your file system. We recommend <code>generalPurpose</code> performance mode for
99
98
  * most file systems. File systems using the <code>maxIO</code> performance mode can scale to
@@ -101,14 +100,11 @@ export declare class EFS extends EFSClient {
101
100
  * higher latencies for most file operations. The performance mode can't be changed after
102
101
  * the file system has been created. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/performance.html#performancemodes.html">Amazon EFS performance
103
102
  * modes</a>.</p>
104
- *
105
103
  * <p>You can set the throughput mode for the file system using the <code>ThroughputMode</code> parameter.</p>
106
- *
107
104
  * <p>After the file system is fully created, Amazon EFS sets its lifecycle state to
108
105
  * <code>available</code>, at which point you can create one or more mount targets for the file
109
106
  * system in your VPC. For more information, see <a>CreateMountTarget</a>. You mount your Amazon EFS file system on an EC2 instances in
110
107
  * your VPC by using the mount target. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/how-it-works.html">Amazon EFS: How it Works</a>. </p>
111
- *
112
108
  * <p> This operation requires permissions for the
113
109
  * <code>elasticfilesystem:CreateFileSystem</code> action. </p>
114
110
  */
@@ -154,7 +150,6 @@ export declare class EFS extends EFSClient {
154
150
  * </ul>
155
151
  * </li>
156
152
  * </ul>
157
- *
158
153
  * <p>After creating the mount target, Amazon EFS returns a response that includes, a
159
154
  * <code>MountTargetId</code> and an <code>IpAddress</code>. You use this IP address when
160
155
  * mounting the file system in an EC2 instance. You can also use the mount target's DNS name
@@ -175,7 +170,6 @@ export declare class EFS extends EFSClient {
175
170
  * mount targets</p>
176
171
  * </li>
177
172
  * </ul>
178
- *
179
173
  * <p>If the request satisfies the requirements, Amazon EFS does the following:</p>
180
174
  * <ul>
181
175
  * <li>
@@ -311,7 +305,6 @@ export declare class EFS extends EFSClient {
311
305
  * </ul>
312
306
  * </li>
313
307
  * </ul>
314
- *
315
308
  * <p>The following properties are set by default:</p>
316
309
  * <ul>
317
310
  * <li>
@@ -328,7 +321,6 @@ export declare class EFS extends EFSClient {
328
321
  * throughput mode.</p>
329
322
  * </li>
330
323
  * </ul>
331
- *
332
324
  * <p>The following properties are turned off by default:</p>
333
325
  * <ul>
334
326
  * <li>
@@ -345,7 +337,6 @@ export declare class EFS extends EFSClient {
345
337
  * setting.</p>
346
338
  * </li>
347
339
  * </ul>
348
- *
349
340
  * <p>For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/efs-replication.html">Amazon EFS replication</a> in the
350
341
  * <i>Amazon EFS User Guide</i>.</p>
351
342
  */
@@ -391,14 +382,12 @@ export declare class EFS extends EFSClient {
391
382
  * </note>
392
383
  * <p> You can't delete a file system that is in use. That is, if the file system has
393
384
  * any mount targets, you must first delete them. For more information, see <a>DescribeMountTargets</a> and <a>DeleteMountTarget</a>. </p>
394
- *
395
385
  * <note>
396
386
  * <p>The <code>DeleteFileSystem</code> call returns while the file system state is still
397
387
  * <code>deleting</code>. You can check the file system deletion status by calling the <a>DescribeFileSystems</a> operation, which returns a list of file systems in your
398
388
  * account. If you pass file system ID or creation token for the deleted file system, the <a>DescribeFileSystems</a> returns a <code>404 FileSystemNotFound</code>
399
389
  * error.</p>
400
390
  * </note>
401
- *
402
391
  * <p>This operation requires permissions for the
403
392
  * <code>elasticfilesystem:DeleteFileSystem</code> action.</p>
404
393
  */
@@ -416,7 +405,6 @@ export declare class EFS extends EFSClient {
416
405
  deleteFileSystemPolicy(args: DeleteFileSystemPolicyCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteFileSystemPolicyCommandOutput) => void): void;
417
406
  /**
418
407
  * <p>Deletes the specified mount target.</p>
419
- *
420
408
  * <p>This operation forcibly breaks any mounts of the file system by using the mount target
421
409
  * that is being deleted, which might disrupt instances or applications using those mounts. To
422
410
  * avoid applications getting cut off abruptly, you might consider unmounting any mounts of the
@@ -433,13 +421,11 @@ export declare class EFS extends EFSClient {
433
421
  * </p>
434
422
  * </li>
435
423
  * </ul>
436
- *
437
424
  * <note>
438
425
  * <p>The <code>DeleteMountTarget</code> call returns while the mount target state is still
439
426
  * <code>deleting</code>. You can check the mount target deletion by calling the <a>DescribeMountTargets</a> operation, which returns a list of mount target
440
427
  * descriptions for the given file system. </p>
441
428
  * </note>
442
- *
443
429
  * <p>The operation also requires permissions for the following Amazon EC2 action on the
444
430
  * mount target's network interface:</p>
445
431
  * <ul>
@@ -475,7 +461,6 @@ export declare class EFS extends EFSClient {
475
461
  * includes a tag key that doesn't exist, Amazon EFS ignores it and doesn't cause an
476
462
  * error. For more information about tags and related restrictions, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html">Tag restrictions</a> in the
477
463
  * <i>Billing and Cost Management User Guide</i>.</p>
478
- *
479
464
  * <p>This operation requires permissions for the <code>elasticfilesystem:DeleteTags</code>
480
465
  * action.</p>
481
466
  */
@@ -516,20 +501,17 @@ export declare class EFS extends EFSClient {
516
501
  * <code>CreationToken</code> or the <code>FileSystemId</code> is provided. Otherwise, it
517
502
  * returns descriptions of all file systems owned by the caller's Amazon Web Services account in the
518
503
  * Amazon Web Services Region of the endpoint that you're calling.</p>
519
- *
520
504
  * <p>When retrieving all file system descriptions, you can optionally specify the
521
505
  * <code>MaxItems</code> parameter to limit the number of descriptions in a response.
522
- * Currently, this number is automatically set to 10. If more file system descriptions remain,
506
+ * This number is automatically set to 100. If more file system descriptions remain,
523
507
  * Amazon EFS returns a <code>NextMarker</code>, an opaque token, in the response. In this case,
524
508
  * you should send a subsequent request with the <code>Marker</code> request parameter set to the
525
509
  * value of <code>NextMarker</code>. </p>
526
- *
527
510
  * <p>To retrieve a list of your file system descriptions, this operation is used in an
528
511
  * iterative process, where <code>DescribeFileSystems</code> is called first without the
529
512
  * <code>Marker</code> and then the operation continues to call it with the <code>Marker</code>
530
513
  * parameter set to the value of the <code>NextMarker</code> from the previous response until the
531
514
  * response has no <code>NextMarker</code>. </p>
532
- *
533
515
  * <p> The order of file systems returned in the response of one
534
516
  * <code>DescribeFileSystems</code> call and the order of file systems returned across the
535
517
  * responses of a multi-call iteration is unspecified. </p>
@@ -557,7 +539,6 @@ export declare class EFS extends EFSClient {
557
539
  * <p>Returns the descriptions of all the current mount targets, or a specific mount target,
558
540
  * for a file system. When requesting all of the current mount targets, the order of mount
559
541
  * targets returned in the response is unspecified.</p>
560
- *
561
542
  * <p>This operation requires permissions for the
562
543
  * <code>elasticfilesystem:DescribeMountTargets</code> action, on either the file system ID
563
544
  * that you specify in <code>FileSystemId</code>, or on the file system of the mount target that
@@ -704,7 +685,6 @@ export declare class EFS extends EFSClient {
704
685
  * <code>TransitionToPrimaryStorageClass</code> to <code>AFTER_1_ACCESS</code>.</p>
705
686
  * </li>
706
687
  * </ul>
707
- *
708
688
  * <p>For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html">EFS Lifecycle Management</a>.</p>
709
689
  * <p>Each Amazon EFS file system supports one lifecycle configuration, which applies to
710
690
  * all files in the file system. If a <code>LifecycleConfiguration</code> object already exists
@@ -729,7 +709,6 @@ export declare class EFS extends EFSClient {
729
709
  * </note>
730
710
  * </li>
731
711
  * </ul>
732
- *
733
712
  * <p>This operation requires permissions for the <code>elasticfilesystem:PutLifecycleConfiguration</code> operation.</p>
734
713
  * <p>To apply a <code>LifecycleConfiguration</code> object to an encrypted file system, you
735
714
  * need the same Key Management Service permissions as when you created the encrypted file system.</p>
@@ -16,9 +16,10 @@ export interface CreateAccessPointCommandOutput extends AccessPointDescription,
16
16
  * the application's own directory and any subdirectories. To learn more, see <a href="https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html">Mounting a file system using EFS access
17
17
  * points</a>.</p>
18
18
  * <note>
19
- * <p>If multiple requests to create access points on the same file system are sent in quick succession, and the file system is
20
- * near the limit of 120 access points, you may experience a throttling response for these requests. This
21
- * is to ensure that the file system does not exceed the stated access point limit.</p>
19
+ * <p>If multiple requests to create access points on the same file system are sent in quick
20
+ * succession, and the file system is near the limit of 1000 access points, you may experience
21
+ * a throttling response for these requests. This is to ensure that the file system does not
22
+ * exceed the stated access point limit.</p>
22
23
  * </note>
23
24
  * <p>This operation requires permissions for the <code>elasticfilesystem:CreateAccessPoint</code> action.</p>
24
25
  * @example
@@ -37,14 +37,12 @@ export interface CreateFileSystemCommandOutput extends FileSystemDescription, __
37
37
  * <p>For more information, see
38
38
  * <a href="https://docs.aws.amazon.com/efs/latest/ug/creating-using-create-fs.html#creating-using-create-fs-part1">Creating a file system</a>
39
39
  * in the <i>Amazon EFS User Guide</i>.</p>
40
- *
41
40
  * <note>
42
41
  * <p>The <code>CreateFileSystem</code> call returns while the file system's lifecycle
43
42
  * state is still <code>creating</code>. You can check the file system creation status by
44
43
  * calling the <a>DescribeFileSystems</a> operation, which among other things returns the file
45
44
  * system state.</p>
46
45
  * </note>
47
- *
48
46
  * <p>This operation accepts an optional <code>PerformanceMode</code> parameter that you
49
47
  * choose for your file system. We recommend <code>generalPurpose</code> performance mode for
50
48
  * most file systems. File systems using the <code>maxIO</code> performance mode can scale to
@@ -52,14 +50,11 @@ export interface CreateFileSystemCommandOutput extends FileSystemDescription, __
52
50
  * higher latencies for most file operations. The performance mode can't be changed after
53
51
  * the file system has been created. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/performance.html#performancemodes.html">Amazon EFS performance
54
52
  * modes</a>.</p>
55
- *
56
53
  * <p>You can set the throughput mode for the file system using the <code>ThroughputMode</code> parameter.</p>
57
- *
58
54
  * <p>After the file system is fully created, Amazon EFS sets its lifecycle state to
59
55
  * <code>available</code>, at which point you can create one or more mount targets for the file
60
56
  * system in your VPC. For more information, see <a>CreateMountTarget</a>. You mount your Amazon EFS file system on an EC2 instances in
61
57
  * your VPC by using the mount target. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/how-it-works.html">Amazon EFS: How it Works</a>. </p>
62
- *
63
58
  * <p> This operation requires permissions for the
64
59
  * <code>elasticfilesystem:CreateFileSystem</code> action. </p>
65
60
  * @example
@@ -46,7 +46,6 @@ export interface CreateMountTargetCommandOutput extends MountTargetDescription,
46
46
  * </ul>
47
47
  * </li>
48
48
  * </ul>
49
- *
50
49
  * <p>After creating the mount target, Amazon EFS returns a response that includes, a
51
50
  * <code>MountTargetId</code> and an <code>IpAddress</code>. You use this IP address when
52
51
  * mounting the file system in an EC2 instance. You can also use the mount target's DNS name
@@ -67,7 +66,6 @@ export interface CreateMountTargetCommandOutput extends MountTargetDescription,
67
66
  * mount targets</p>
68
67
  * </li>
69
68
  * </ul>
70
- *
71
69
  * <p>If the request satisfies the requirements, Amazon EFS does the following:</p>
72
70
  * <ul>
73
71
  * <li>
@@ -56,7 +56,6 @@ export interface CreateReplicationConfigurationCommandOutput extends Replication
56
56
  * </ul>
57
57
  * </li>
58
58
  * </ul>
59
- *
60
59
  * <p>The following properties are set by default:</p>
61
60
  * <ul>
62
61
  * <li>
@@ -73,7 +72,6 @@ export interface CreateReplicationConfigurationCommandOutput extends Replication
73
72
  * throughput mode.</p>
74
73
  * </li>
75
74
  * </ul>
76
- *
77
75
  * <p>The following properties are turned off by default:</p>
78
76
  * <ul>
79
77
  * <li>
@@ -90,7 +88,6 @@ export interface CreateReplicationConfigurationCommandOutput extends Replication
90
88
  * setting.</p>
91
89
  * </li>
92
90
  * </ul>
93
- *
94
91
  * <p>For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/efs-replication.html">Amazon EFS replication</a> in the
95
92
  * <i>Amazon EFS User Guide</i>.</p>
96
93
  * @example
@@ -20,14 +20,12 @@ export interface DeleteFileSystemCommandOutput extends __MetadataBearer {
20
20
  * </note>
21
21
  * <p> You can't delete a file system that is in use. That is, if the file system has
22
22
  * any mount targets, you must first delete them. For more information, see <a>DescribeMountTargets</a> and <a>DeleteMountTarget</a>. </p>
23
- *
24
23
  * <note>
25
24
  * <p>The <code>DeleteFileSystem</code> call returns while the file system state is still
26
25
  * <code>deleting</code>. You can check the file system deletion status by calling the <a>DescribeFileSystems</a> operation, which returns a list of file systems in your
27
26
  * account. If you pass file system ID or creation token for the deleted file system, the <a>DescribeFileSystems</a> returns a <code>404 FileSystemNotFound</code>
28
27
  * error.</p>
29
28
  * </note>
30
- *
31
29
  * <p>This operation requires permissions for the
32
30
  * <code>elasticfilesystem:DeleteFileSystem</code> action.</p>
33
31
  * @example
@@ -9,7 +9,6 @@ export interface DeleteMountTargetCommandOutput extends __MetadataBearer {
9
9
  }
10
10
  /**
11
11
  * <p>Deletes the specified mount target.</p>
12
- *
13
12
  * <p>This operation forcibly breaks any mounts of the file system by using the mount target
14
13
  * that is being deleted, which might disrupt instances or applications using those mounts. To
15
14
  * avoid applications getting cut off abruptly, you might consider unmounting any mounts of the
@@ -26,13 +25,11 @@ export interface DeleteMountTargetCommandOutput extends __MetadataBearer {
26
25
  * </p>
27
26
  * </li>
28
27
  * </ul>
29
- *
30
28
  * <note>
31
29
  * <p>The <code>DeleteMountTarget</code> call returns while the mount target state is still
32
30
  * <code>deleting</code>. You can check the mount target deletion by calling the <a>DescribeMountTargets</a> operation, which returns a list of mount target
33
31
  * descriptions for the given file system. </p>
34
32
  * </note>
35
- *
36
33
  * <p>The operation also requires permissions for the following Amazon EC2 action on the
37
34
  * mount target's network interface:</p>
38
35
  * <ul>
@@ -18,7 +18,6 @@ export interface DeleteTagsCommandOutput extends __MetadataBearer {
18
18
  * includes a tag key that doesn't exist, Amazon EFS ignores it and doesn't cause an
19
19
  * error. For more information about tags and related restrictions, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html">Tag restrictions</a> in the
20
20
  * <i>Billing and Cost Management User Guide</i>.</p>
21
- *
22
21
  * <p>This operation requires permissions for the <code>elasticfilesystem:DeleteTags</code>
23
22
  * action.</p>
24
23
  * @example
@@ -12,20 +12,17 @@ export interface DescribeFileSystemsCommandOutput extends DescribeFileSystemsRes
12
12
  * <code>CreationToken</code> or the <code>FileSystemId</code> is provided. Otherwise, it
13
13
  * returns descriptions of all file systems owned by the caller's Amazon Web Services account in the
14
14
  * Amazon Web Services Region of the endpoint that you're calling.</p>
15
- *
16
15
  * <p>When retrieving all file system descriptions, you can optionally specify the
17
16
  * <code>MaxItems</code> parameter to limit the number of descriptions in a response.
18
- * Currently, this number is automatically set to 10. If more file system descriptions remain,
17
+ * This number is automatically set to 100. If more file system descriptions remain,
19
18
  * Amazon EFS returns a <code>NextMarker</code>, an opaque token, in the response. In this case,
20
19
  * you should send a subsequent request with the <code>Marker</code> request parameter set to the
21
20
  * value of <code>NextMarker</code>. </p>
22
- *
23
21
  * <p>To retrieve a list of your file system descriptions, this operation is used in an
24
22
  * iterative process, where <code>DescribeFileSystems</code> is called first without the
25
23
  * <code>Marker</code> and then the operation continues to call it with the <code>Marker</code>
26
24
  * parameter set to the value of the <code>NextMarker</code> from the previous response until the
27
25
  * response has no <code>NextMarker</code>. </p>
28
- *
29
26
  * <p> The order of file systems returned in the response of one
30
27
  * <code>DescribeFileSystems</code> call and the order of file systems returned across the
31
28
  * responses of a multi-call iteration is unspecified. </p>
@@ -11,7 +11,6 @@ export interface DescribeMountTargetsCommandOutput extends DescribeMountTargetsR
11
11
  * <p>Returns the descriptions of all the current mount targets, or a specific mount target,
12
12
  * for a file system. When requesting all of the current mount targets, the order of mount
13
13
  * targets returned in the response is unspecified.</p>
14
- *
15
14
  * <p>This operation requires permissions for the
16
15
  * <code>elasticfilesystem:DescribeMountTargets</code> action, on either the file system ID
17
16
  * that you specify in <code>FileSystemId</code>, or on the file system of the mount target that
@@ -28,7 +28,6 @@ export interface PutLifecycleConfigurationCommandOutput extends LifecycleConfigu
28
28
  * <code>TransitionToPrimaryStorageClass</code> to <code>AFTER_1_ACCESS</code>.</p>
29
29
  * </li>
30
30
  * </ul>
31
- *
32
31
  * <p>For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/lifecycle-management-efs.html">EFS Lifecycle Management</a>.</p>
33
32
  * <p>Each Amazon EFS file system supports one lifecycle configuration, which applies to
34
33
  * all files in the file system. If a <code>LifecycleConfiguration</code> object already exists
@@ -53,7 +52,6 @@ export interface PutLifecycleConfigurationCommandOutput extends LifecycleConfigu
53
52
  * </note>
54
53
  * </li>
55
54
  * </ul>
56
- *
57
55
  * <p>This operation requires permissions for the <code>elasticfilesystem:PutLifecycleConfiguration</code> operation.</p>
58
56
  * <p>To apply a <code>LifecycleConfiguration</code> object to an encrypted file system, you
59
57
  * need the same Key Management Service permissions as when you created the encrypted file system.</p>
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-efs",
3
3
  "description": "AWS SDK for JavaScript Efs Client for Node.js, Browser and React Native",
4
- "version": "3.245.0",
4
+ "version": "3.253.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -11,7 +11,7 @@
11
11
  "build:types": "tsc -p tsconfig.types.json",
12
12
  "build:types:downlevel": "downlevel-dts dist-types dist-types/ts3.4",
13
13
  "clean": "rimraf ./dist-* && rimraf *.tsbuildinfo",
14
- "generate:client": "(cd ../../ && yarn generate-clients -g ./codegen/sdk-codegen/aws-models/efs.json --keepFiles)"
14
+ "generate:client": "node ../../scripts/generate-clients/single-service --solo efs"
15
15
  },
16
16
  "main": "./dist-cjs/index.js",
17
17
  "types": "./dist-types/index.d.ts",
@@ -20,9 +20,9 @@
20
20
  "dependencies": {
21
21
  "@aws-crypto/sha256-browser": "2.0.0",
22
22
  "@aws-crypto/sha256-js": "2.0.0",
23
- "@aws-sdk/client-sts": "3.245.0",
23
+ "@aws-sdk/client-sts": "3.252.0",
24
24
  "@aws-sdk/config-resolver": "3.234.0",
25
- "@aws-sdk/credential-provider-node": "3.245.0",
25
+ "@aws-sdk/credential-provider-node": "3.252.0",
26
26
  "@aws-sdk/fetch-http-handler": "3.226.0",
27
27
  "@aws-sdk/hash-node": "3.226.0",
28
28
  "@aws-sdk/invalid-dependency": "3.226.0",