@awboost/cfn-resource-types 0.1.72 → 0.1.74

package/lib/AWS-Bedrock-GuardrailVersion.d.ts

@@ -0,0 +1,52 @@
+import { Resource as $Resource } from "@awboost/cfn-template-builder/template/resource";
+import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-builder/template";
+/**
+ * Definition of AWS::Bedrock::GuardrailVersion Resource Type
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-bedrock-guardrailversion.html}
+ */
+export type BedrockGuardrailVersionProperties = {
+    /**
+     * Description of the Guardrail version
+     * @minLength `1`
+     * @maxLength `200`
+     */
+    Description?: string;
+    /**
+     * Identifier (GuardrailId or GuardrailArn) for the guardrail
+     * @maxLength `2048`
+     * @pattern `^(([a-z0-9]+)|(arn:aws(-[^:]+)?:bedrock:[a-z0-9-]{1,20}:[0-9]{12}:guardrail/[a-z0-9]+))$`
+     */
+    GuardrailIdentifier: string;
+};
+/**
+ * Attribute type definition for `AWS::Bedrock::GuardrailVersion`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-bedrock-guardrailversion.html#aws-resource-bedrock-guardrailversion-return-values}
+ */
+export type BedrockGuardrailVersionAttributes = {
+    /**
+     * Arn representation for the guardrail
+     * @maxLength `2048`
+     * @pattern `^arn:aws(-[^:]+)?:bedrock:[a-z0-9-]{1,20}:[0-9]{12}:guardrail/[a-z0-9]+$`
+     */
+    GuardrailArn: string;
+    /**
+     * Unique id for the guardrail
+     * @maxLength `64`
+     * @pattern `^[a-z0-9]+$`
+     */
+    GuardrailId: string;
+    /**
+     * Guardrail version
+     * @pattern `^[1-9][0-9]{0,7}$`
+     */
+    Version: string;
+};
+/**
+ * Definition of AWS::Bedrock::GuardrailVersion Resource Type
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-bedrock-guardrailversion.html}
+ */
+export declare class BedrockGuardrailVersion extends $Resource<"AWS::Bedrock::GuardrailVersion", BedrockGuardrailVersionProperties, BedrockGuardrailVersionAttributes> {
+    static readonly Type = "AWS::Bedrock::GuardrailVersion";
+    constructor(logicalId: string, properties: BedrockGuardrailVersionProperties, options?: $ResourceOptions);
+}
+//# sourceMappingURL=AWS-Bedrock-GuardrailVersion.d.ts.map

package/lib/AWS-Bedrock-GuardrailVersion.js

@@ -0,0 +1,12 @@
+import { Resource as $Resource } from "@awboost/cfn-template-builder/template/resource";
+/**
+ * Definition of AWS::Bedrock::GuardrailVersion Resource Type
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-bedrock-guardrailversion.html}
+ */
+export class BedrockGuardrailVersion extends $Resource {
+    static Type = "AWS::Bedrock::GuardrailVersion";
+    constructor(logicalId, properties, options) {
+        super(logicalId, BedrockGuardrailVersion.Type, properties, options);
+    }
+}
+//# sourceMappingURL=AWS-Bedrock-GuardrailVersion.js.map

package/lib/AWS-Budgets-BudgetsAction.d.ts

@@ -13,6 +13,7 @@ export type BudgetsBudgetsActionProperties = {
     Definition: Definition;
     ExecutionRoleArn: string;
     NotificationType: "ACTUAL" | "FORECASTED";
+    ResourceTags?: ResourceTag[];
     /**
      * @minLength `1`
      * @maxLength `11`
@@ -65,6 +66,14 @@ export type IamActionDefinition = {
      */
     Users?: string[];
 };
