aws-sdk 2.1503.0 → 2.1505.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.
Files changed (41) hide show
  1. package/CHANGELOG.md +15 -1
  2. package/README.md +1 -1
  3. package/apis/appsync-2017-07-25.min.json +141 -6
  4. package/apis/b2bi-2022-06-23.examples.json +714 -0
  5. package/apis/b2bi-2022-06-23.min.json +1095 -0
  6. package/apis/b2bi-2022-06-23.paginators.json +28 -0
  7. package/apis/backup-2018-11-15.min.json +855 -84
  8. package/apis/backup-2018-11-15.paginators.json +18 -0
  9. package/apis/controltower-2018-05-10.min.json +80 -12
  10. package/apis/elasticache-2015-02-02.min.json +481 -132
  11. package/apis/elasticache-2015-02-02.paginators.json +12 -0
  12. package/apis/elasticfilesystem-2015-02-01.min.json +66 -32
  13. package/apis/fis-2020-12-01.min.json +366 -15
  14. package/apis/fis-2020-12-01.paginators.json +10 -0
  15. package/apis/metadata.json +3 -0
  16. package/apis/securityhub-2018-10-26.examples.json +433 -8
  17. package/apis/securityhub-2018-10-26.min.json +790 -336
  18. package/apis/securityhub-2018-10-26.paginators.json +12 -0
  19. package/apis/transcribe-2017-10-26.min.json +257 -70
  20. package/apis/transcribe-2017-10-26.paginators.json +5 -0
  21. package/clients/all.d.ts +1 -0
  22. package/clients/all.js +2 -1
  23. package/clients/appsync.d.ts +169 -0
  24. package/clients/b2bi.d.ts +1388 -0
  25. package/clients/b2bi.js +18 -0
  26. package/clients/backup.d.ts +848 -45
  27. package/clients/controltower.d.ts +103 -47
  28. package/clients/efs.d.ts +42 -9
  29. package/clients/elasticache.d.ts +484 -12
  30. package/clients/fis.d.ts +383 -3
  31. package/clients/glue.d.ts +3 -3
  32. package/clients/rds.d.ts +80 -80
  33. package/clients/securityhub.d.ts +603 -13
  34. package/clients/transcribeservice.d.ts +301 -45
  35. package/dist/aws-sdk-core-react-native.js +2 -2
  36. package/dist/aws-sdk-react-native.js +54 -17
  37. package/dist/aws-sdk.js +565 -167
  38. package/dist/aws-sdk.min.js +60 -60
  39. package/lib/config_service_placeholders.d.ts +2 -0
  40. package/lib/core.js +1 -1
  41. package/package.json +1 -1
