cdk-lambda-subminute 2.0.439 → 2.0.441

package/node_modules/aws-sdk/clients/oam.d.ts

@@ -12,19 +12,19 @@ declare class OAM extends Service {
   constructor(options?: OAM.Types.ClientConfiguration)
   config: Config & OAM.Types.ClientConfiguration;
   /**
-   * Creates a link between a source account and a sink that you have created in a monitoring account. Before you create a link, you must create a sink in the monitoring account and create a sink policy in that account. The sink policy must permit the source account to link to it. You can grant permission to source accounts by granting permission to an entire organization or to individual accounts. For more information, see CreateSink and PutSinkPolicy. Each monitoring account can be linked to as many as 100,000 source accounts. Each source account can be linked to as many as five monitoring accounts.
+   * Creates a link between a source account and a sink that you have created in a monitoring account. After the link is created, data is sent from the source account to the monitoring account. When you create a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account. Before you create a link, you must create a sink in the monitoring account and create a sink policy in that account. The sink policy must permit the source account to link to it. You can grant permission to source accounts by granting permission to an entire organization or to individual accounts. For more information, see CreateSink and PutSinkPolicy. Each monitoring account can be linked to as many as 100,000 source accounts. Each source account can be linked to as many as five monitoring accounts.
    */
   createLink(params: OAM.Types.CreateLinkInput, callback?: (err: AWSError, data: OAM.Types.CreateLinkOutput) => void): Request<OAM.Types.CreateLinkOutput, AWSError>;
   /**
-   * Creates a link between a source account and a sink that you have created in a monitoring account. Before you create a link, you must create a sink in the monitoring account and create a sink policy in that account. The sink policy must permit the source account to link to it. You can grant permission to source accounts by granting permission to an entire organization or to individual accounts. For more information, see CreateSink and PutSinkPolicy. Each monitoring account can be linked to as many as 100,000 source accounts. Each source account can be linked to as many as five monitoring accounts.
+   * Creates a link between a source account and a sink that you have created in a monitoring account. After the link is created, data is sent from the source account to the monitoring account. When you create a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account. Before you create a link, you must create a sink in the monitoring account and create a sink policy in that account. The sink policy must permit the source account to link to it. You can grant permission to source accounts by granting permission to an entire organization or to individual accounts. For more information, see CreateSink and PutSinkPolicy. Each monitoring account can be linked to as many as 100,000 source accounts. Each source account can be linked to as many as five monitoring accounts.
    */
   createLink(callback?: (err: AWSError, data: OAM.Types.CreateLinkOutput) => void): Request<OAM.Types.CreateLinkOutput, AWSError>;
   /**
-   * Use this to create a sink in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data. After you create a sink, you must create a sink policy that allows source accounts to attach to it. For more information, see PutSinkPolicy. Each account can contain one sink. If you delete a sink, you can then create a new one in that account.
+   * Use this to create a sink in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data. After you create a sink, you must create a sink policy that allows source accounts to attach to it. For more information, see PutSinkPolicy. Each account can contain one sink per Region. If you delete a sink, you can then create a new one in that Region.
    */
   createSink(params: OAM.Types.CreateSinkInput, callback?: (err: AWSError, data: OAM.Types.CreateSinkOutput) => void): Request<OAM.Types.CreateSinkOutput, AWSError>;
   /**
-   * Use this to create a sink in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data. After you create a sink, you must create a sink policy that allows source accounts to attach to it. For more information, see PutSinkPolicy. Each account can contain one sink. If you delete a sink, you can then create a new one in that account.
+   * Use this to create a sink in the current account, so that it can be used as a monitoring account in CloudWatch cross-account observability. A sink is a resource that represents an attachment point in a monitoring account. Source accounts can link to the sink to send observability data. After you create a sink, you must create a sink policy that allows source accounts to attach to it. For more information, see PutSinkPolicy. Each account can contain one sink per Region. If you delete a sink, you can then create a new one in that Region.
    */
   createSink(callback?: (err: AWSError, data: OAM.Types.CreateSinkOutput) => void): Request<OAM.Types.CreateSinkOutput, AWSError>;
   /**
@@ -124,11 +124,11 @@ declare class OAM extends Service {
    */
   untagResource(callback?: (err: AWSError, data: OAM.Types.UntagResourceOutput) => void): Request<OAM.Types.UntagResourceOutput, AWSError>;
   /**
-   * Use this operation to change what types of data are shared from a source account to its linked monitoring account sink. You can't change the sink or change the monitoring account with this operation. To update the list of tags associated with the sink, use TagResource.
+   * Use this operation to change what types of data are shared from a source account to its linked monitoring account sink. You can't change the sink or change the monitoring account with this operation. When you update a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account. To update the list of tags associated with the sink, use TagResource.
    */
   updateLink(params: OAM.Types.UpdateLinkInput, callback?: (err: AWSError, data: OAM.Types.UpdateLinkOutput) => void): Request<OAM.Types.UpdateLinkOutput, AWSError>;
   /**
-   * Use this operation to change what types of data are shared from a source account to its linked monitoring account sink. You can't change the sink or change the monitoring account with this operation. To update the list of tags associated with the sink, use TagResource.
+   * Use this operation to change what types of data are shared from a source account to its linked monitoring account sink. You can't change the sink or change the monitoring account with this operation. When you update a link, you can optionally specify filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account. To update the list of tags associated with the sink, use TagResource.
    */
   updateLink(callback?: (err: AWSError, data: OAM.Types.UpdateLinkOutput) => void): Request<OAM.Types.UpdateLinkOutput, AWSError>;
 }