+/**
+ * Type definition for `AWS::Budgets::BudgetsAction.ResourceTag`.
+ * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-budgets-budgetsaction-resourcetag.html}
+ */
+export type ResourceTag = {
+    Key: string;
+    Value: string;
+};
 /**
  * Type definition for `AWS::Budgets::BudgetsAction.ScpActionDefinition`.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-budgets-budgetsaction-scpactiondefinition.html}

package/lib/AWS-EC2-LaunchTemplate.d.ts

@@ -5,7 +5,7 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
  * Specifies the properties for creating a launch template.
  The minimum required properties for specifying a launch template are as follows:
   +  You must specify at least one property for the launch template data.
-  +  You do not need to specify a name for the launch template. If you do not specify a name, CFN creates the name for you.
+  +  You can optionally specify a name for the launch template. If you do not specify a name, CFN creates a name for you.
   
  A launch template can contain some or all of the configuration information to launch an instance. When you launch an instance using a launch template, instance properties that are not specified in the launch template use default values, except the ``ImageId`` property, which has no default value. If you do not specify an AMI ID for the launch template ``ImageId`` property, you must specify an AMI ID for the instance ``ImageId`` property.
  For more information, see [Launch an instance from a launch template](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html) in the *Amazon EC2 User Guide*.
@@ -920,7 +920,7 @@ export type NetworkInterface = {
      */
     Description?: string;
     /**
-     * The device index for the network interface attachment.
+     * The device index for the network interface attachment. Each network interface requires a device index. If you create a launch template that includes secondary network interfaces but not a primary network interface, then you must add a primary network interface as a launch parameter when you launch an instance from the template.
      */
     DeviceIndex?: number;
     /**
@@ -1186,7 +1186,7 @@ export type VCpuCount = {
  * Specifies the properties for creating a launch template.
  The minimum required properties for specifying a launch template are as follows:
   +  You must specify at least one property for the launch template data.
-  +  You do not need to specify a name for the launch template. If you do not specify a name, CFN creates the name for you.
+  +  You can optionally specify a name for the launch template. If you do not specify a name, CFN creates a name for you.
   
  A launch template can contain some or all of the configuration information to launch an instance. When you launch an instance using a launch template, instance properties that are not specified in the launch template use default values, except the ``ImageId`` property, which has no default value. If you do not specify an AMI ID for the launch template ``ImageId`` property, you must specify an AMI ID for the instance ``ImageId`` property.
  For more information, see [Launch an instance from a launch template](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html) in the *Amazon EC2 User Guide*.

package/lib/AWS-EC2-LaunchTemplate.js

@@ -4,7 +4,7 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
  * Specifies the properties for creating a launch template.
  The minimum required properties for specifying a launch template are as follows:
   +  You must specify at least one property for the launch template data.
-  +  You do not need to specify a name for the launch template. If you do not specify a name, CFN creates the name for you.
+  +  You can optionally specify a name for the launch template. If you do not specify a name, CFN creates a name for you.
   
  A launch template can contain some or all of the configuration information to launch an instance. When you launch an instance using a launch template, instance properties that are not specified in the launch template use default values, except the ``ImageId`` property, which has no default value. If you do not specify an AMI ID for the launch template ``ImageId`` property, you must specify an AMI ID for the instance ``ImageId`` property.
  For more information, see [Launch an instance from a launch template](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html) in the *Amazon EC2 User Guide*.

package/lib/AWS-KMS-Alias.d.ts

@@ -3,7 +3,15 @@ import type { ResourceOptions as $ResourceOptions } from "@awboost/cfn-template-
 /**
  * The ``AWS::KMS::Alias`` resource specifies a display name for a [KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys). You can use an alias to identify a KMS key in the KMS console, in the [DescribeKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_DescribeKey.html) operation, and in [cryptographic operations](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations), such as [Decrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html) and [GenerateDataKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateDataKey.html).
   Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see [ABAC for](https://docs.aws.amazon.com/kms/latest/developerguide/abac.html) in the *Developer Guide*.
-  Using an alias to refer to a KMS key can help you simplify key management. For example, an alias in your code can be associated with different KMS keys i
+  Using an alias to refer to a KMS key can help you simplify key management. For example, an alias in your code can be associated with different KMS keys in different AWS-Regions. For more information, see [Using aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html) in the *Developer Guide*.
+ When specifying an alias, observe the following rules.
+  +  Each alias is associated with one KMS key, but multiple aliases can be associated with the same KMS key.
+  +  The alias and its associated KMS key must be in the same AWS-account and Region.
+  +  The alias name must be unique in the AWS-account and Region. However, you can create aliases with the same name in different AWS-Regions. For example, you can have an ``alias/projectKey`` in multiple Regions, each of which is associated with a KMS key in its Region.
+  +  Each alias name must begin with ``alias/`` followed by a name, such as ``alias/exampleKey``. The alias name can contain only alphanumeric characters, forward slashes (/), underscores (_), and dashes (-). Alias names cannot begin with ``alias/aws/``. That alias name prefix is reserved for [](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+  
+  *Regions*
+  KMS CloudFormation resources are available in all AWS-Regions in which KMS and CFN are supported.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kms-alias.html}
  */
 export type KMSAliasProperties = {
@@ -34,7 +42,15 @@ export type KMSAliasProperties = {
 /**
  * The ``AWS::KMS::Alias`` resource specifies a display name for a [KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys). You can use an alias to identify a KMS key in the KMS console, in the [DescribeKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_DescribeKey.html) operation, and in [cryptographic operations](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations), such as [Decrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html) and [GenerateDataKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateDataKey.html).
   Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see [ABAC for](https://docs.aws.amazon.com/kms/latest/developerguide/abac.html) in the *Developer Guide*.
-  Using an alias to refer to a KMS key can help you simplify key management. For example, an alias in your code can be associated with different KMS keys i
+  Using an alias to refer to a KMS key can help you simplify key management. For example, an alias in your code can be associated with different KMS keys in different AWS-Regions. For more information, see [Using aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html) in the *Developer Guide*.
+ When specifying an alias, observe the following rules.
+  +  Each alias is associated with one KMS key, but multiple aliases can be associated with the same KMS key.
+  +  The alias and its associated KMS key must be in the same AWS-account and Region.
+  +  The alias name must be unique in the AWS-account and Region. However, you can create aliases with the same name in different AWS-Regions. For example, you can have an ``alias/projectKey`` in multiple Regions, each of which is associated with a KMS key in its Region.
+  +  Each alias name must begin with ``alias/`` followed by a name, such as ``alias/exampleKey``. The alias name can contain only alphanumeric characters, forward slashes (/), underscores (_), and dashes (-). Alias names cannot begin with ``alias/aws/``. That alias name prefix is reserved for [](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+  
+  *Regions*
+  KMS CloudFormation resources are available in all AWS-Regions in which KMS and CFN are supported.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kms-alias.html}
  */
 export declare class KMSAlias extends $Resource<"AWS::KMS::Alias", KMSAliasProperties, Record<string, never>> {

package/lib/AWS-KMS-Alias.js

@@ -2,7 +2,15 @@ import { Resource as $Resource } from "@awboost/cfn-template-builder/template/re
 /**
  * The ``AWS::KMS::Alias`` resource specifies a display name for a [KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#kms_keys). You can use an alias to identify a KMS key in the KMS console, in the [DescribeKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_DescribeKey.html) operation, and in [cryptographic operations](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#cryptographic-operations), such as [Decrypt](https://docs.aws.amazon.com/kms/latest/APIReference/API_Decrypt.html) and [GenerateDataKey](https://docs.aws.amazon.com/kms/latest/APIReference/API_GenerateDataKey.html).
   Adding, deleting, or updating an alias can allow or deny permission to the KMS key. For details, see [ABAC for](https://docs.aws.amazon.com/kms/latest/developerguide/abac.html) in the *Developer Guide*.
-  Using an alias to refer to a KMS key can help you simplify key management. For example, an alias in your code can be associated with different KMS keys i
+  Using an alias to refer to a KMS key can help you simplify key management. For example, an alias in your code can be associated with different KMS keys in different AWS-Regions. For more information, see [Using aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html) in the *Developer Guide*.
+ When specifying an alias, observe the following rules.
+  +  Each alias is associated with one KMS key, but multiple aliases can be associated with the same KMS key.
+  +  The alias and its associated KMS key must be in the same AWS-account and Region.
+  +  The alias name must be unique in the AWS-account and Region. However, you can create aliases with the same name in different AWS-Regions. For example, you can have an ``alias/projectKey`` in multiple Regions, each of which is associated with a KMS key in its Region.
+  +  Each alias name must begin with ``alias/`` followed by a name, such as ``alias/exampleKey``. The alias name can contain only alphanumeric characters, forward slashes (/), underscores (_), and dashes (-). Alias names cannot begin with ``alias/aws/``. That alias name prefix is reserved for [](https://docs.aws.amazon.com/kms/latest/developerguide/concepts.html#aws-managed-cmk).
+  
+  *Regions*
+  KMS CloudFormation resources are available in all AWS-Regions in which KMS and CFN are supported.
  * @see {@link https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-kms-alias.html}
  */
 export class KMSAlias extends $Resource {