@@ -12,19 +12,19 @@ declare class ControlTower extends Service {
12
12
  constructor(options?: ControlTower.Types.ClientConfiguration)
13
13
  config: Config & ControlTower.Types.ClientConfiguration;
14
14
  /**
15
- * Creates a new landing zone. This starts an asynchronous operation that creates and configures a landing zone based on the parameters specified in the manifest JSON file.
15
+ * Creates a new landing zone. This API call starts an asynchronous operation that creates and configures a landing zone, based on the parameters specified in the manifest JSON file.
16
16
  */
17
17
  createLandingZone(params: ControlTower.Types.CreateLandingZoneInput, callback?: (err: AWSError, data: ControlTower.Types.CreateLandingZoneOutput) => void): Request<ControlTower.Types.CreateLandingZoneOutput, AWSError>;
18
18
  /**
19
- * Creates a new landing zone. This starts an asynchronous operation that creates and configures a landing zone based on the parameters specified in the manifest JSON file.
19
+ * Creates a new landing zone. This API call starts an asynchronous operation that creates and configures a landing zone, based on the parameters specified in the manifest JSON file.
20
20
  */
21
21
  createLandingZone(callback?: (err: AWSError, data: ControlTower.Types.CreateLandingZoneOutput) => void): Request<ControlTower.Types.CreateLandingZoneOutput, AWSError>;
22
22
  /**
23
- * This decommissions a landing zone. This starts an asynchronous operation that deletes Amazon Web Services Control Tower resources deployed in Amazon Web Services Control Tower managed accounts.
23
+ * Decommissions a landing zone. This API call starts an asynchronous operation that deletes Amazon Web Services Control Tower resources deployed in accounts managed by Amazon Web Services Control Tower.
24
24
  */
25
25
  deleteLandingZone(params: ControlTower.Types.DeleteLandingZoneInput, callback?: (err: AWSError, data: ControlTower.Types.DeleteLandingZoneOutput) => void): Request<ControlTower.Types.DeleteLandingZoneOutput, AWSError>;
26
26
  /**
27
- * This decommissions a landing zone. This starts an asynchronous operation that deletes Amazon Web Services Control Tower resources deployed in Amazon Web Services Control Tower managed accounts.
27
+ * Decommissions a landing zone. This API call starts an asynchronous operation that deletes Amazon Web Services Control Tower resources deployed in accounts managed by Amazon Web Services Control Tower.
28
28
  */
29
29
  deleteLandingZone(callback?: (err: AWSError, data: ControlTower.Types.DeleteLandingZoneOutput) => void): Request<ControlTower.Types.DeleteLandingZoneOutput, AWSError>;
30
30
  /**
@@ -60,19 +60,19 @@ declare class ControlTower extends Service {
60
60
  */
61
61
  getEnabledControl(callback?: (err: AWSError, data: ControlTower.Types.GetEnabledControlOutput) => void): Request<ControlTower.Types.GetEnabledControlOutput, AWSError>;
62
62
  /**
63
- * Returns details about the landing zone. Displays a message in case of error.
63
+ * Returns details about the landing zone. Displays a message in case of error.
64
64
  */
65
65
  getLandingZone(params: ControlTower.Types.GetLandingZoneInput, callback?: (err: AWSError, data: ControlTower.Types.GetLandingZoneOutput) => void): Request<ControlTower.Types.GetLandingZoneOutput, AWSError>;
66
66
  /**
67
- * Returns details about the landing zone. Displays a message in case of error.
67
+ * Returns details about the landing zone. Displays a message in case of error.
68
68
  */
69
69
  getLandingZone(callback?: (err: AWSError, data: ControlTower.Types.GetLandingZoneOutput) => void): Request<ControlTower.Types.GetLandingZoneOutput, AWSError>;
70
70
  /**
71
- * Returns the status of the specified landing zone operation. Details for an operation are available for X days.
71
+ * Returns the status of the specified landing zone operation. Details for an operation are available for 60 days.
72
72
  */
73
73
  getLandingZoneOperation(params: ControlTower.Types.GetLandingZoneOperationInput, callback?: (err: AWSError, data: ControlTower.Types.GetLandingZoneOperationOutput) => void): Request<ControlTower.Types.GetLandingZoneOperationOutput, AWSError>;
74
74
  /**
75
- * Returns the status of the specified landing zone operation. Details for an operation are available for X days.
75
+ * Returns the status of the specified landing zone operation. Details for an operation are available for 60 days.
76
76
  */
77
77
  getLandingZoneOperation(callback?: (err: AWSError, data: ControlTower.Types.GetLandingZoneOperationOutput) => void): Request<ControlTower.Types.GetLandingZoneOperationOutput, AWSError>;
78
78
  /**
@@ -84,11 +84,11 @@ declare class ControlTower extends Service {
84
84
  */
85
85
  listEnabledControls(callback?: (err: AWSError, data: ControlTower.Types.ListEnabledControlsOutput) => void): Request<ControlTower.Types.ListEnabledControlsOutput, AWSError>;
86
86
  /**
87
- * Returns the landing zone ARN for the landing zone deployed in your managed account. This API also creates an ARN for existing accounts that do not yet have a landing zone ARN. The return limit is one landing zone ARN.
87
+ * Returns the landing zone ARN for the landing zone deployed in your managed account. This API also creates an ARN for existing accounts that do not yet have a landing zone ARN. Returns one landing zone ARN.
88
88
  */
89
89
  listLandingZones(params: ControlTower.Types.ListLandingZonesInput, callback?: (err: AWSError, data: ControlTower.Types.ListLandingZonesOutput) => void): Request<ControlTower.Types.ListLandingZonesOutput, AWSError>;
90
90
  /**
91
- * Returns the landing zone ARN for the landing zone deployed in your managed account. This API also creates an ARN for existing accounts that do not yet have a landing zone ARN. The return limit is one landing zone ARN.
91
+ * Returns the landing zone ARN for the landing zone deployed in your managed account. This API also creates an ARN for existing accounts that do not yet have a landing zone ARN. Returns one landing zone ARN.
92
92
  */
93
93
  listLandingZones(callback?: (err: AWSError, data: ControlTower.Types.ListLandingZonesOutput) => void): Request<ControlTower.Types.ListLandingZonesOutput, AWSError>;
94
94
  /**
@@ -100,11 +100,11 @@ declare class ControlTower extends Service {
100
100
  */
101
101
  listTagsForResource(callback?: (err: AWSError, data: ControlTower.Types.ListTagsForResourceOutput) => void): Request<ControlTower.Types.ListTagsForResourceOutput, AWSError>;
102
102
  /**
103
- * This API call resets a landing zone. It starts an asynchronous operation that resets the landing zone to the parameters specified in its original configuration.
103
+ * This API call resets a landing zone. It starts an asynchronous operation that resets the landing zone to the parameters specified in its original configuration.
104
104
  */
105
105
  resetLandingZone(params: ControlTower.Types.ResetLandingZoneInput, callback?: (err: AWSError, data: ControlTower.Types.ResetLandingZoneOutput) => void): Request<ControlTower.Types.ResetLandingZoneOutput, AWSError>;
106
106
  /**
107
- * This API call resets a landing zone. It starts an asynchronous operation that resets the landing zone to the parameters specified in its original configuration.
107
+ * This API call resets a landing zone. It starts an asynchronous operation that resets the landing zone to the parameters specified in its original configuration.
108
108
  */
109
109
  resetLandingZone(callback?: (err: AWSError, data: ControlTower.Types.ResetLandingZoneOutput) => void): Request<ControlTower.Types.ResetLandingZoneOutput, AWSError>;
110
110
  /**
@@ -124,11 +124,19 @@ declare class ControlTower extends Service {
124
124
  */
125
125
  untagResource(callback?: (err: AWSError, data: ControlTower.Types.UntagResourceOutput) => void): Request<ControlTower.Types.UntagResourceOutput, AWSError>;
126
126
  /**
127
- * This API call updates the landing zone. It starts an asynchronous operation that updates the landing zone based on the new landing zone version or the updated parameters specified in the updated manifest file.
127
+ * Updates the configuration of an already enabled control. If the enabled control shows an EnablementStatus of SUCCEEDED, supply parameters that are different from the currently configured parameters. Otherwise, Amazon Web Services Control Tower will not accept the request. If the enabled control shows an EnablementStatus of FAILED, Amazon Web Services Control Tower will update the control to match any valid parameters that you supply. If the DriftSummary status for the control shows as DRIFTED, you cannot call this API. Instead, you can update the control by calling DisableControl and again calling EnableControl, or you can run an extending governance operation. For usage examples, see the Amazon Web Services Control Tower User Guide
128
+ */
129
+ updateEnabledControl(params: ControlTower.Types.UpdateEnabledControlInput, callback?: (err: AWSError, data: ControlTower.Types.UpdateEnabledControlOutput) => void): Request<ControlTower.Types.UpdateEnabledControlOutput, AWSError>;
130
+ /**
131
+ * Updates the configuration of an already enabled control. If the enabled control shows an EnablementStatus of SUCCEEDED, supply parameters that are different from the currently configured parameters. Otherwise, Amazon Web Services Control Tower will not accept the request. If the enabled control shows an EnablementStatus of FAILED, Amazon Web Services Control Tower will update the control to match any valid parameters that you supply. If the DriftSummary status for the control shows as DRIFTED, you cannot call this API. Instead, you can update the control by calling DisableControl and again calling EnableControl, or you can run an extending governance operation. For usage examples, see the Amazon Web Services Control Tower User Guide
132
+ */
133
+ updateEnabledControl(callback?: (err: AWSError, data: ControlTower.Types.UpdateEnabledControlOutput) => void): Request<ControlTower.Types.UpdateEnabledControlOutput, AWSError>;
134
+ /**
135
+ * This API call updates the landing zone. It starts an asynchronous operation that updates the landing zone based on the new landing zone version, or on the changed parameters specified in the updated manifest file.
128
136
  */
129
137
  updateLandingZone(params: ControlTower.Types.UpdateLandingZoneInput, callback?: (err: AWSError, data: ControlTower.Types.UpdateLandingZoneOutput) => void): Request<ControlTower.Types.UpdateLandingZoneOutput, AWSError>;
130
138
  /**
131
- * This API call updates the landing zone. It starts an asynchronous operation that updates the landing zone based on the new landing zone version or the updated parameters specified in the updated manifest file.
139
+ * This API call updates the landing zone. It starts an asynchronous operation that updates the landing zone based on the new landing zone version, or on the changed parameters specified in the updated manifest file.
132
140
  */
133
141
  updateLandingZone(callback?: (err: AWSError, data: ControlTower.Types.UpdateLandingZoneOutput) => void): Request<ControlTower.Types.UpdateLandingZoneOutput, AWSError>;
134
142
  }