@@ -139,6 +139,10 @@ declare namespace OAM {
      * Specify a friendly human-readable name to use to identify this source account when you are viewing data from it in the monitoring account. You can use a custom label or use the following variables:    $AccountName is the name of the account    $AccountEmail is the globally unique email address of the account    $AccountEmailNoDomain is the email address of the account without the domain name  
      */
     LabelTemplate: LabelTemplate;
+    /**
+     * Use this structure to optionally create filters that specify that only some metric namespaces or log groups are to be shared from the source account to the monitoring account.
+     */
+    LinkConfiguration?: LinkConfiguration;
     /**
      * An array of strings that define which types of data that the source account shares with the monitoring account.
      */
@@ -169,6 +173,10 @@ declare namespace OAM {
      * The exact label template that you specified, with the variables not resolved.
      */
     LabelTemplate?: String;
+    /**
+     * This structure includes filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.
+     */
+    LinkConfiguration?: LinkConfiguration;
     /**
      * The resource types supported by this link.
      */
@@ -249,6 +257,10 @@ declare namespace OAM {
      * The exact label template that was specified when the link was created, with the template variables not resolved.
      */
     LabelTemplate?: String;
+    /**
+     * This structure includes filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.
+     */
+    LinkConfiguration?: LinkConfiguration;
     /**
      * The resource types supported by this link.
      */
@@ -293,6 +305,10 @@ declare namespace OAM {
     SinkIdentifier: ResourceIdentifier;
   }
   export interface GetSinkPolicyOutput {
+    /**
+     * The policy that you specified, in JSON format.
+     */
+    Policy?: String;
     /**
      * The ARN of the sink.
      */
@@ -301,12 +317,18 @@ declare namespace OAM {
      * The random ID string that Amazon Web Services generated as part of the sink ARN.
      */
     SinkId?: String;
+  }
+  export type LabelTemplate = string;
+  export interface LinkConfiguration {
     /**
-     * The policy that you specified, in JSON format.
+     * Use this structure to filter which log groups are to send log events from the source account to the monitoring account.
      */
-    Policy?: String;
+    LogGroupConfiguration?: LogGroupConfiguration;
+    /**
+     * Use this structure to filter which metric namespaces are to be shared from the source account to the monitoring account.
+     */
+    MetricConfiguration?: MetricConfiguration;
   }
-  export type LabelTemplate = string;
   export interface ListAttachedLinksInput {
     /**
      * Limits the number of returned links to the specified number.
@@ -439,18 +461,36 @@ declare namespace OAM {
      */
     Tags?: TagMapOutput;
   }
-  export type NextToken = string;
-  export interface PutSinkPolicyInput {
+  export interface LogGroupConfiguration {
     /**
-     * The ARN of the sink to attach this policy to.
+     * Use this field to specify which log groups are to share their log events with the monitoring account. Use the term LogGroupName and one or more of the following operands. Use single quotation marks (') around log group names. The matching of log group names is case sensitive. Each filter has a limit of five conditional operands. Conditional operands are AND and OR.    = and !=     AND     OR     LIKE and NOT LIKE. These can be used only as prefix searches. Include a % at the end of the string that you want to search for and include.    IN and NOT IN, using parentheses ( )    Examples:    LogGroupName IN ('This-Log-Group', 'Other-Log-Group') includes only the log groups with names This-Log-Group and Other-Log-Group.    LogGroupName NOT IN ('Private-Log-Group', 'Private-Log-Group-2') includes all log groups except the log groups with names Private-Log-Group and Private-Log-Group-2.    LogGroupName LIKE 'aws/lambda/%' OR LogGroupName LIKE 'AWSLogs%' includes all log groups that have names that start with aws/lambda/ or AWSLogs.    If you are updating a link that uses filters, you can specify * as the only value for the filter parameter to delete the filter and share all log groups with the monitoring account. 
      */
-    SinkIdentifier: ResourceIdentifier;
+    Filter: LogsFilter;
+  }
+  export type LogsFilter = string;
+  export interface MetricConfiguration {
+    /**
+     * Use this field to specify which metrics are to be shared with the monitoring account. Use the term Namespace and one or more of the following operands. Use single quotation marks (') around namespace names. The matching of namespace names is case sensitive. Each filter has a limit of five conditional operands. Conditional operands are AND and OR.    = and !=     AND     OR     LIKE and NOT LIKE. These can be used only as prefix searches. Include a % at the end of the string that you want to search for and include.    IN and NOT IN, using parentheses ( )    Examples:    Namespace NOT LIKE 'AWS/%' includes only namespaces that don't start with AWS/, such as custom namespaces.    Namespace IN ('AWS/EC2', 'AWS/ELB', 'AWS/S3') includes only the metrics in the EC2, Elastic Load Balancing, and Amazon S3 namespaces.     Namespace = 'AWS/EC2' OR Namespace NOT LIKE 'AWS/%' includes only the EC2 namespace and your custom namespaces.    If you are updating a link that uses filters, you can specify * as the only value for the filter parameter to delete the filter and share all metric namespaces with the monitoring account. 
+     */
+    Filter: MetricsFilter;
+  }
+  export type MetricsFilter = string;
+  export type NextToken = string;
+  export interface PutSinkPolicyInput {
     /**
      * The JSON policy to use. If you are updating an existing policy, the entire existing policy is replaced by what you specify here. The policy must be in JSON string format with quotation marks escaped and no newlines. For examples of different types of policies, see the Examples section on this page.
      */
     Policy: SinkPolicy;
+    /**
+     * The ARN of the sink to attach this policy to.
+     */
+    SinkIdentifier: ResourceIdentifier;
   }
   export interface PutSinkPolicyOutput {
+    /**
+     * The policy that you specified.
+     */
+    Policy?: String;
     /**
      * The ARN of the sink.
      */
@@ -459,10 +499,6 @@ declare namespace OAM {
      * The random ID string that Amazon Web Services generated as part of the sink ARN.
      */
     SinkId?: String;
-    /**
-     * The policy that you specified.
-     */
-    Policy?: String;
   }
   export type ResourceIdentifier = string;
   export type ResourceType = "AWS::CloudWatch::Metric"|"AWS::Logs::LogGroup"|"AWS::XRay::Trace"|"AWS::ApplicationInsights::Application"|"AWS::InternetMonitor::Monitor"|string;
@@ -505,6 +541,10 @@ declare namespace OAM {
      * The ARN of the link that you want to update.
      */
     Identifier: ResourceIdentifier;
+    /**
+     * Use this structure to filter which metric namespaces and which log groups are to be shared from the source account to the monitoring account.
+     */
+    LinkConfiguration?: LinkConfiguration;
     /**
      * An array of strings that define which types of data that the source account will send to the monitoring account. Your input here replaces the current set of data types that are shared.
      */
@@ -527,6 +567,10 @@ declare namespace OAM {
      * The exact label template that was specified when the link was created, with the template variables not resolved.
      */
     LabelTemplate?: LabelTemplate;
+    /**
+     * This structure includes filters that specify which metric namespaces and which log groups are shared from the source account to the monitoring account.
+     */
+    LinkConfiguration?: LinkConfiguration;
     /**
      * The resource types now supported by this link.
      */

package/node_modules/aws-sdk/clients/rds.d.ts

@@ -2464,7 +2464,7 @@ declare namespace RDS {
      */
     PromotionTier?: IntegerOptional;
     /**
-     * The time zone of the DB instance. The time zone parameter is currently supported only by Microsoft SQL Server.
+     * The time zone of the DB instance. The time zone parameter is currently supported only by RDS for Db2 and RDS for SQL Server.
      */
     Timezone?: String;
     /**
@@ -3966,6 +3966,10 @@ declare namespace RDS {
      * JSON string that lists the installation files and parameters that RDS Custom uses to create a custom engine version (CEV). RDS Custom applies the patches in the order in which they're listed in the manifest. You can set the Oracle home, Oracle base, and UNIX/Linux user and group using the installation parameters. For more information, see JSON fields in the CEV manifest in the Amazon RDS User Guide. 
      */
     CustomDBEngineVersionManifest?: CustomDBEngineVersionManifest;
+    /**
+     * Indicates whether the DB engine version supports Aurora Limitless Database.
+     */
+    SupportsLimitlessDatabase?: Boolean;
     /**
      * Indicates whether the engine version supports rotating the server certificate without rebooting the DB instance.
      */
@@ -4196,7 +4200,7 @@ declare namespace RDS {
      */
     DBInstanceArn?: String;
     /**
-     * The time zone of the DB instance. In most cases, the Timezone element is empty. Timezone content appears only for Microsoft SQL Server DB instances that were created with a time zone specified.
+     * The time zone of the DB instance. In most cases, the Timezone element is empty. Timezone content appears only for RDS for Db2 and RDS for SQL Server DB instances that were created with a time zone specified.
      */
     Timezone?: String;
     /**
@@ -7582,7 +7586,7 @@ declare namespace RDS {
      */
     DBInstanceClass?: String;
     /**
-     * The new DB subnet group for the DB instance. You can use this parameter to move your DB instance to a different VPC. If your DB instance isn't in a VPC, you can also use this parameter to move your DB instance into a VPC. For more information, see Working with a DB instance in a VPC in the Amazon RDS User Guide. Changing the subnet group causes an outage during the change. The change is applied during the next maintenance window, unless you enable ApplyImmediately. This parameter doesn't apply to RDS Custom DB instances. Constraints:   If supplied, must match existing DB subnet group.   Example: mydbsubnetgroup 
+     * The new DB subnet group for the DB instance. You can use this parameter to move your DB instance to a different VPC. If your DB instance isn't in a VPC, you can also use this parameter to move your DB instance into a VPC. For more information, see Working with a DB instance in a VPC in the Amazon RDS User Guide. Changing the subnet group causes an outage during the change. The change is applied during the next maintenance window, unless you enable ApplyImmediately. This setting doesn't apply to RDS Custom DB instances. Constraints:   If supplied, must match existing DB subnet group.   Example: mydbsubnetgroup 
      */
     DBSubnetGroupName?: String;
     /**
@@ -7746,7 +7750,7 @@ declare namespace RDS {
      */
     UseDefaultProcessorFeatures?: BooleanOptional;
     /**
-     * Specifies whether the DB instance has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection isn't enabled. For more information, see  Deleting a DB Instance.
+     * Specifies whether the DB instance has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection isn't enabled. For more information, see  Deleting a DB Instance. This setting doesn't apply to Amazon Aurora DB instances. You can enable or disable deletion protection for the DB cluster. For more information, see ModifyDBCluster. DB instances in a DB cluster can be deleted even when deletion protection is enabled for the DB cluster.
      */
     DeletionProtection?: BooleanOptional;
     /**
@@ -10717,6 +10721,10 @@ declare namespace RDS {
      * Indicates whether you can use Babelfish for Aurora PostgreSQL with the target engine version.
      */
     SupportsBabelfish?: BooleanOptional;
+    /**
+     * Indicates whether the DB engine version supports Aurora Limitless Database.
+     */
+    SupportsLimitlessDatabase?: BooleanOptional;
     /**
      * Indicates whether the target engine version supports forwarding write operations from reader DB instances to the writer DB instance in the DB cluster. By default, write operations aren't allowed on reader DB instances. Valid for: Aurora DB clusters only
      */

package/node_modules/aws-sdk/clients/stepfunctions.d.ts

@@ -299,6 +299,14 @@ declare class StepFunctions extends Service {
    * Updates the configuration of an existing state machine alias by modifying its description or routingConfiguration. You must specify at least one of the description or routingConfiguration parameters to update a state machine alias.   UpdateStateMachineAlias is an idempotent API. Step Functions bases the idempotency check on the stateMachineAliasArn, description, and routingConfiguration parameters. Requests with the same parameters return an idempotent response.   This operation is eventually consistent. All StartExecution requests made within a few seconds use the latest alias configuration. Executions started immediately after calling UpdateStateMachineAlias may use the previous routing configuration.   Related operations:     CreateStateMachineAlias     DescribeStateMachineAlias     ListStateMachineAliases     DeleteStateMachineAlias   
    */
   updateStateMachineAlias(callback?: (err: AWSError, data: StepFunctions.Types.UpdateStateMachineAliasOutput) => void): Request<StepFunctions.Types.UpdateStateMachineAliasOutput, AWSError>;
+  /**
+   * Validates the syntax of a state machine definition. You can validate that a state machine definition is correct without creating a state machine resource. Step Functions will implicitly perform the same syntax check when you invoke CreateStateMachine and UpdateStateMachine. State machine definitions are specified using a JSON-based, structured language. For more information on Amazon States Language see Amazon States Language (ASL).  Suggested uses for ValidateStateMachineDefinition:   Integrate automated checks into your code review or Continuous Integration (CI) process to validate state machine definitions before starting deployments.   Run the validation from a Git pre-commit hook to check your state machine definitions before committing them to your source repository.    Errors found in the state machine definition will be returned in the response as a list of diagnostic elements, rather than raise an exception. 
+   */
+  validateStateMachineDefinition(params: StepFunctions.Types.ValidateStateMachineDefinitionInput, callback?: (err: AWSError, data: StepFunctions.Types.ValidateStateMachineDefinitionOutput) => void): Request<StepFunctions.Types.ValidateStateMachineDefinitionOutput, AWSError>;
+  /**
+   * Validates the syntax of a state machine definition. You can validate that a state machine definition is correct without creating a state machine resource. Step Functions will implicitly perform the same syntax check when you invoke CreateStateMachine and UpdateStateMachine. State machine definitions are specified using a JSON-based, structured language. For more information on Amazon States Language see Amazon States Language (ASL).  Suggested uses for ValidateStateMachineDefinition:   Integrate automated checks into your code review or Continuous Integration (CI) process to validate state machine definitions before starting deployments.   Run the validation from a Git pre-commit hook to check your state machine definitions before committing them to your source repository.    Errors found in the state machine definition will be returned in the response as a list of diagnostic elements, rather than raise an exception. 
+   */
+  validateStateMachineDefinition(callback?: (err: AWSError, data: StepFunctions.Types.ValidateStateMachineDefinitionOutput) => void): Request<StepFunctions.Types.ValidateStateMachineDefinitionOutput, AWSError>;
 }
 declare namespace StepFunctions {
   export interface ActivityFailedEventDetails {
@@ -2252,6 +2260,50 @@ declare namespace StepFunctions {
      */
     stateMachineVersionArn?: Arn;
   }
+  export type ValidateStateMachineDefinitionCode = string;
+  export interface ValidateStateMachineDefinitionDiagnostic {
+    /**
+     * A value of ERROR means that you cannot create or update a state machine with this definition.
+     */
+    severity: ValidateStateMachineDefinitionSeverity;
+    /**
+     * Identifying code for the diagnostic.
+     */
+    code: ValidateStateMachineDefinitionCode;
+    /**
+     * Message describing the diagnostic condition.
+     */
+    message: ValidateStateMachineDefinitionMessage;
+    /**
+     * Location of the issue in the state machine, if available. For errors specific to a field, the location could be in the format: /States/&lt;StateName&gt;/&lt;FieldName&gt;, for example: /States/FailState/ErrorPath.
+     */
+    location?: ValidateStateMachineDefinitionLocation;
+  }
+  export type ValidateStateMachineDefinitionDiagnosticList = ValidateStateMachineDefinitionDiagnostic[];
+  export interface ValidateStateMachineDefinitionInput {
+    /**
+     * The Amazon States Language definition of the state machine. For more information, see Amazon States Language (ASL).
+     */
+    definition: Definition;
+    /**
+     * The target type of state machine for this definition. The default is STANDARD.
+     */
+    type?: StateMachineType;
+  }
+  export type ValidateStateMachineDefinitionLocation = string;
+  export type ValidateStateMachineDefinitionMessage = string;
+  export interface ValidateStateMachineDefinitionOutput {
+    /**
+     * The result value will be OK when no syntax errors are found, or FAIL if the workflow definition does not pass verification.
+     */
+    result: ValidateStateMachineDefinitionResultCode;
+    /**
+     * If the result is OK, this field will be empty. When there are errors, this field will contain an array of Diagnostic objects to help you troubleshoot.
+     */
+    diagnostics: ValidateStateMachineDefinitionDiagnosticList;
+  }
+  export type ValidateStateMachineDefinitionResultCode = "OK"|"FAIL"|string;
+  export type ValidateStateMachineDefinitionSeverity = "ERROR"|string;
   export type VersionDescription = string;
   export type VersionWeight = number;
   export type includedDetails = boolean;

package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js

@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
 	  /**
 	   * @constant
 	   */
-	  VERSION: '2.1606.0',
+	  VERSION: '2.1608.0',
 
 	  /**
 	   * @api private