aws-sdk 2.1578.0 → 2.1580.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.
@@ -460,6 +460,14 @@ declare class CloudFormation extends Service {
460
460
  * Returns descriptions of all resources of the specified stack. For deleted stacks, ListStackResources returns resource information for up to 90 days after the stack has been deleted.
461
461
  */
462
462
  listStackResources(callback?: (err: AWSError, data: CloudFormation.Types.ListStackResourcesOutput) => void): Request<CloudFormation.Types.ListStackResourcesOutput, AWSError>;
463
+ /**
464
+ * Returns summary information about deployment targets for a stack set.
465
+ */
466
+ listStackSetAutoDeploymentTargets(params: CloudFormation.Types.ListStackSetAutoDeploymentTargetsInput, callback?: (err: AWSError, data: CloudFormation.Types.ListStackSetAutoDeploymentTargetsOutput) => void): Request<CloudFormation.Types.ListStackSetAutoDeploymentTargetsOutput, AWSError>;
467
+ /**
468
+ * Returns summary information about deployment targets for a stack set.
469
+ */
470
+ listStackSetAutoDeploymentTargets(callback?: (err: AWSError, data: CloudFormation.Types.ListStackSetAutoDeploymentTargetsOutput) => void): Request<CloudFormation.Types.ListStackSetAutoDeploymentTargetsOutput, AWSError>;
463
471
  /**
464
472
  * Returns summary information about the results of a stack set operation.
465
473
  */
@@ -1176,7 +1184,7 @@ declare namespace CloudFormation {
1176
1184
  */
1177
1185
  NotificationARNs?: NotificationARNs;
1178
1186
  /**
1179
- * In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack. CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities. The following IAM resources require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have IAM resources, you can specify either capability. If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities error. If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary. AWS::IAM::AccessKey AWS::IAM::AccessKey AWS::IAM::Group AWS::IAM::InstanceProfile AWS::IAM::Policy AWS::IAM::Role AWS::IAM::User AWS::IAM::UserToGroupAddition For more information, see Acknowledging IAM Resources in CloudFormation Templates. CAPABILITY_AUTO_EXPAND Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation. If you want to create a stack from a stack template that contains macros and nested stacks, you must create the stack directly from the template using this capability. You should only create stacks directly from a stack template that contains macros if you know what processing the macro performs. Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified. For more information, see Using CloudFormation macros to perform custom processing on templates. Only one of the Capabilities and ResourceType parameters can be specified.
1187
+ * In some cases, you must explicitly acknowledge that your stack template contains certain capabilities in order for CloudFormation to create the stack. CAPABILITY_IAM and CAPABILITY_NAMED_IAM Some stack templates might include resources that can affect permissions in your Amazon Web Services account; for example, by creating new Identity and Access Management (IAM) users. For those stacks, you must explicitly acknowledge this by specifying one of these capabilities. The following IAM resources require you to specify either the CAPABILITY_IAM or CAPABILITY_NAMED_IAM capability. If you have IAM resources, you can specify either capability. If you have IAM resources with custom names, you must specify CAPABILITY_NAMED_IAM. If you don't specify either of these capabilities, CloudFormation returns an InsufficientCapabilities error. If your stack template contains these resources, we recommend that you review all permissions associated with them and edit their permissions if necessary. AWS::IAM::AccessKey AWS::IAM::Group AWS::IAM::InstanceProfile AWS::IAM::Policy AWS::IAM::Role AWS::IAM::User AWS::IAM::UserToGroupAddition For more information, see Acknowledging IAM Resources in CloudFormation Templates. CAPABILITY_AUTO_EXPAND Some template contain macros. Macros perform custom processing on templates; this can include simple actions like find-and-replace operations, all the way to extensive transformations of entire templates. Because of this, users typically create a change set from the processed template, so that they can review the changes resulting from the macros before actually creating the stack. If your stack template contains one or more macros, and you choose to create a stack directly from the processed template, without first reviewing the resulting changes in a change set, you must acknowledge this capability. This includes the AWS::Include and AWS::Serverless transforms, which are macros hosted by CloudFormation. If you want to create a stack from a stack template that contains macros and nested stacks, you must create the stack directly from the template using this capability. You should only create stacks directly from a stack template that contains macros if you know what processing the macro performs. Each macro relies on an underlying Lambda service function for processing stack templates. Be aware that the Lambda function owner can update the function operation without CloudFormation being notified. For more information, see Using CloudFormation macros to perform custom processing on templates. Only one of the Capabilities and ResourceType parameters can be specified.
1180
1188
  */
1181
1189
  Capabilities?: Capabilities;
1182
1190
  /**
@@ -2730,6 +2738,34 @@ declare namespace CloudFormation {
2730
2738
  */
2731
2739
  NextToken?: NextToken;
2732
2740
  }
2741
+ export interface ListStackSetAutoDeploymentTargetsInput {
2742
+ /**
2743
+ * The name or unique ID of the stack set that you want to get automatic deployment targets for.
2744
+ */
2745
+ StackSetName: StackSetNameOrId;
2746
+ /**
2747
+ * A string that identifies the next page of stack set deployment targets that you want to retrieve.
2748
+ */
2749
+ NextToken?: NextToken;
2750
+ /**
2751
+ * The maximum number of results to be returned with a single call. If the number of available results exceeds this maximum, the response includes a NextToken value that you can assign to the NextToken request parameter to get the next set of results.
2752
+ */
2753
+ MaxResults?: MaxResults;
2754
+ /**
2755
+ * Specifies whether you are acting as an account administrator in the organization's management account or as a delegated administrator in a member account. By default, SELF is specified. Use SELF for StackSets with self-managed permissions. If you are signed in to the management account, specify SELF. If you are signed in to a delegated administrator account, specify DELEGATED_ADMIN. Your Amazon Web Services account must be registered as a delegated administrator in the management account. For more information, see Register a delegated administrator in the CloudFormation User Guide.
2756
+ */
2757
+ CallAs?: CallAs;
2758
+ }
2759
+ export interface ListStackSetAutoDeploymentTargetsOutput {
2760
+ /**
2761
+ * An array of summaries of the deployment targets for the stack set.
2762
+ */
2763
+ Summaries?: StackSetAutoDeploymentTargetSummaries;
2764
+ /**
2765
+ * If the request doesn't return all the remaining results, NextToken is set to a token. To retrieve the next set of results, call ListStackSetAutoDeploymentTargets again and use that value for the NextToken parameter. If the request returns all results, NextToken is set to an empty string.
2766
+ */
2767
+ NextToken?: NextToken;
2768
+ }
2733
2769
  export interface ListStackSetOperationResultsInput {
2734
2770
  /**
2735
2771
  * The name or unique ID of the stack set that you want to get operation results for.
@@ -3885,7 +3921,7 @@ declare namespace CloudFormation {
3885
3921
  }
3886
3922
  export interface StackInstanceComprehensiveStatus {
3887
3923
  /**
3888
- * CANCELLED: The operation in the specified account and Region has been canceled. This is either because a user has stopped the stack set operation, or because the failure tolerance of the stack set operation has been exceeded. FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded. INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually. PENDING: The operation in the specified account and Region has yet to start. RUNNING: The operation in the specified account and Region is currently in progress. SKIPPED_SUSPENDED_ACCOUNT: The operation in the specified account and Region has been skipped because the account was suspended at the time of the operation. SUCCEEDED: The operation in the specified account and Region completed successfully.
3924
+ * CANCELLED: The operation in the specified account and Region has been canceled. This is either because a user has stopped the stack set operation, or because the failure tolerance of the stack set operation has been exceeded. FAILED: The operation in the specified account and Region failed. If the stack set operation fails in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded. FAILED_IMPORT: The import of the stack instance in the specified account and Region failed and left the stack in an unstable state. Once the issues causing the failure are fixed, the import operation can be retried. If enough stack set operations fail in enough accounts within a Region, the failure tolerance for the stack set operation as a whole might be exceeded. INOPERABLE: A DeleteStackInstances operation has failed and left the stack in an unstable state. Stacks in this state are excluded from further UpdateStackSet operations. You might need to perform a DeleteStackInstances operation, with RetainStacks set to true, to delete the stack instance, and then delete the stack manually. PENDING: The operation in the specified account and Region has yet to start. RUNNING: The operation in the specified account and Region is currently in progress. SKIPPED_SUSPENDED_ACCOUNT: The operation in the specified account and Region has been skipped because the account was suspended at the time of the operation. SUCCEEDED: The operation in the specified account and Region completed successfully.
3889
3925
  */
3890
3926
  DetailedStatus?: StackInstanceDetailedStatus;
3891
3927
  }
@@ -4264,6 +4300,17 @@ declare namespace CloudFormation {
4264
4300
  Regions?: RegionList;
4265
4301
  }
4266
4302
  export type StackSetARN = string;
4303
+ export type StackSetAutoDeploymentTargetSummaries = StackSetAutoDeploymentTargetSummary[];
4304
+ export interface StackSetAutoDeploymentTargetSummary {
4305
+ /**
4306
+ * The organization root ID or organizational unit (OU) IDs where the stack set is targeted.
4307
+ */
4308
+ OrganizationalUnitId?: OrganizationalUnitId;
4309
+ /**
4310
+ * The list of Regions targeted for this organization or OU.
4311
+ */
4312
+ Regions?: RegionList;
4313
+ }
4267
4314
  export interface StackSetDriftDetectionDetails {
4268
4315
  /**
4269
4316
  * Status of the stack set's actual configuration compared to its expected template and parameter configuration. A stack set is considered to have drifted if one or more of its stack instances have drifted from their expected template and parameter configuration. DRIFTED: One or more of the stack instances belonging to the stack set stack differs from the expected template and parameter configuration. A stack instance is considered to have drifted if one or more of the resources in the associated stack have drifted. NOT_CHECKED: CloudFormation hasn't checked the stack set for drift. IN_SYNC: All of the stack instances belonging to the stack set stack match from the expected template and parameter configuration.
@@ -1046,6 +1046,10 @@ declare namespace CodeBuild {
1046
1046
  * The scaling configuration of the compute fleet.
1047
1047
  */
1048
1048
  scalingConfiguration?: ScalingConfigurationInput;
1049
+ /**
1050
+ * The compute fleet overflow behavior. For overflow behavior QUEUE, your overflow builds need to wait on the existing fleet instance to become available. For overflow behavior ON_DEMAND, your overflow builds run on CodeBuild on-demand.
1051
+ */
1052
+ overflowBehavior?: FleetOverflowBehavior;
1049
1053
  /**
1050
1054
  * A list of tag key and value pairs associated with this compute fleet. These tags are available for use by Amazon Web Services services that support CodeBuild build project tags.
1051
1055
  */
@@ -1469,6 +1473,10 @@ declare namespace CodeBuild {
1469
1473
  * The scaling configuration of the compute fleet.
1470
1474
  */
1471
1475
  scalingConfiguration?: ScalingConfigurationOutput;
1476
+ /**
1477
+ * The compute fleet overflow behavior. For overflow behavior QUEUE, your overflow builds need to wait on the existing fleet instance to become available. For overflow behavior ON_DEMAND, your overflow builds run on CodeBuild on-demand.
1478
+ */
1479
+ overflowBehavior?: FleetOverflowBehavior;
1472
1480
  /**
1473
1481
  * A list of tag key and value pairs associated with this compute fleet. These tags are available for use by Amazon Web Services services that support CodeBuild build project tags.
1474
1482
  */
@@ -1479,6 +1487,7 @@ declare namespace CodeBuild {
1479
1487
  export type FleetContextCode = "CREATE_FAILED"|"UPDATE_FAILED"|string;
1480
1488
  export type FleetName = string;
1481
1489
  export type FleetNames = NonEmptyString[];
1490
+ export type FleetOverflowBehavior = "QUEUE"|"ON_DEMAND"|string;
1482
1491
  export type FleetScalingMetricType = "FLEET_UTILIZATION_RATE"|string;
1483
1492
  export type FleetScalingType = "TARGET_TRACKING_SCALING"|string;
1484
1493
  export type FleetSortByType = "NAME"|"CREATED_TIME"|"LAST_MODIFIED_TIME"|string;
@@ -3008,6 +3017,10 @@ declare namespace CodeBuild {
3008
3017
  * The scaling configuration of the compute fleet.
3009
3018
  */
3010
3019
  scalingConfiguration?: ScalingConfigurationInput;
3020
+ /**
3021
+ * The compute fleet overflow behavior. For overflow behavior QUEUE, your overflow builds need to wait on the existing fleet instance to become available. For overflow behavior ON_DEMAND, your overflow builds run on CodeBuild on-demand.
3022
+ */
3023
+ overflowBehavior?: FleetOverflowBehavior;
3011
3024
  /**
3012
3025
  * A list of tag key and value pairs associated with this compute fleet. These tags are available for use by Amazon Web Services services that support CodeBuild build project tags.
3013
3026
  */
@@ -2477,7 +2477,15 @@ declare namespace Connect {
2477
2477
  */
2478
2478
  Value?: InstanceAttributeValue;
2479
2479
  }
2480
+ export interface AttributeAndCondition {
2481
+ /**
2482
+ * A leaf node condition which can be used to specify a tag condition.
2483
+ */
2484
+ TagConditions?: TagAndConditionList;
2485
+ HierarchyGroupCondition?: HierarchyGroupCondition;
2486
+ }
2480
2487
  export type AttributeName = string;
2488
+ export type AttributeOrConditionList = AttributeAndCondition[];
2481
2489
  export type AttributeValue = string;
2482
2490
  export type Attributes = {[key: string]: AttributeValue};
2483
2491
  export type AttributesList = Attribute[];
@@ -3097,6 +3105,18 @@ declare namespace Connect {
3097
3105
  */
3098
3106
  TagCondition?: TagCondition;
3099
3107
  }
3108
+ export interface ControlPlaneUserAttributeFilter {
3109
+ /**
3110
+ * A list of conditions which would be applied together with an OR condition.
3111
+ */
3112
+ OrConditions?: AttributeOrConditionList;
3113
+ /**
3114
+ * A list of conditions which would be applied together with an AND condition.
3115
+ */
3116
+ AndCondition?: AttributeAndCondition;
3117
+ TagCondition?: TagCondition;
3118
+ HierarchyGroupCondition?: HierarchyGroupCondition;
3119
+ }
3100
3120
  export interface CreateAgentStatusRequest {
3101
3121
  /**
3102
3122
  * The identifier of the Amazon Connect instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.
@@ -3663,6 +3683,14 @@ declare namespace Connect {
3663
3683
  * This API is in preview release for Amazon Connect and is subject to change. A list of third-party applications that the security profile will give access to.
3664
3684
  */
3665
3685
  Applications?: Applications;
3686
+ /**
3687
+ * The list of resources that a security profile applies hierarchy restrictions to in Amazon Connect. Following are acceptable ResourceNames: User.
3688
+ */
3689
+ HierarchyRestrictedResources?: HierarchyRestrictedResourceList;
3690
+ /**
3691
+ * The identifier of the hierarchy group that a security profile uses to restrict access to resources in Amazon Connect.
3692
+ */
3693
+ AllowedAccessControlHierarchyGroupId?: HierarchyGroupId;
3666
3694
  }
3667
3695
  export interface CreateSecurityProfileResponse {
3668
3696
  /**
@@ -6139,6 +6167,8 @@ declare namespace Connect {
6139
6167
  */
6140
6168
  LevelFive?: HierarchyGroupSummaryReference;
6141
6169
  }
6170
+ export type HierarchyRestrictedResourceList = HierarchyRestrictedResourceName[];
6171
+ export type HierarchyRestrictedResourceName = string;
6142
6172
  export interface HierarchyStructure {
6143
6173
  /**
6144
6174
  * Information about level one.
@@ -9888,6 +9918,14 @@ declare namespace Connect {
9888
9918
  * The Amazon Web Services Region where this resource was last modified.
9889
9919
  */
9890
9920
  LastModifiedRegion?: RegionName;
9921
+ /**
9922
+ * The list of resources that a security profile applies hierarchy restrictions to in Amazon Connect. Following are acceptable ResourceNames: User.
9923
+ */
9924
+ HierarchyRestrictedResources?: HierarchyRestrictedResourceList;
9925
+ /**
9926
+ * The identifier of the hierarchy group that a security profile uses to restrict access to resources in Amazon Connect.
9927
+ */
9928
+ AllowedAccessControlHierarchyGroupId?: HierarchyGroupId;
9891
9929
  }
9892
9930
  export type SecurityProfileDescription = string;
9893
9931
  export type SecurityProfileId = string;
@@ -11604,6 +11642,14 @@ declare namespace Connect {
11604
11642
  * This API is in preview release for Amazon Connect and is subject to change. A list of the third-party application's metadata.
11605
11643
  */
11606
11644
  Applications?: Applications;
11645
+ /**
11646
+ * The list of resources that a security profile applies hierarchy restrictions to in Amazon Connect. Following are acceptable ResourceNames: User.
11647
+ */
11648
+ HierarchyRestrictedResources?: HierarchyRestrictedResourceList;
11649
+ /**
11650
+ * The identifier of the hierarchy group that a security profile uses to restrict access to resources in Amazon Connect.
11651
+ */
11652
+ AllowedAccessControlHierarchyGroupId?: HierarchyGroupId;
11607
11653
  }
11608
11654
  export interface UpdateTaskTemplateRequest {
11609
11655
  /**
@@ -12124,6 +12170,10 @@ declare namespace Connect {
12124
12170
  }
12125
12171
  export interface UserSearchFilter {
12126
12172
  TagFilter?: ControlPlaneTagFilter;
12173
+ /**
12174
+ * An object that can be used to specify Tag conditions or Hierarchy Group conditions inside the SearchFilter. This accepts an OR of AND (List of List) input where: The top level list specifies conditions that need to be applied with OR operator. The inner list specifies conditions that need to be applied with AND operator. Only one field can be populated. This object can’t be used along with TagFilter. Request can either contain TagFilter or UserAttributeFilter if SearchFilter is specified, combination of both is not supported and such request will throw AccessDeniedException.
12175
+ */
12176
+ UserAttributeFilter?: ControlPlaneUserAttributeFilter;
12127
12177
  }
12128
12178
  export interface UserSearchSummary {
12129
12179
  /**
package/clients/ec2.d.ts CHANGED
@@ -25247,6 +25247,14 @@ declare namespace EC2 {
25247
25247
  * Describes the supported NitroTPM versions for the instance type.
25248
25248
  */
25249
25249
  NitroTpmInfo?: NitroTpmInfo;
25250
+ /**
25251
+ * Describes the media accelerator settings for the instance type.
25252
+ */
25253
+ MediaAcceleratorInfo?: MediaAcceleratorInfo;
25254
+ /**
25255
+ * Describes the Neuron accelerator settings for the instance type.
25256
+ */
25257
+ NeuronInfo?: NeuronInfo;
25250
25258
  }
25251
25259
  export interface InstanceTypeInfoFromInstanceRequirements {
25252
25260
  /**
@@ -27778,6 +27786,45 @@ declare namespace EC2 {
27778
27786
  export type MaximumIops = number;
27779
27787
  export type MaximumNetworkCards = number;
27780
27788
  export type MaximumThroughputInMBps = number;
27789
+ export interface MediaAcceleratorInfo {
27790
+ /**
27791
+ * Describes the media accelerators for the instance type.
27792
+ */
27793
+ Accelerators?: MediaDeviceInfoList;
27794
+ /**
27795
+ * The total size of the memory for the media accelerators for the instance type, in MiB.
27796
+ */
27797
+ TotalMediaMemoryInMiB?: TotalMediaMemory;
27798
+ }
27799
+ export type MediaDeviceCount = number;
27800
+ export interface MediaDeviceInfo {
27801
+ /**
27802
+ * The number of media accelerators for the instance type.
27803
+ */
27804
+ Count?: MediaDeviceCount;
27805
+ /**
27806
+ * The name of the media accelerator.
27807
+ */
27808
+ Name?: MediaDeviceName;
27809
+ /**
27810
+ * The manufacturer of the media accelerator.
27811
+ */
27812
+ Manufacturer?: MediaDeviceManufacturerName;
27813
+ /**
27814
+ * Describes the memory available to the media accelerator.
27815
+ */
27816
+ MemoryInfo?: MediaDeviceMemoryInfo;
27817
+ }
27818
+ export type MediaDeviceInfoList = MediaDeviceInfo[];
27819
+ export type MediaDeviceManufacturerName = string;
27820
+ export interface MediaDeviceMemoryInfo {
27821
+ /**
27822
+ * The size of the memory available to each media accelerator, in MiB.
27823
+ */
27824
+ SizeInMiB?: MediaDeviceMemorySize;
27825
+ }
27826
+ export type MediaDeviceMemorySize = number;
27827
+ export type MediaDeviceName = string;
27781
27828
  export type MembershipType = "static"|"igmp"|string;
27782
27829
  export interface MemoryGiBPerVCpu {
27783
27830
  /**
@@ -30924,6 +30971,56 @@ declare namespace EC2 {
30924
30971
  export type NetworkInterfaceType = "interface"|"natGateway"|"efa"|"trunk"|"load_balancer"|"network_load_balancer"|"vpc_endpoint"|"branch"|"transit_gateway"|"lambda"|"quicksight"|"global_accelerator_managed"|"api_gateway_managed"|"gateway_load_balancer"|"gateway_load_balancer_endpoint"|"iot_rules_managed"|"aws_codestar_connections_managed"|string;
30925
30972
  export type NetworkNodesList = String[];
30926
30973
  export type NetworkPerformance = string;
30974
+ export type NeuronDeviceCoreCount = number;
30975
+ export interface NeuronDeviceCoreInfo {
30976
+ /**
30977
+ * The number of cores available to the neuron accelerator.
30978
+ */
30979
+ Count?: NeuronDeviceCoreCount;
30980
+ /**
30981
+ * The version of the neuron accelerator.
30982
+ */
30983
+ Version?: NeuronDeviceCoreVersion;
30984
+ }
30985
+ export type NeuronDeviceCoreVersion = number;
30986
+ export type NeuronDeviceCount = number;
30987
+ export interface NeuronDeviceInfo {
30988
+ /**
30989
+ * The number of neuron accelerators for the instance type.
30990
+ */
30991
+ Count?: NeuronDeviceCount;
30992
+ /**
30993
+ * The name of the neuron accelerator.
30994
+ */
30995
+ Name?: NeuronDeviceName;
30996
+ /**
30997
+ * Describes the cores available to each neuron accelerator.
30998
+ */
30999
+ CoreInfo?: NeuronDeviceCoreInfo;
31000
+ /**
31001
+ * Describes the memory available to each neuron accelerator.
31002
+ */
31003
+ MemoryInfo?: NeuronDeviceMemoryInfo;
31004
+ }
31005
+ export type NeuronDeviceInfoList = NeuronDeviceInfo[];
31006
+ export interface NeuronDeviceMemoryInfo {
31007
+ /**
31008
+ * The size of the memory available to the neuron accelerator, in MiB.
31009
+ */
31010
+ SizeInMiB?: NeuronDeviceMemorySize;
31011
+ }
31012
+ export type NeuronDeviceMemorySize = number;
31013
+ export type NeuronDeviceName = string;
31014
+ export interface NeuronInfo {
31015
+ /**
31016
+ * Describes the neuron accelerators for the instance type.
31017
+ */
31018
+ NeuronDevices?: NeuronDeviceInfoList;
31019
+ /**
31020
+ * The total size of the memory for the neuron accelerators for the instance type, in MiB.
31021
+ */
31022
+ TotalNeuronDeviceMemoryInMiB?: TotalNeuronMemory;
31023
+ }
30927
31024
  export interface NewDhcpConfiguration {
30928
31025
  Key?: String;
30929
31026
  Values?: ValueStringList;
@@ -35768,7 +35865,7 @@ declare namespace EC2 {
35768
35865
  */
35769
35866
  IamFleetRole: String;
35770
35867
  /**
35771
- * The launch specifications for the Spot Fleet request. If you specify LaunchSpecifications, you can't specify LaunchTemplateConfigs. If you include On-Demand capacity in your request, you must use LaunchTemplateConfigs.
35868
+ * The launch specifications for the Spot Fleet request. If you specify LaunchSpecifications, you can't specify LaunchTemplateConfigs. If you include On-Demand capacity in your request, you must use LaunchTemplateConfigs. If an AMI specified in a launch specification is deregistered or disabled, no new instances can be launched from the AMI. For fleets of type maintain, the target capacity will not be maintained.
35772
35869
  */
35773
35870
  LaunchSpecifications?: LaunchSpecsList;
35774
35871
  /**
@@ -36829,6 +36926,8 @@ declare namespace EC2 {
36829
36926
  */
36830
36927
  Max?: Double;
36831
36928
  }
36929
+ export type TotalMediaMemory = number;
36930
+ export type TotalNeuronMemory = number;
36832
36931
  export type TpmSupportValues = "v2.0"|string;
36833
36932
  export type TrafficDirection = "ingress"|"egress"|string;
36834
36933
  export interface TrafficMirrorFilter {
@@ -2097,7 +2097,7 @@ declare namespace KinesisAnalyticsV2 {
2097
2097
  */
2098
2098
  ApplicationRestoreConfiguration?: ApplicationRestoreConfiguration;
2099
2099
  }
2100
- export type RuntimeEnvironment = "SQL-1_0"|"FLINK-1_6"|"FLINK-1_8"|"ZEPPELIN-FLINK-1_0"|"FLINK-1_11"|"FLINK-1_13"|"ZEPPELIN-FLINK-2_0"|"FLINK-1_15"|"ZEPPELIN-FLINK-3_0"|string;
2100
+ export type RuntimeEnvironment = "SQL-1_0"|"FLINK-1_6"|"FLINK-1_8"|"ZEPPELIN-FLINK-1_0"|"FLINK-1_11"|"FLINK-1_13"|"ZEPPELIN-FLINK-2_0"|"FLINK-1_15"|"ZEPPELIN-FLINK-3_0"|"FLINK-1_18"|string;
2101
2101
  export interface S3ApplicationCodeLocationDescription {
2102
2102
  /**
2103
2103
  * The Amazon Resource Name (ARN) for the S3 bucket containing the application code.
package/clients/kms.d.ts CHANGED
@@ -236,11 +236,11 @@ declare class KMS extends Service {
236
236
  */
237
237
  getPublicKey(callback?: (err: AWSError, data: KMS.Types.GetPublicKeyResponse) => void): Request<KMS.Types.GetPublicKeyResponse, AWSError>;
238
238
  /**
239
- * Imports or reimports key material into an existing KMS key that was created without key material. ImportKeyMaterial also sets the expiration model and expiration date of the imported key material. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. After you successfully import key material into a KMS key, you can reimport the same key material into that KMS key, but you cannot import different key material. You might reimport key material to replace key material that expired or key material that you deleted. You might also reimport key material to change the expiration model or expiration date of the key material. Before reimporting key material, if necessary, call DeleteImportedKeyMaterial to delete the current imported key material. Each time you import key material into KMS, you can determine whether (ExpirationModel) and when (ValidTo) the key material expires. To change the expiration of your key material, you must import it again, either by calling ImportKeyMaterial or using the import features of the KMS console. Before calling ImportKeyMaterial: Create or identify a KMS key with no key material. The KMS key must have an Origin value of EXTERNAL, which indicates that the KMS key is designed for imported key material. To create an new KMS key for imported key material, call the CreateKey operation with an Origin value of EXTERNAL. You can create a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. Use the DescribeKey operation to verify that the KeyState of the KMS key is PendingImport, which indicates that the KMS key has no key material. If you are reimporting the same key material into an existing KMS key, you might need to call the DeleteImportedKeyMaterial to delete its existing key material. Call the GetParametersForImport operation to get a public key and import token set for importing key material. Use the public key in the GetParametersForImport response to encrypt your key material. Then, in an ImportKeyMaterial request, you submit your encrypted key material and import token. When calling this operation, you must specify the following values: The key ID or key ARN of the KMS key to associate with the imported key material. Its Origin must be EXTERNAL and its KeyState must be PendingImport. You cannot perform this operation on a KMS key in a custom key store, or on a KMS key in a different Amazon Web Services account. To get the Origin and KeyState of a KMS key, call DescribeKey. The encrypted key material. The import token that GetParametersForImport returned. You must use a public key and token from the same GetParametersForImport response. Whether the key material expires (ExpirationModel) and, if so, when (ValidTo). For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide. If you set an expiration date, KMS deletes the key material from the KMS key on the specified date, making the KMS key unusable. To use the KMS key in cryptographic operations again, you must reimport the same key material. However, you can delete and reimport the key material at any time, including before the key material expires. Each time you reimport, you can eliminate or reset the expiration time. When this operation is successful, the key state of the KMS key changes from PendingImport to Enabled, and you can use the KMS key in cryptographic operations. If this operation fails, use the exception to help determine the problem. If the error is related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key and repeat the import procedure. For help, see How To Import Key Material in the Key Management Service Developer Guide. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:ImportKeyMaterial (key policy) Related operations: DeleteImportedKeyMaterial GetParametersForImport Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
239
+ * Imports or reimports key material into an existing KMS key that was created without key material. ImportKeyMaterial also sets the expiration model and expiration date of the imported key material. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. After you successfully import key material into a KMS key, you can reimport the same key material into that KMS key, but you cannot import different key material. You might reimport key material to replace key material that expired or key material that you deleted. You might also reimport key material to change the expiration model or expiration date of the key material. Each time you import key material into KMS, you can determine whether (ExpirationModel) and when (ValidTo) the key material expires. To change the expiration of your key material, you must import it again, either by calling ImportKeyMaterial or using the import features of the KMS console. Before calling ImportKeyMaterial: Create or identify a KMS key with no key material. The KMS key must have an Origin value of EXTERNAL, which indicates that the KMS key is designed for imported key material. To create an new KMS key for imported key material, call the CreateKey operation with an Origin value of EXTERNAL. You can create a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. Use the DescribeKey operation to verify that the KeyState of the KMS key is PendingImport, which indicates that the KMS key has no key material. If you are reimporting the same key material into an existing KMS key, you might need to call the DeleteImportedKeyMaterial to delete its existing key material. Call the GetParametersForImport operation to get a public key and import token set for importing key material. Use the public key in the GetParametersForImport response to encrypt your key material. Then, in an ImportKeyMaterial request, you submit your encrypted key material and import token. When calling this operation, you must specify the following values: The key ID or key ARN of the KMS key to associate with the imported key material. Its Origin must be EXTERNAL and its KeyState must be PendingImport. You cannot perform this operation on a KMS key in a custom key store, or on a KMS key in a different Amazon Web Services account. To get the Origin and KeyState of a KMS key, call DescribeKey. The encrypted key material. The import token that GetParametersForImport returned. You must use a public key and token from the same GetParametersForImport response. Whether the key material expires (ExpirationModel) and, if so, when (ValidTo). For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide. If you set an expiration date, KMS deletes the key material from the KMS key on the specified date, making the KMS key unusable. To use the KMS key in cryptographic operations again, you must reimport the same key material. However, you can delete and reimport the key material at any time, including before the key material expires. Each time you reimport, you can eliminate or reset the expiration time. When this operation is successful, the key state of the KMS key changes from PendingImport to Enabled, and you can use the KMS key in cryptographic operations. If this operation fails, use the exception to help determine the problem. If the error is related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key and repeat the import procedure. For help, see How To Import Key Material in the Key Management Service Developer Guide. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:ImportKeyMaterial (key policy) Related operations: DeleteImportedKeyMaterial GetParametersForImport Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
240
240
  */
241
241
  importKeyMaterial(params: KMS.Types.ImportKeyMaterialRequest, callback?: (err: AWSError, data: KMS.Types.ImportKeyMaterialResponse) => void): Request<KMS.Types.ImportKeyMaterialResponse, AWSError>;
242
242
  /**
243
- * Imports or reimports key material into an existing KMS key that was created without key material. ImportKeyMaterial also sets the expiration model and expiration date of the imported key material. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. After you successfully import key material into a KMS key, you can reimport the same key material into that KMS key, but you cannot import different key material. You might reimport key material to replace key material that expired or key material that you deleted. You might also reimport key material to change the expiration model or expiration date of the key material. Before reimporting key material, if necessary, call DeleteImportedKeyMaterial to delete the current imported key material. Each time you import key material into KMS, you can determine whether (ExpirationModel) and when (ValidTo) the key material expires. To change the expiration of your key material, you must import it again, either by calling ImportKeyMaterial or using the import features of the KMS console. Before calling ImportKeyMaterial: Create or identify a KMS key with no key material. The KMS key must have an Origin value of EXTERNAL, which indicates that the KMS key is designed for imported key material. To create an new KMS key for imported key material, call the CreateKey operation with an Origin value of EXTERNAL. You can create a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. Use the DescribeKey operation to verify that the KeyState of the KMS key is PendingImport, which indicates that the KMS key has no key material. If you are reimporting the same key material into an existing KMS key, you might need to call the DeleteImportedKeyMaterial to delete its existing key material. Call the GetParametersForImport operation to get a public key and import token set for importing key material. Use the public key in the GetParametersForImport response to encrypt your key material. Then, in an ImportKeyMaterial request, you submit your encrypted key material and import token. When calling this operation, you must specify the following values: The key ID or key ARN of the KMS key to associate with the imported key material. Its Origin must be EXTERNAL and its KeyState must be PendingImport. You cannot perform this operation on a KMS key in a custom key store, or on a KMS key in a different Amazon Web Services account. To get the Origin and KeyState of a KMS key, call DescribeKey. The encrypted key material. The import token that GetParametersForImport returned. You must use a public key and token from the same GetParametersForImport response. Whether the key material expires (ExpirationModel) and, if so, when (ValidTo). For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide. If you set an expiration date, KMS deletes the key material from the KMS key on the specified date, making the KMS key unusable. To use the KMS key in cryptographic operations again, you must reimport the same key material. However, you can delete and reimport the key material at any time, including before the key material expires. Each time you reimport, you can eliminate or reset the expiration time. When this operation is successful, the key state of the KMS key changes from PendingImport to Enabled, and you can use the KMS key in cryptographic operations. If this operation fails, use the exception to help determine the problem. If the error is related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key and repeat the import procedure. For help, see How To Import Key Material in the Key Management Service Developer Guide. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:ImportKeyMaterial (key policy) Related operations: DeleteImportedKeyMaterial GetParametersForImport Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
243
+ * Imports or reimports key material into an existing KMS key that was created without key material. ImportKeyMaterial also sets the expiration model and expiration date of the imported key material. By default, KMS keys are created with key material that KMS generates. This operation supports Importing key material, an advanced feature that lets you generate and import the cryptographic key material for a KMS key. For more information about importing key material into KMS, see Importing key material in the Key Management Service Developer Guide. After you successfully import key material into a KMS key, you can reimport the same key material into that KMS key, but you cannot import different key material. You might reimport key material to replace key material that expired or key material that you deleted. You might also reimport key material to change the expiration model or expiration date of the key material. Each time you import key material into KMS, you can determine whether (ExpirationModel) and when (ValidTo) the key material expires. To change the expiration of your key material, you must import it again, either by calling ImportKeyMaterial or using the import features of the KMS console. Before calling ImportKeyMaterial: Create or identify a KMS key with no key material. The KMS key must have an Origin value of EXTERNAL, which indicates that the KMS key is designed for imported key material. To create an new KMS key for imported key material, call the CreateKey operation with an Origin value of EXTERNAL. You can create a symmetric encryption KMS key, HMAC KMS key, asymmetric encryption KMS key, or asymmetric signing KMS key. You can also import key material into a multi-Region key of any supported type. However, you can't import key material into a KMS key in a custom key store. Use the DescribeKey operation to verify that the KeyState of the KMS key is PendingImport, which indicates that the KMS key has no key material. If you are reimporting the same key material into an existing KMS key, you might need to call the DeleteImportedKeyMaterial to delete its existing key material. Call the GetParametersForImport operation to get a public key and import token set for importing key material. Use the public key in the GetParametersForImport response to encrypt your key material. Then, in an ImportKeyMaterial request, you submit your encrypted key material and import token. When calling this operation, you must specify the following values: The key ID or key ARN of the KMS key to associate with the imported key material. Its Origin must be EXTERNAL and its KeyState must be PendingImport. You cannot perform this operation on a KMS key in a custom key store, or on a KMS key in a different Amazon Web Services account. To get the Origin and KeyState of a KMS key, call DescribeKey. The encrypted key material. The import token that GetParametersForImport returned. You must use a public key and token from the same GetParametersForImport response. Whether the key material expires (ExpirationModel) and, if so, when (ValidTo). For help with this choice, see Setting an expiration time in the Key Management Service Developer Guide. If you set an expiration date, KMS deletes the key material from the KMS key on the specified date, making the KMS key unusable. To use the KMS key in cryptographic operations again, you must reimport the same key material. However, you can delete and reimport the key material at any time, including before the key material expires. Each time you reimport, you can eliminate or reset the expiration time. When this operation is successful, the key state of the KMS key changes from PendingImport to Enabled, and you can use the KMS key in cryptographic operations. If this operation fails, use the exception to help determine the problem. If the error is related to the key material, the import token, or wrapping key, use GetParametersForImport to get a new public key and import token for the KMS key and repeat the import procedure. For help, see How To Import Key Material in the Key Management Service Developer Guide. The KMS key that you use for this operation must be in a compatible key state. For details, see Key states of KMS keys in the Key Management Service Developer Guide. Cross-account use: No. You cannot perform this operation on a KMS key in a different Amazon Web Services account. Required permissions: kms:ImportKeyMaterial (key policy) Related operations: DeleteImportedKeyMaterial GetParametersForImport Eventual consistency: The KMS API follows an eventual consistency model. For more information, see KMS eventual consistency.
244
244
  */
245
245
  importKeyMaterial(callback?: (err: AWSError, data: KMS.Types.ImportKeyMaterialResponse) => void): Request<KMS.Types.ImportKeyMaterialResponse, AWSError>;
246
246
  /**
@@ -1103,15 +1103,19 @@ declare namespace KMS {
1103
1103
  */
1104
1104
  KeyId: KeyIdType;
1105
1105
  /**
1106
- * Specifies the name of the key policy. The only valid name is default. To get the names of key policies, use ListKeyPolicies.
1106
+ * Specifies the name of the key policy. If no policy name is specified, the default value is default. The only valid name is default. To get the names of key policies, use ListKeyPolicies.
1107
1107
  */
1108
- PolicyName: PolicyNameType;
1108
+ PolicyName?: PolicyNameType;
1109
1109
  }
1110
1110
  export interface GetKeyPolicyResponse {
1111
1111
  /**
1112
1112
  * A key policy document in JSON format.
1113
1113
  */
1114
1114
  Policy?: PolicyType;
1115
+ /**
1116
+ * The name of the key policy. The only valid value is default.
1117
+ */
1118
+ PolicyName?: PolicyNameType;
1115
1119
  }
1116
1120
  export interface GetKeyRotationStatusRequest {
1117
1121
  /**
@@ -1597,9 +1601,9 @@ declare namespace KMS {
1597
1601
  */
1598
1602
  KeyId: KeyIdType;
1599
1603
  /**
1600
- * The name of the key policy. The only valid value is default.
1604
+ * The name of the key policy. If no policy name is specified, the default value is default. The only valid value is default.
1601
1605
  */
1602
- PolicyName: PolicyNameType;
1606
+ PolicyName?: PolicyNameType;
1603
1607
  /**
1604
1608
  * The key policy to attach to the KMS key. The key policy must meet the following criteria: The key policy must allow the calling principal to make a subsequent PutKeyPolicy request on the KMS key. This reduces the risk that the KMS key becomes unmanageable. For more information, see Default key policy in the Key Management Service Developer Guide. (To omit this condition, set BypassPolicyLockoutSafetyCheck to true.) Each statement in the key policy must contain one or more principals. The principals in the key policy must exist and be visible to KMS. When you create a new Amazon Web Services principal, you might need to enforce a delay before including the new principal in a key policy because the new principal might not be immediately visible to KMS. For more information, see Changes that I make are not always immediately visible in the Amazon Web Services Identity and Access Management User Guide. A key policy document can include only the following characters: Printable ASCII characters from the space character (\u0020) through the end of the ASCII character range. Printable characters in the Basic Latin and Latin-1 Supplement character set (through \u00FF). The tab (\u0009), line feed (\u000A), and carriage return (\u000D) special characters For information about key policies, see Key policies in KMS in the Key Management Service Developer Guide.For help writing and formatting a JSON policy document, see the IAM JSON Policy Reference in the Identity and Access Management User Guide .
1605
1609
  */