@@ -158,7 +166,7 @@ declare namespace ControlTower {
158
166
  statusMessage?: String;
159
167
  }
160
168
  export type ControlOperationStatus = "SUCCEEDED"|"FAILED"|"IN_PROGRESS"|string;
161
- export type ControlOperationType = "ENABLE_CONTROL"|"DISABLE_CONTROL"|string;
169
+ export type ControlOperationType = "ENABLE_CONTROL"|"DISABLE_CONTROL"|"UPDATE_ENABLED_CONTROL"|string;
162
170
  export interface CreateLandingZoneInput {
163
171
  /**
164
172
  * The manifest.yaml file is a text file that describes your Amazon Web Services resources. For examples, review The manifest file.
@@ -169,35 +177,35 @@ declare namespace ControlTower {
169
177
  */
170
178
  tags?: TagMap;
171
179
  /**
172
- * The landing zone version.
180
+ * The landing zone version, for example, 3.0.
173
181
  */
174
182
  version: LandingZoneVersion;
175
183
  }
176
184
  export interface CreateLandingZoneOutput {
177
185
  /**
178
- * The ARN of the landing zone.
186
+ * The ARN of the landing zone resource.
179
187
  */
180
188
  arn: Arn;
181
189
  /**
182
- * A unique identifier assigned to a CreateLandingZone operation. You can use this identifier as an input of GetLandingZoneOperation to check the operation's status.
190
+ * A unique identifier assigned to a CreateLandingZone operation. You can use this identifier as an input of GetLandingZoneOperation to check the operation's status.
183
191
  */
184
192
  operationIdentifier: OperationIdentifier;
185
193
  }
186
194
  export interface DeleteLandingZoneInput {
187
195
  /**
188
- * The unique identifier of the landing zone.
196
+ * The unique identifier of the landing zone.
189
197
  */
190
198
  landingZoneIdentifier: String;
191
199
  }
192
200
  export interface DeleteLandingZoneOutput {
193
201
  /**
194
- * A unique identifier assigned to a DeleteLandingZone operation. You can use this identifier as an input of GetLandingZoneOperation to check the operation's status.
202
+ * &gt;A unique identifier assigned to a DeleteLandingZone operation. You can use this identifier as an input parameter of GetLandingZoneOperation to check the operation's status.
195
203
  */
196
204
  operationIdentifier: OperationIdentifier;
197
205
  }
198
206
  export interface DisableControlInput {
199
207
  /**
200
- * The ARN of the control. Only Strongly recommended and Elective controls are permitted, with the exception of the Region deny control. For information on how to find the controlIdentifier, see the overview page.
208
+ * The ARN of the control. Only Strongly recommended and Elective controls are permitted, with the exception of the landing zone Region deny control. For information on how to find the controlIdentifier, see the overview page.
201
209
  */
202
210
  controlIdentifier: ControlIdentifier;
203
211
  /**
@@ -211,6 +219,8 @@ declare namespace ControlTower {
211
219
  */
212
220
  operationIdentifier: OperationIdentifier;
213
221
  }
222
+ export interface Document {
223
+ }
214
224
  export type DriftStatus = "DRIFTED"|"IN_SYNC"|"NOT_CHECKING"|"UNKNOWN"|string;
215
225
  export interface DriftStatusSummary {
216
226
  /**
@@ -220,9 +230,13 @@ declare namespace ControlTower {
220
230
  }
221
231
  export interface EnableControlInput {
222
232
  /**
223
- * The ARN of the control. Only Strongly recommended and Elective controls are permitted, with the exception of the Region deny control. For information on how to find the controlIdentifier, see the overview page.
233
+ * The ARN of the control. Only Strongly recommended and Elective controls are permitted, with the exception of the landing zone Region deny control. For information on how to find the controlIdentifier, see the overview page.
224
234
  */
225
235
  controlIdentifier: ControlIdentifier;
236
+ /**
237
+ * An array of EnabledControlParameter objects
238
+ */
239
+ parameters?: EnabledControlParameters;
226
240
  /**
227
241
  * Tags to be applied to the EnabledControl resource.
228
242
  */
@@ -255,6 +269,10 @@ declare namespace ControlTower {
255
269
  * The drift status of the enabled control.
256
270
  */
257
271
  driftStatusSummary?: DriftStatusSummary;
272
+ /**
273
+ * Array of EnabledControlParameter objects.
274
+ */
275
+ parameters?: EnabledControlParameterSummaries;
258
276
  /**
259
277
  * The deployment summary of the enabled control.
260
278
  */
@@ -268,6 +286,28 @@ declare namespace ControlTower {
268
286
  */
269
287
  targetRegions?: TargetRegions;
270
288
  }
289
+ export interface EnabledControlParameter {
290
+ /**
291
+ * The key of a key/value pair. It is of type string.
292
+ */
293
+ key: String;
294
+ /**
295
+ * The value of a key/value pair. It can be of type array string, number, object, or boolean.
296
+ */
297
+ value: Document;
298
+ }
299
+ export type EnabledControlParameterSummaries = EnabledControlParameterSummary[];
300
+ export interface EnabledControlParameterSummary {
301
+ /**
302
+ * The key of a key/value pair.
303
+ */
304
+ key: String;
305
+ /**
306
+ * The value of a key/value pair.
307
+ */
308
+ value: Document;
309
+ }
310
+ export type EnabledControlParameters = EnabledControlParameter[];
271
311
  export interface EnabledControlSummary {
272
312
  /**
273
313
  * The ARN of the enabled control.
@@ -286,7 +326,7 @@ declare namespace ControlTower {
286
326
  */
287
327
  statusSummary?: EnablementStatusSummary;
288
328
  /**
289
- * The ARN of the organizational unit.
329
+ * The ARN of the organizational unit.
290
330
  */
291
331
  targetIdentifier?: TargetIdentifier;
292
332
  }
@@ -328,39 +368,39 @@ declare namespace ControlTower {
328
368
  }
329
369
  export interface GetLandingZoneInput {
330
370
  /**
331
- * The unique identifier of the landing zone.
371
+ * The unique identifier of the landing zone.
332
372
  */
333
373
  landingZoneIdentifier: String;
334
374
  }
335
375
  export interface GetLandingZoneOperationInput {
336
376
  /**
337
- * A unique identifier assigned to a landing zone operation.
377
+ * A unique identifier assigned to a landing zone operation.
338
378
  */
339
379
  operationIdentifier: OperationIdentifier;
340
380
  }
341
381
  export interface GetLandingZoneOperationOutput {
342
382
  /**
343
- * The landing zone operation details.
383
+ * Details about a landing zone operation.
344
384
  */
345
385
  operationDetails: LandingZoneOperationDetail;
346
386
  }
347
387
  export interface GetLandingZoneOutput {
348
388
  /**
349
- * Information about the landing zone.
389
+ * Information about the landing zone.
350
390
  */
351
391
  landingZone: LandingZoneDetail;
352
392
  }
353
393
  export interface LandingZoneDetail {
354
394
  /**
355
- * The ARN of the landing zone.
395
+ * The ARN of the landing zone.
356
396
  */
357
397
  arn?: Arn;
358
398
  /**
359
- * The drift status of the landing zone.
399
+ * The drift status of the landing zone.
360
400
  */
361
401
  driftStatus?: LandingZoneDriftStatusSummary;
362
402
  /**
363
- * The latest available version of the landing zone.
403
+ * The latest available version of the landing zone.
364
404
  */
365
405
  latestAvailableVersion?: LandingZoneVersion;
366
406
  /**
@@ -368,11 +408,11 @@ declare namespace ControlTower {
368
408
  */
369
409
  manifest: Manifest;
370
410
  /**
371
- * The landing zone deployment status. Valid values: ACTIVE: The landing zone is actively deployed. PROCESSING: The landing zone is processing deployment. FAILED: The landing zone failed deployment.
411
+ * The landing zone deployment status.
372
412
  */
373
413
  status?: LandingZoneStatus;
374
414
  /**
375
- * The landing zone's current deployed version.
415
+ * The landing zone's current deployed version.
376
416
  */
377
417
  version: LandingZoneVersion;
378
418
  }
@@ -385,7 +425,7 @@ declare namespace ControlTower {
385
425
  }
386
426
  export interface LandingZoneOperationDetail {
387
427
  /**
388
- * The landing zone operation end time.
428
+ * The landing zone operation end time.
389
429
  */
390
430
  endTime?: Timestamp;
391
431
  /**
@@ -393,15 +433,15 @@ declare namespace ControlTower {
393
433
  */
394
434
  operationType?: LandingZoneOperationType;
395
435
  /**
396
- * The landing zone operation start time.
436
+ * The landing zone operation start time.
397
437
  */
398
438
  startTime?: Timestamp;
399
439
  /**
400
- * The landing zone operation status. Valid values: SUCCEEDED: The landing zone operation succeeded. IN_PROGRESS: The landing zone operation is in progress. FAILED: The landing zone operation failed.
440
+ * Valid values: SUCCEEDED: The landing zone operation succeeded. IN_PROGRESS: The landing zone operation is in progress. FAILED: The landing zone operation failed.
401
441
  */
402
442
  status?: LandingZoneOperationStatus;
403
443
  /**
404
- * If the operation result is FAILED, this string contains a message explaining why the operation failed.
444
+ * If the operation result is FAILED, this string contains a message explaining why the operation failed.
405
445
  */
406
446
  statusMessage?: String;
407
447
  }
@@ -410,7 +450,7 @@ declare namespace ControlTower {
410
450
  export type LandingZoneStatus = "ACTIVE"|"PROCESSING"|"FAILED"|string;
411
451
  export interface LandingZoneSummary {
412
452
  /**
413
- * The ARN of the landing zone.
453
+ * The ARN of the landing zone.
414
454
  */
415
455
  arn?: Arn;
416
456
  }
@@ -435,28 +475,28 @@ declare namespace ControlTower {
435
475
  */
436
476
  enabledControls: EnabledControls;
437
477
  /**
438
- * Retrieves the next page of results. If the string is empty, the current response is the end of the results.
478
+ * Retrieves the next page of results. If the string is empty, the response is the end of the results.
439
479
  */
440
480
  nextToken?: String;
441
481
  }
442
482
  export interface ListLandingZonesInput {
443
483
  /**
444
- * The maximum number of returned landing zone ARNs.
484
+ * The maximum number of returned landing zone ARNs, which is one.
445
485
  */
446
486
  maxResults?: ListLandingZonesMaxResults;
447
487
  /**
448
- * The token to continue the list from a previous API call with the same parameters.
488
+ * The token to continue the list from a previous API call with the same parameters.
449
489
  */
450
490
  nextToken?: String;
451
491
  }
452
492
  export type ListLandingZonesMaxResults = number;
453
493
  export interface ListLandingZonesOutput {
454
494
  /**
455
- * The ARN of the landing zone.
495
+ * The ARN of the landing zone.
456
496
  */
457
497
  landingZones: ListLandingZonesOutputLandingZonesList;
458
498
  /**
459
- * Retrieves the next page of results. If the string is empty, the current response is the end of the results.
499
+ * Retrieves the next page of results. If the string is empty, the response is the end of the results.
460
500
  */
461
501
  nextToken?: String;
462
502
  }
@@ -486,13 +526,13 @@ declare namespace ControlTower {
486
526
  export type RegionName = string;
487
527
  export interface ResetLandingZoneInput {
488
528
  /**
489
- * The unique identifier of the landing zone.
529
+ * The unique identifier of the landing zone.
490
530
  */
491
531
  landingZoneIdentifier: String;
492
532
  }
493
533
  export interface ResetLandingZoneOutput {
494
534
  /**
495
- * A unique identifier assigned to a ResetLandingZone operation. You can use this identifier as an input of GetLandingZoneOperation to check the operation's status.
535
+ * A unique identifier assigned to a ResetLandingZone operation. You can use this identifier as an input parameter of GetLandingZoneOperation to check the operation's status.
496
536
  */
497
537
  operationIdentifier: OperationIdentifier;
498
538
  }
@@ -529,17 +569,33 @@ declare namespace ControlTower {
529
569
  }
530
570
  export interface UntagResourceOutput {
531
571
  }
572
+ export interface UpdateEnabledControlInput {
573
+ /**
574
+ * The ARN of the enabled control that will be updated.
575
+ */
576
+ enabledControlIdentifier: Arn;
577
+ /**
578
+ * A key/value pair, where Key is of type String and Value is of type Document.
579
+ */
580
+ parameters: EnabledControlParameters;
581
+ }
582
+ export interface UpdateEnabledControlOutput {
583
+ /**
584
+ * The operation identifier for this UpdateEnabledControl operation.
585
+ */
586
+ operationIdentifier: OperationIdentifier;
587
+ }
532
588
  export interface UpdateLandingZoneInput {
533
589
  /**
534
- * The unique identifier of the landing zone.
590
+ * The unique identifier of the landing zone.
535
591
  */
536
592
  landingZoneIdentifier: String;
537
593
  /**
538
- * The manifest.yaml file is a text file that describes your Amazon Web Services resources. For examples, review The manifest file
594
+ * The manifest.yaml file is a text file that describes your Amazon Web Services resources. For examples, review The manifest file.
539
595
  */
540
596
  manifest: Manifest;
541
597
  /**
542
- * The landing zone version.
598
+ * The landing zone version, for example, 3.2.
543
599
  */
544
600
  version: LandingZoneVersion;
545
601
  }
package/clients/efs.d.ts CHANGED
@@ -36,11 +36,11 @@ declare class EFS extends Service {
36
36
  */
37
37
  createMountTarget(callback?: (err: AWSError, data: EFS.Types.MountTargetDescription) => void): Request<EFS.Types.MountTargetDescription, AWSError>;
38
38
  /**
39
- * Creates a replication configuration that replicates an existing EFS file system to a new, read-only file system. For more information, see Amazon EFS replication in the Amazon EFS User Guide. The replication configuration specifies the following: Source file system - An existing EFS file system that you want replicated. The source file system cannot be a destination file system in an existing replication configuration. Destination file system configuration - The configuration of the destination file system to which the source file system will be replicated. There can only be one destination file system in a replication configuration. The destination file system configuration consists of the following properties: Amazon Web Services Region - The Amazon Web Services Region in which the destination file system is created. Amazon EFS replication is available in all Amazon Web Services Regions in which EFS is available. To use EFS replication in a Region that is disabled by default, you must first opt in to the Region. For more information, see Managing Amazon Web Services Regions in the Amazon Web Services General Reference Reference Guide Availability Zone - If you want the destination file system to use EFS One Zone availability, you must specify the Availability Zone to create the file system in. For more information about EFS storage classes, see Amazon EFS storage classes in the Amazon EFS User Guide. Encryption - All destination file systems are created with encryption at rest enabled. You can specify the Key Management Service (KMS) key that is used to encrypt the destination file system. If you don't specify a KMS key, your service-managed KMS key for Amazon EFS is used. After the file system is created, you cannot change the KMS key. The following properties are set by default: Performance mode - The destination file system's performance mode matches that of the source file system, unless the destination file system uses EFS One Zone storage. In that case, the General Purpose performance mode is used. The performance mode cannot be changed. Throughput mode - The destination file system's throughput mode matches that of the source file system. After the file system is created, you can modify the throughput mode. The following properties are turned off by default: Lifecycle management – Lifecycle management is not enabled on the destination file system. After the destination file system is created, you can enable it. Automatic backups – Automatic daily backups are enabled on the destination file system. After the file system is created, you can change this setting. For more information, see Amazon EFS replication in the Amazon EFS User Guide.
39
+ * Creates a replication configuration that replicates an existing EFS file system to a new, read-only file system. For more information, see Amazon EFS replication in the Amazon EFS User Guide. The replication configuration specifies the following: Source file system The EFS file system that you want replicated. The source file system cannot be a destination file system in an existing replication configuration. Amazon Web Services Region – The Amazon Web Services Region in which the destination file system is created. Amazon EFS replication is available in all Amazon Web Services Regions in which EFS is available. The Region must be enabled. For more information, see Managing Amazon Web Services Regions in the Amazon Web Services General Reference Reference Guide. Destination file system configuration The configuration of the destination file system to which the source file system will be replicated. There can only be one destination file system in a replication configuration. Parameters for the replication configuration include: File system ID The ID of the destination file system for the replication. If no ID is provided, then EFS creates a new file system with the default settings. For existing file systems, the file system's replication overwrite protection must be disabled. For more information, see Replicating to an existing file system. Availability Zone If you want the destination file system to use One Zone storage, you must specify the Availability Zone to create the file system in. For more information, see EFS file system types in the Amazon EFS User Guide. Encryption All destination file systems are created with encryption at rest enabled. You can specify the Key Management Service (KMS) key that is used to encrypt the destination file system. If you don't specify a KMS key, your service-managed KMS key for Amazon EFS is used. After the file system is created, you cannot change the KMS key. After the file system is created, you cannot change the KMS key. For new destination file systems, the following properties are set by default: Performance mode - The destination file system's performance mode matches that of the source file system, unless the destination file system uses EFS One Zone storage. In that case, the General Purpose performance mode is used. The performance mode cannot be changed. Throughput mode - The destination file system's throughput mode matches that of the source file system. After the file system is created, you can modify the throughput mode. Lifecycle management – Lifecycle management is not enabled on the destination file system. After the destination file system is created, you can enable lifecycle management. Automatic backups – Automatic daily backups are enabled on the destination file system. After the file system is created, you can change this setting. For more information, see Amazon EFS replication in the Amazon EFS User Guide.
40
40
  */
41
41
  createReplicationConfiguration(params: EFS.Types.CreateReplicationConfigurationRequest, callback?: (err: AWSError, data: EFS.Types.ReplicationConfigurationDescription) => void): Request<EFS.Types.ReplicationConfigurationDescription, AWSError>;
42
42
  /**
43
- * Creates a replication configuration that replicates an existing EFS file system to a new, read-only file system. For more information, see Amazon EFS replication in the Amazon EFS User Guide. The replication configuration specifies the following: Source file system - An existing EFS file system that you want replicated. The source file system cannot be a destination file system in an existing replication configuration. Destination file system configuration - The configuration of the destination file system to which the source file system will be replicated. There can only be one destination file system in a replication configuration. The destination file system configuration consists of the following properties: Amazon Web Services Region - The Amazon Web Services Region in which the destination file system is created. Amazon EFS replication is available in all Amazon Web Services Regions in which EFS is available. To use EFS replication in a Region that is disabled by default, you must first opt in to the Region. For more information, see Managing Amazon Web Services Regions in the Amazon Web Services General Reference Reference Guide Availability Zone - If you want the destination file system to use EFS One Zone availability, you must specify the Availability Zone to create the file system in. For more information about EFS storage classes, see Amazon EFS storage classes in the Amazon EFS User Guide. Encryption - All destination file systems are created with encryption at rest enabled. You can specify the Key Management Service (KMS) key that is used to encrypt the destination file system. If you don't specify a KMS key, your service-managed KMS key for Amazon EFS is used. After the file system is created, you cannot change the KMS key. The following properties are set by default: Performance mode - The destination file system's performance mode matches that of the source file system, unless the destination file system uses EFS One Zone storage. In that case, the General Purpose performance mode is used. The performance mode cannot be changed. Throughput mode - The destination file system's throughput mode matches that of the source file system. After the file system is created, you can modify the throughput mode. The following properties are turned off by default: Lifecycle management – Lifecycle management is not enabled on the destination file system. After the destination file system is created, you can enable it. Automatic backups – Automatic daily backups are enabled on the destination file system. After the file system is created, you can change this setting. For more information, see Amazon EFS replication in the Amazon EFS User Guide.
43
+ * Creates a replication configuration that replicates an existing EFS file system to a new, read-only file system. For more information, see Amazon EFS replication in the Amazon EFS User Guide. The replication configuration specifies the following: Source file system The EFS file system that you want replicated. The source file system cannot be a destination file system in an existing replication configuration. Amazon Web Services Region – The Amazon Web Services Region in which the destination file system is created. Amazon EFS replication is available in all Amazon Web Services Regions in which EFS is available. The Region must be enabled. For more information, see Managing Amazon Web Services Regions in the Amazon Web Services General Reference Reference Guide. Destination file system configuration The configuration of the destination file system to which the source file system will be replicated. There can only be one destination file system in a replication configuration. Parameters for the replication configuration include: File system ID The ID of the destination file system for the replication. If no ID is provided, then EFS creates a new file system with the default settings. For existing file systems, the file system's replication overwrite protection must be disabled. For more information, see Replicating to an existing file system. Availability Zone If you want the destination file system to use One Zone storage, you must specify the Availability Zone to create the file system in. For more information, see EFS file system types in the Amazon EFS User Guide. Encryption All destination file systems are created with encryption at rest enabled. You can specify the Key Management Service (KMS) key that is used to encrypt the destination file system. If you don't specify a KMS key, your service-managed KMS key for Amazon EFS is used. After the file system is created, you cannot change the KMS key. After the file system is created, you cannot change the KMS key. For new destination file systems, the following properties are set by default: Performance mode - The destination file system's performance mode matches that of the source file system, unless the destination file system uses EFS One Zone storage. In that case, the General Purpose performance mode is used. The performance mode cannot be changed. Throughput mode - The destination file system's throughput mode matches that of the source file system. After the file system is created, you can modify the throughput mode. Lifecycle management – Lifecycle management is not enabled on the destination file system. After the destination file system is created, you can enable lifecycle management. Automatic backups – Automatic daily backups are enabled on the destination file system. After the file system is created, you can change this setting. For more information, see Amazon EFS replication in the Amazon EFS User Guide.
44
44
  */
45
45
  createReplicationConfiguration(callback?: (err: AWSError, data: EFS.Types.ReplicationConfigurationDescription) => void): Request<EFS.Types.ReplicationConfigurationDescription, AWSError>;
46
46
  /**
@@ -84,11 +84,11 @@ declare class EFS extends Service {
84
84
  */
85
85
  deleteMountTarget(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
86
86
  /**
87
- * Deletes an existing replication configuration. Deleting a replication configuration ends the replication process. After a replication configuration is deleted, the destination file system is no longer read-only. You can write to the destination file system after its status becomes Writeable.
87
+ * Deletes a replication configuration. Deleting a replication configuration ends the replication process. After a replication configuration is deleted, the destination file system becomes Writeable and its replication overwrite protection is re-enabled. For more information, see Delete a replication configuration. This operation requires permissions for the elasticfilesystem:DeleteReplicationConfiguration action.
88
88
  */
89
89
  deleteReplicationConfiguration(params: EFS.Types.DeleteReplicationConfigurationRequest, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
90
90
  /**
91
- * Deletes an existing replication configuration. Deleting a replication configuration ends the replication process. After a replication configuration is deleted, the destination file system is no longer read-only. You can write to the destination file system after its status becomes Writeable.
91
+ * Deletes a replication configuration. Deleting a replication configuration ends the replication process. After a replication configuration is deleted, the destination file system becomes Writeable and its replication overwrite protection is re-enabled. For more information, see Delete a replication configuration. This operation requires permissions for the elasticfilesystem:DeleteReplicationConfiguration action.
92
92
  */
93
93
  deleteReplicationConfiguration(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
94
94
  /**
@@ -140,11 +140,11 @@ declare class EFS extends Service {
140
140
  */
141
141
  describeFileSystems(callback?: (err: AWSError, data: EFS.Types.DescribeFileSystemsResponse) => void): Request<EFS.Types.DescribeFileSystemsResponse, AWSError>;
142
142
  /**
143
- * Returns the current LifecycleConfiguration object for the specified Amazon EFS file system. Llifecycle management uses the LifecycleConfiguration object to identify when to move files between storage classes. For a file system without a LifecycleConfiguration object, the call returns an empty array in the response. This operation requires permissions for the elasticfilesystem:DescribeLifecycleConfiguration operation.
143
+ * Returns the current LifecycleConfiguration object for the specified Amazon EFS file system. Lifecycle management uses the LifecycleConfiguration object to identify when to move files between storage classes. For a file system without a LifecycleConfiguration object, the call returns an empty array in the response. This operation requires permissions for the elasticfilesystem:DescribeLifecycleConfiguration operation.
144
144
  */
145
145
  describeLifecycleConfiguration(params: EFS.Types.DescribeLifecycleConfigurationRequest, callback?: (err: AWSError, data: EFS.Types.LifecycleConfigurationDescription) => void): Request<EFS.Types.LifecycleConfigurationDescription, AWSError>;
146
146
  /**
147
- * Returns the current LifecycleConfiguration object for the specified Amazon EFS file system. Llifecycle management uses the LifecycleConfiguration object to identify when to move files between storage classes. For a file system without a LifecycleConfiguration object, the call returns an empty array in the response. This operation requires permissions for the elasticfilesystem:DescribeLifecycleConfiguration operation.
147
+ * Returns the current LifecycleConfiguration object for the specified Amazon EFS file system. Lifecycle management uses the LifecycleConfiguration object to identify when to move files between storage classes. For a file system without a LifecycleConfiguration object, the call returns an empty array in the response. This operation requires permissions for the elasticfilesystem:DescribeLifecycleConfiguration operation.
148
148
  */
149
149
  describeLifecycleConfiguration(callback?: (err: AWSError, data: EFS.Types.LifecycleConfigurationDescription) => void): Request<EFS.Types.LifecycleConfigurationDescription, AWSError>;
150
150
  /**
@@ -220,11 +220,11 @@ declare class EFS extends Service {
220
220
  */
221
221
  putFileSystemPolicy(callback?: (err: AWSError, data: EFS.Types.FileSystemPolicyDescription) => void): Request<EFS.Types.FileSystemPolicyDescription, AWSError>;
222
222
  /**
223
- * Use this action to manage storage of your file system. A LifecycleConfiguration consists of one or more LifecyclePolicy objects that define the following: TransitionToIA – When to move files in the file system from primary storage (Standard storage class) into the Infrequent Access (IA) storage. TransitionToArchive – When to move files in the file system from their current storage class (either IA or Standard storage) into the Archive storage. File systems cannot transition into Archive storage before transitioning into IA storage. Therefore, TransitionToArchive must either not be set or must be later than TransitionToIA. The Archive storage class is available only for file systems that use the Elastic Throughput mode and the General Purpose Performance mode. TransitionToPrimaryStorageClass – Whether to move files in the file system back to primary storage (Standard storage class) after they are accessed in IA or Archive storage. For more information, see Managing file system storage. Each Amazon EFS file system supports one lifecycle configuration, which applies to all files in the file system. If a LifecycleConfiguration object already exists for the specified file system, a PutLifecycleConfiguration call modifies the existing configuration. A PutLifecycleConfiguration call with an empty LifecyclePolicies array in the request body deletes any existing LifecycleConfiguration for the file system. In the request, specify the following: The ID for the file system for which you are enabling, disabling, or modifying Lifecycle management. A LifecyclePolicies array of LifecyclePolicy objects that define when to move files to IA storage, to Archive storage, and back to primary storage. Amazon EFS requires that each LifecyclePolicy object have only have a single transition, so the LifecyclePolicies array needs to be structured with separate LifecyclePolicy objects. See the example requests in the following section for more information. This operation requires permissions for the elasticfilesystem:PutLifecycleConfiguration operation. To apply a LifecycleConfiguration object to an encrypted file system, you need the same Key Management Service permissions as when you created the encrypted file system.
223
+ * Use this action to manage storage for your file system. A LifecycleConfiguration consists of one or more LifecyclePolicy objects that define the following: TransitionToIA – When to move files in the file system from primary storage (Standard storage class) into the Infrequent Access (IA) storage. TransitionToArchive – When to move files in the file system from their current storage class (either IA or Standard storage) into the Archive storage. File systems cannot transition into Archive storage before transitioning into IA storage. Therefore, TransitionToArchive must either not be set or must be later than TransitionToIA. The Archive storage class is available only for file systems that use the Elastic Throughput mode and the General Purpose Performance mode. TransitionToPrimaryStorageClass – Whether to move files in the file system back to primary storage (Standard storage class) after they are accessed in IA or Archive storage. For more information, see Managing file system storage. Each Amazon EFS file system supports one lifecycle configuration, which applies to all files in the file system. If a LifecycleConfiguration object already exists for the specified file system, a PutLifecycleConfiguration call modifies the existing configuration. A PutLifecycleConfiguration call with an empty LifecyclePolicies array in the request body deletes any existing LifecycleConfiguration. In the request, specify the following: The ID for the file system for which you are enabling, disabling, or modifying Lifecycle management. A LifecyclePolicies array of LifecyclePolicy objects that define when to move files to IA storage, to Archive storage, and back to primary storage. Amazon EFS requires that each LifecyclePolicy object have only have a single transition, so the LifecyclePolicies array needs to be structured with separate LifecyclePolicy objects. See the example requests in the following section for more information. This operation requires permissions for the elasticfilesystem:PutLifecycleConfiguration operation. To apply a LifecycleConfiguration object to an encrypted file system, you need the same Key Management Service permissions as when you created the encrypted file system.
224
224
  */
225
225
  putLifecycleConfiguration(params: EFS.Types.PutLifecycleConfigurationRequest, callback?: (err: AWSError, data: EFS.Types.LifecycleConfigurationDescription) => void): Request<EFS.Types.LifecycleConfigurationDescription, AWSError>;
226
226
  /**
227
- * Use this action to manage storage of your file system. A LifecycleConfiguration consists of one or more LifecyclePolicy objects that define the following: TransitionToIA – When to move files in the file system from primary storage (Standard storage class) into the Infrequent Access (IA) storage. TransitionToArchive – When to move files in the file system from their current storage class (either IA or Standard storage) into the Archive storage. File systems cannot transition into Archive storage before transitioning into IA storage. Therefore, TransitionToArchive must either not be set or must be later than TransitionToIA. The Archive storage class is available only for file systems that use the Elastic Throughput mode and the General Purpose Performance mode. TransitionToPrimaryStorageClass – Whether to move files in the file system back to primary storage (Standard storage class) after they are accessed in IA or Archive storage. For more information, see Managing file system storage. Each Amazon EFS file system supports one lifecycle configuration, which applies to all files in the file system. If a LifecycleConfiguration object already exists for the specified file system, a PutLifecycleConfiguration call modifies the existing configuration. A PutLifecycleConfiguration call with an empty LifecyclePolicies array in the request body deletes any existing LifecycleConfiguration for the file system. In the request, specify the following: The ID for the file system for which you are enabling, disabling, or modifying Lifecycle management. A LifecyclePolicies array of LifecyclePolicy objects that define when to move files to IA storage, to Archive storage, and back to primary storage. Amazon EFS requires that each LifecyclePolicy object have only have a single transition, so the LifecyclePolicies array needs to be structured with separate LifecyclePolicy objects. See the example requests in the following section for more information. This operation requires permissions for the elasticfilesystem:PutLifecycleConfiguration operation. To apply a LifecycleConfiguration object to an encrypted file system, you need the same Key Management Service permissions as when you created the encrypted file system.
227
+ * Use this action to manage storage for your file system. A LifecycleConfiguration consists of one or more LifecyclePolicy objects that define the following: TransitionToIA – When to move files in the file system from primary storage (Standard storage class) into the Infrequent Access (IA) storage. TransitionToArchive – When to move files in the file system from their current storage class (either IA or Standard storage) into the Archive storage. File systems cannot transition into Archive storage before transitioning into IA storage. Therefore, TransitionToArchive must either not be set or must be later than TransitionToIA. The Archive storage class is available only for file systems that use the Elastic Throughput mode and the General Purpose Performance mode. TransitionToPrimaryStorageClass – Whether to move files in the file system back to primary storage (Standard storage class) after they are accessed in IA or Archive storage. For more information, see Managing file system storage. Each Amazon EFS file system supports one lifecycle configuration, which applies to all files in the file system. If a LifecycleConfiguration object already exists for the specified file system, a PutLifecycleConfiguration call modifies the existing configuration. A PutLifecycleConfiguration call with an empty LifecyclePolicies array in the request body deletes any existing LifecycleConfiguration. In the request, specify the following: The ID for the file system for which you are enabling, disabling, or modifying Lifecycle management. A LifecyclePolicies array of LifecyclePolicy objects that define when to move files to IA storage, to Archive storage, and back to primary storage. Amazon EFS requires that each LifecyclePolicy object have only have a single transition, so the LifecyclePolicies array needs to be structured with separate LifecyclePolicy objects. See the example requests in the following section for more information. This operation requires permissions for the elasticfilesystem:PutLifecycleConfiguration operation. To apply a LifecycleConfiguration object to an encrypted file system, you need the same Key Management Service permissions as when you created the encrypted file system.
228
228
  */
229
229
  putLifecycleConfiguration(callback?: (err: AWSError, data: EFS.Types.LifecycleConfigurationDescription) => void): Request<EFS.Types.LifecycleConfigurationDescription, AWSError>;
230
230
  /**
@@ -251,6 +251,14 @@ declare class EFS extends Service {
251
251
  * Updates the throughput mode or the amount of provisioned throughput of an existing file system.
252
252
  */
253
253
  updateFileSystem(callback?: (err: AWSError, data: EFS.Types.FileSystemDescription) => void): Request<EFS.Types.FileSystemDescription, AWSError>;
254
+ /**
255
+ * Updates protection on the file system. This operation requires permissions for the elasticfilesystem:UpdateFileSystemProtection action.
256
+ */
257
+ updateFileSystemProtection(params: EFS.Types.UpdateFileSystemProtectionRequest, callback?: (err: AWSError, data: EFS.Types.FileSystemProtectionDescription) => void): Request<EFS.Types.FileSystemProtectionDescription, AWSError>;
258
+ /**
259
+ * Updates protection on the file system. This operation requires permissions for the elasticfilesystem:UpdateFileSystemProtection action.
260
+ */
261
+ updateFileSystemProtection(callback?: (err: AWSError, data: EFS.Types.FileSystemProtectionDescription) => void): Request<EFS.Types.FileSystemProtectionDescription, AWSError>;
254
262
  }
255
263
  declare namespace EFS {
256
264
  export type AccessPointArn = string;
@@ -695,9 +703,13 @@ declare namespace EFS {
695
703
  */
696
704
  AvailabilityZoneName?: AvailabilityZoneName;
697
705
  /**
698
- * Specifies the Key Management Service (KMS) key that you want to use to encrypt the destination file system. If you do not specify a KMS key, Amazon EFS uses your default KMS key for Amazon EFS, /aws/elasticfilesystem. This ID can be in one of the following formats: Key ID - The unique identifier of the key, for example 1234abcd-12ab-34cd-56ef-1234567890ab. ARN - The Amazon Resource Name (ARN) for the key, for example arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab. Key alias - A previously created display name for a key, for example alias/projectKey1. Key alias ARN - The ARN for a key alias, for example arn:aws:kms:us-west-2:444455556666:alias/projectKey1.
706
+ * Specify the Key Management Service (KMS) key that you want to use to encrypt the destination file system. If you do not specify a KMS key, Amazon EFS uses your default KMS key for Amazon EFS, /aws/elasticfilesystem. This ID can be in one of the following formats: Key ID - The unique identifier of the key, for example 1234abcd-12ab-34cd-56ef-1234567890ab. ARN - The Amazon Resource Name (ARN) for the key, for example arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab. Key alias - A previously created display name for a key, for example alias/projectKey1. Key alias ARN - The ARN for a key alias, for example arn:aws:kms:us-west-2:444455556666:alias/projectKey1.
699
707
  */
700
708
  KmsKeyId?: KmsKeyId;
709
+ /**
710
+ * The ID of the file system to use for the destination. The file system's replication overwrite replication must be disabled. If you do not provide an ID, then EFS creates a new file system for the replication destination.
711
+ */
712
+ FileSystemId?: FileSystemId;
701
713
  }
702
714
  export type Destinations = Destination[];
703
715
  export type DestinationsToCreate = DestinationToCreate[];
@@ -772,6 +784,10 @@ declare namespace EFS {
772
784
  * The tags associated with the file system, presented as an array of Tag objects.
773
785
  */
774
786
  Tags: Tags;
787
+ /**
788
+ * Describes the protection on the file system.
789
+ */
790
+ FileSystemProtection?: FileSystemProtectionDescription;
775
791
  }
776
792
  export type FileSystemDescriptions = FileSystemDescription[];
777
793
  export type FileSystemId = string;
@@ -786,6 +802,12 @@ declare namespace EFS {
786
802
  */
787
803
  Policy?: Policy;
788
804
  }
805
+ export interface FileSystemProtectionDescription {
806
+ /**
807
+ * The status of the file system's replication overwrite protection. ENABLED – The file system cannot be used as the destination file system in a replication configuration. The file system is writeable. Replication overwrite protection is ENABLED by default. DISABLED – The file system can be used as the destination file system in a replication configuration. The file system is read-only and can only be modified by EFS replication. REPLICATING – The file system is being used as the destination file system in a replication configuration. The file system is read-only and is only modified only by EFS replication. If the replication configuration is deleted, the file system's replication overwrite protection is re-enabled, the file system becomes writeable.
808
+ */
809
+ ReplicationOverwriteProtection?: ReplicationOverwriteProtection;
810
+ }
789
811
  export interface FileSystemSize {
790
812
  /**
791
813
  * The latest known metered size (in bytes) of data stored in the file system.
@@ -1010,6 +1032,7 @@ declare namespace EFS {
1010
1032
  Destinations: Destinations;
1011
1033
  }
1012
1034
  export type ReplicationConfigurationDescriptions = ReplicationConfigurationDescription[];
1035
+ export type ReplicationOverwriteProtection = "ENABLED"|"DISABLED"|"REPLICATING"|string;
1013
1036
  export type ReplicationStatus = "ENABLED"|"ENABLING"|"DELETING"|"ERROR"|"PAUSED"|"PAUSING"|string;
1014
1037
  export type Resource = "FILE_SYSTEM"|"MOUNT_TARGET"|string;
1015
1038
  export type ResourceId = string;
@@ -1081,6 +1104,16 @@ declare namespace EFS {
1081
1104
  */
1082
1105
  TagKeys: TagKeys;
1083
1106
  }
1107
+ export interface UpdateFileSystemProtectionRequest {
1108
+ /**
1109
+ * The ID of the file system to update.
1110
+ */
1111
+ FileSystemId: FileSystemId;
1112
+ /**
1113
+ * The status of the file system's replication overwrite protection. ENABLED – The file system cannot be used as the destination file system in a replication configuration. The file system is writeable. Replication overwrite protection is ENABLED by default. DISABLED – The file system can be used as the destination file system in a replication configuration. The file system is read-only and can only be modified by EFS replication. REPLICATING – The file system is being used as the destination file system in a replication configuration. The file system is read-only and is only modified only by EFS replication. If the replication configuration is deleted, the file system's replication overwrite protection is re-enabled, the file system becomes writeable.
1114
+ */
1115
+ ReplicationOverwriteProtection?: ReplicationOverwriteProtection;
1116
+ }
1084
1117
  export interface UpdateFileSystemRequest {
1085
1118
  /**
1086
1119
  * The ID of the file system that you want to update.