feat: update L1 CloudFormation resource definitions (#34064)

aws-cdk-automation · web-flow · commit 9cb260266e92 · 2025-04-08T23:51:21.000Z
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-apigateway │ └ resources │ └[~] resource AWS::ApiGateway::DomainName │ └ - documentation: The `AWS::ApiGateway::DomainName` resource specifies a public custom domain name for your API in API Gateway. │ You can use a custom domain name to provide a URL that's more intuitive and easier to recall. For more information about using custom domain names, see [Set up Custom Domain Name for an API in API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html) in the *API Gateway Developer Guide* . │ + documentation: The `AWS::ApiGateway::DomainName` resource specifies a public custom domain name for your API in API Gateway. │ To create a custom domain name for private APIs, use [AWS::ApiGateway::DomainV2](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigateway-domainnamev2.html) . │ You can use a custom domain name to provide a URL that's more intuitive and easier to recall. For more information about using custom domain names, see [Set up Custom Domain Name for an API in API Gateway](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html) in the *API Gateway Developer Guide* . ├[~] service aws-bedrock │ └ resources │ ├[~] resource AWS::Bedrock::Prompt │ │ └ types │ │ ├[~] type CachePointBlock │ │ │ ├ - documentation: Indicates where a cache checkpoint is located. All information before this checkpoint is cached to be accessed on subsequent requests. │ │ │ │ + documentation: Defines a section of content to be cached for reuse in subsequent API calls. │ │ │ └ properties │ │ │ └ Type: (documentation changed) │ │ ├[~] type ContentBlock │ │ │ └ properties │ │ │ └ CachePoint: (documentation changed) │ │ ├[~] type SystemContentBlock │ │ │ └ properties │ │ │ └ CachePoint: (documentation changed) │ │ └[~] type Tool │ │ └ properties │ │ └ CachePoint: (documentation changed) │ └[~] resource AWS::Bedrock::PromptVersion │ └ types │ ├[~] type CachePointBlock │ │ ├ - documentation: Indicates where a cache checkpoint is located. All information before this checkpoint is cached to be accessed on subsequent requests. │ │ │ + documentation: Defines a section of content to be cached for reuse in subsequent API calls. │ │ └ properties │ │ └ Type: (documentation changed) │ ├[~] type ContentBlock │ │ └ properties │ │ └ CachePoint: (documentation changed) │ ├[~] type SystemContentBlock │ │ └ properties │ │ └ CachePoint: (documentation changed) │ └[~] type Tool │ └ properties │ └ CachePoint: (documentation changed) ├[+] service aws-dsql │ ├ capitalized: DSQL │ │ cloudFormationNamespace: AWS::DSQL │ │ name: aws-dsql │ │ shortName: dsql │ └ resources │ └ resource AWS::DSQL::Cluster │ ├ name: Cluster │ │ cloudFormationType: AWS::DSQL::Cluster │ │ documentation: Resource Type definition for AWS::DSQL::Cluster │ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"} │ ├ properties │ │ ├ DeletionProtectionEnabled: boolean │ │ └ Tags: Array<tag> │ └ attributes │ ├ ResourceArn: string │ ├ Identifier: string │ ├ CreationTime: string │ └ Status: string ├[~] service aws-dynamodb │ └ resources │ ├[~] resource AWS::DynamoDB::GlobalTable │ │ └ types │ │ └[~] type Projection │ │ └ properties │ │ └ NonKeyAttributes: (documentation changed) │ └[~] resource AWS::DynamoDB::Table │ └ types │ └[~] type Projection │ └ properties │ └ NonKeyAttributes: (documentation changed) ├[~] service aws-ec2 │ └ resources │ ├[~] resource AWS::EC2::Instance │ │ └ types │ │ └[~] type NetworkInterface │ │ └ properties │ │ └ EnaSrdSpecification: (documentation changed) │ ├[~] resource AWS::EC2::LaunchTemplate │ │ └ types │ │ └[~] type NetworkInterface │ │ └ properties │ │ └ DeviceIndex: (documentation changed) │ ├[~] resource AWS::EC2::RouteServer │ │ ├ - documentation: VPC Route Server │ │ │ + documentation: Specifies a route server to manage dynamic routing in a VPC. │ │ │ Amazon VPC Route Server simplifies routing for traffic between workloads that are deployed within a VPC and its internet gateways. With this feature, VPC Route Server dynamically updates VPC and internet gateway route tables with your preferred routes to achieve routing fault tolerance for those workloads. This enables you to automatically reroute traffic within a VPC, which increases the manageability of VPC routing and interoperability with third-party workloads. │ │ │ For more information see [Dynamic routing in your VPC with VPC Route Server](https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html) in the *Amazon VPC User Guide* . │ │ ├ properties │ │ │ ├ AmazonSideAsn: (documentation changed) │ │ │ ├ PersistRoutes: (documentation changed) │ │ │ ├ PersistRoutesDuration: (documentation changed) │ │ │ ├ SnsNotificationsEnabled: (documentation changed) │ │ │ └ Tags: (documentation changed) │ │ └ attributes │ │ ├ Arn: (documentation changed) │ │ └ Id: (documentation changed) │ ├[~] resource AWS::EC2::RouteServerAssociation │ │ ├ - documentation: VPC Route Server Association │ │ │ + documentation: Specifies the association between a route server and a VPC. │ │ │ A route server association is the connection established between a route server and a VPC. │ │ └ properties │ │ ├ RouteServerId: (documentation changed) │ │ └ VpcId: (documentation changed) │ ├[~] resource AWS::EC2::RouteServerEndpoint │ │ ├ - documentation: VPC Route Server Endpoint │ │ │ + documentation: Creates a new endpoint for a route server in a specified subnet. │ │ │ A route server endpoint is an AWS -managed component inside a subnet that facilitates [BGP (Border Gateway Protocol)](https://docs.aws.amazon.com/https://en.wikipedia.org/wiki/Border_Gateway_Protocol) connections between your route server and your BGP peers. │ │ │ For more information see [Dynamic routing in your VPC with VPC Route Server](https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html) in the *Amazon VPC User Guide* . │ │ ├ properties │ │ │ ├ RouteServerId: (documentation changed) │ │ │ ├ SubnetId: (documentation changed) │ │ │ └ Tags: (documentation changed) │ │ └ attributes │ │ ├ Arn: (documentation changed) │ │ ├ EniAddress: (documentation changed) │ │ ├ EniId: (documentation changed) │ │ ├ Id: (documentation changed) │ │ └ VpcId: (documentation changed) │ ├[~] resource AWS::EC2::RouteServerPeer │ │ ├ - documentation: VPC Route Server Peer │ │ │ + documentation: Specifies a BGP peer configuration for a route server endpoint. │ │ │ A route server peer is a session between a route server endpoint and the device deployed in AWS (such as a firewall appliance or other network security function running on an EC2 instance). │ │ ├ properties │ │ │ ├ BgpOptions: (documentation changed) │ │ │ ├ PeerAddress: (documentation changed) │ │ │ ├ RouteServerEndpointId: (documentation changed) │ │ │ └ Tags: (documentation changed) │ │ ├ attributes │ │ │ ├ Arn: (documentation changed) │ │ │ ├ EndpointEniAddress: (documentation changed) │ │ │ ├ EndpointEniId: (documentation changed) │ │ │ ├ Id: (documentation changed) │ │ │ ├ RouteServerId: (documentation changed) │ │ │ ├ SubnetId: (documentation changed) │ │ │ └ VpcId: (documentation changed) │ │ └ types │ │ └[~] type BgpOptions │ │ ├ - documentation: BGP Options │ │ │ + documentation: The BGP configuration options for this peer, including ASN (Autonomous System Number) and BFD (Bidrectional Forwarding Detection) settings. │ │ └ properties │ │ ├ PeerAsn: (documentation changed) │ │ └ PeerLivenessDetection: (documentation changed) │ ├[~] resource AWS::EC2::RouteServerPropagation │ │ ├ - documentation: VPC Route Server Propagation │ │ │ + documentation: Specifies route propagation from a route server to a route table. │ │ │ For more information see [Dynamic routing in your VPC with VPC Route Server](https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html) in the *Amazon VPC User Guide* . │ │ └ properties │ │ ├ RouteServerId: (documentation changed) │ │ └ RouteTableId: (documentation changed) │ └[~] resource AWS::EC2::SecurityGroup │ ├ - documentation: Specifies a security group. │ │ You must specify ingress rules to allow inbound traffic. By default, no inbound traffic is allowed. │ │ If you do not specify an egress rule, we add egress rules that allow outbound IPv4 and IPv6 traffic on all ports and protocols to any destination. We do not add these rules if you specify your own egress rules. │ │ This type supports updates. For more information about updating stacks, see [AWS CloudFormation Stacks Updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ > To cross-reference two security groups in the ingress and egress rules of those security groups, use the [AWS::EC2::SecurityGroupEgress](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-security-group-egress.html) and [AWS::EC2::SecurityGroupIngress](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-security-group-ingress.html) resources to define your rules. Do not use the embedded ingress and egress rules in the `AWS::EC2::SecurityGroup` . Doing so creates a circular dependency, which AWS CloudFormation doesn't allow. │ │ + documentation: Specifies a security group. │ │ You must specify ingress rules to allow inbound traffic. By default, no inbound traffic is allowed. │ │ If you do not specify an egress rule, we add egress rules that allow outbound IPv4 and IPv6 traffic on all ports and protocols to any destination. We do not add these rules if you specify your own egress rules. │ │ If you modify a rule, CloudFormation removes the existing rule and then adds a new rule. There is a brief period when neither the original rule or the new rule exists, so the corresponding traffic is dropped. │ │ This type supports updates. For more information about updating stacks, see [AWS CloudFormation Stacks Updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ > To cross-reference two security groups in the ingress and egress rules of those security groups, use the [AWS::EC2::SecurityGroupEgress](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-security-group-egress.html) and [AWS::EC2::SecurityGroupIngress](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-security-group-ingress.html) resources to define your rules. Do not use the embedded ingress and egress rules in the `AWS::EC2::SecurityGroup` . Doing so creates a circular dependency, which AWS CloudFormation doesn't allow. │ └ properties │ ├ SecurityGroupEgress: (documentation changed) │ └ SecurityGroupIngress: (documentation changed) ├[~] service aws-fsx │ └ resources │ └[~] resource AWS::FSx::FileSystem │ └ types │ └[~] type WindowsConfiguration │ └ properties │ └ WeeklyMaintenanceStartTime: (documentation changed) ├[~] service aws-gamelift │ └ resources │ ├[~] resource AWS::GameLift::Alias │ │ ├ - tagInformation: undefined │ │ │ + tagInformation: {"tagPropertyName":"Tags","variant":"standard"} │ │ ├ properties │ │ │ └[+] Tags: Array<tag> │ │ └ attributes │ │ └[+] AliasArn: string │ ├[~] resource AWS::GameLift::Build │ │ ├ - tagInformation: undefined │ │ │ + tagInformation: {"tagPropertyName":"Tags","variant":"standard"} │ │ ├ properties │ │ │ └[+] Tags: Array<tag> │ │ └ attributes │ │ └[+] BuildArn: string │ └[~] resource AWS::GameLift::ContainerGroupDefinition │ ├ properties │ │ └ OperatingSystem: (documentation changed) │ └ types │ └[~] type ContainerPortRange │ └ - documentation: A set of one or more port numbers that can be opened on the container. │ *Part of:* [ContainerPortConfiguration](https://docs.aws.amazon.com/gamelift/latest/apireference/API_ContainerPortConfiguration.html) │ + documentation: A set of one or more port numbers that can be opened on the container, and the supported network protocol. │ *Part of:* [ContainerPortConfiguration](https://docs.aws.amazon.com/gamelift/latest/apireference/API_ContainerPortConfiguration.html) ├[~] service aws-groundstation │ └ resources │ └[~] resource AWS::GroundStation::DataflowEndpointGroup │ └ properties │ └ EndpointDetails: (documentation changed) ├[~] service aws-kinesisfirehose │ └ resources │ └[~] resource AWS::KinesisFirehose::DeliveryStream │ ├ properties │ │ └ IcebergDestinationConfiguration: - IcebergDestinationConfiguration (immutable) │ │ + IcebergDestinationConfiguration │ └ types │ └[~] type IcebergDestinationConfiguration │ └ properties │ └ CatalogConfiguration: - CatalogConfiguration (required) │ + CatalogConfiguration (required, immutable) ├[~] service aws-paymentcryptography │ └ resources │ └[~] resource AWS::PaymentCryptography::Key │ └ - documentation: Creates an AWS Payment Cryptography key, a logical representation of a cryptographic key, that is unique in your account and AWS Region . You use keys for cryptographic functions such as encryption and decryption. │ In addition to the key material used in cryptographic operations, an AWS Payment Cryptography key includes metadata such as the key ARN, key usage, key origin, creation date, description, and key state. │ When you create a key, you specify both immutable and mutable data about the key. The immutable data contains key attributes that define the scope and cryptographic operations that you can perform using the key, for example key class (example: `SYMMETRIC_KEY` ), key algorithm (example: `TDES_2KEY` ), key usage (example: `TR31_P0_PIN_ENCRYPTION_KEY` ) and key modes of use (example: `Encrypt` ). For information about valid combinations of key attributes, see [Understanding key attributes](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html) in the *AWS Payment Cryptography User Guide* . The mutable data contained within a key includes usage timestamp and key deletion timestamp and can be modified after creation. │ AWS Payment Cryptography binds key attributes to keys using key blocks when you store or export them. AWS Payment Cryptography stores the key contents wrapped and never stores or transmits them in the clear. │ *Cross-account use* : This operation can't be used across different AWS accounts. │ *Related operations:* │ - [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) │ - [GetKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetKey.html) │ - [ListKeys](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListKeys.html) │ + documentation: Creates an AWS Payment Cryptography key, a logical representation of a cryptographic key, that is unique in your account and AWS Region . You use keys for cryptographic functions such as encryption and decryption. │ In addition to the key material used in cryptographic operations, an AWS Payment Cryptography key includes metadata such as the key ARN, key usage, key origin, creation date, description, and key state. │ When you create a key, you specify both immutable and mutable data about the key. The immutable data contains key attributes that define the scope and cryptographic operations that you can perform using the key, for example key class (example: `SYMMETRIC_KEY` ), key algorithm (example: `TDES_2KEY` ), key usage (example: `TR31_P0_PIN_ENCRYPTION_KEY` ) and key modes of use (example: `Encrypt` ). AWS Payment Cryptography binds key attributes to keys using key blocks when you store or export them. AWS Payment Cryptography stores the key contents wrapped and never stores or transmits them in the clear. │ For information about valid combinations of key attributes, see [Understanding key attributes](https://docs.aws.amazon.com/payment-cryptography/latest/userguide/keys-validattributes.html) in the *AWS Payment Cryptography User Guide* . The mutable data contained within a key includes usage timestamp and key deletion timestamp and can be modified after creation. │ You can use the `CreateKey` operation to generate an ECC (Elliptic Curve Cryptography) key pair used for establishing an ECDH (Elliptic Curve Diffie-Hellman) key agreement between two parties. In the ECDH key agreement process, both parties generate their own ECC key pair with key usage K3 and exchange the public keys. Each party then use their private key, the received public key from the other party, and the key derivation parameters including key derivation function, hash algorithm, derivation data, and key algorithm to derive a shared key. │ To maintain the single-use principle of cryptographic keys in payments, ECDH derived keys should not be used for multiple purposes, such as a `TR31_P0_PIN_ENCRYPTION_KEY` and `TR31_K1_KEY_BLOCK_PROTECTION_KEY` . When creating ECC key pairs in AWS Payment Cryptography you can optionally set the `DeriveKeyUsage` parameter, which defines the key usage bound to the symmetric key that will be derived using the ECC key pair. │ *Cross-account use* : This operation can't be used across different AWS accounts. │ *Related operations:* │ - [DeleteKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_DeleteKey.html) │ - [GetKey](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_GetKey.html) │ - [ListKeys](https://docs.aws.amazon.com/payment-cryptography/latest/APIReference/API_ListKeys.html) └[~] service aws-redshiftserverless └ resources └[~] resource AWS::RedshiftServerless::Workgroup └ properties ├[+] RecoveryPointId: string ├[+] SnapshotArn: string ├[+] SnapshotName: string └[+] SnapshotOwnerAccount: string ```
diff --git a/packages/aws-cdk-lib/aws-dsql/.jsiirc.json b/packages/aws-cdk-lib/aws-dsql/.jsiirc.json
@@ -0,0 +1,13 @@
+{
+  "targets": {
+    "java": {
+      "package": "software.amazon.awscdk.services.dsql"
+    },
+    "dotnet": {
+      "package": "Amazon.CDK.AWS.DSQL"
+    },
+    "python": {
+      "module": "aws_cdk.aws_dsql"
+    }
+  }
+}
diff --git a/packages/aws-cdk-lib/aws-dsql/README.md b/packages/aws-cdk-lib/aws-dsql/README.md
@@ -0,0 +1,39 @@
+# AWS::DSQL Construct Library
+<!--BEGIN STABILITY BANNER-->
+
+---
+
+![cfn-resources: Stable](https://img.shields.io/badge/cfn--resources-stable-success.svg?style=for-the-badge)
+
+> All classes with the `Cfn` prefix in this module ([CFN Resources]) are always stable and safe to use.
+>
+> [CFN Resources]: https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib
+
+---
+
+<!--END STABILITY BANNER-->
+
+This module is part of the [AWS Cloud Development Kit](https://github.com/aws/aws-cdk) project.
+
+```ts nofixture
+import * as dsql from 'aws-cdk-lib/aws-dsql';
+```
+
+<!--BEGIN CFNONLY DISCLAIMER-->
+
+There are no official hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. Here are some suggestions on how to proceed:
+
+- Search [Construct Hub for DSQL construct libraries](https://constructs.dev/search?q=dsql)
+- Use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, in the same way you would use [the CloudFormation AWS::DSQL resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_DSQL.html) directly.
+
+
+<!--BEGIN CFNONLY DISCLAIMER-->
+
+There are no hand-written ([L2](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_lib)) constructs for this service yet. 
+However, you can still use the automatically generated [L1](https://docs.aws.amazon.com/cdk/latest/guide/constructs.html#constructs_l1_using) constructs, and use this service exactly as you would using CloudFormation directly.
+
+For more information on the resources and properties available for this service, see the [CloudFormation documentation for AWS::DSQL](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_DSQL.html).
+
+(Read the [CDK Contributing Guide](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and submit an RFC if you are interested in contributing to this construct library.)
+
+<!--END CFNONLY DISCLAIMER-->
diff --git a/packages/aws-cdk-lib/aws-dsql/index.ts b/packages/aws-cdk-lib/aws-dsql/index.ts
@@ -0,0 +1 @@
+export * from './lib';
diff --git a/packages/aws-cdk-lib/aws-dsql/lib/index.ts b/packages/aws-cdk-lib/aws-dsql/lib/index.ts
@@ -0,0 +1,2 @@
+// AWS::DSQL Cloudformation Resources
+export * from './dsql.generated';
diff --git a/packages/aws-cdk-lib/index.ts b/packages/aws-cdk-lib/index.ts
@@ -86,6 +86,7 @@ export * as aws_dlm from './aws-dlm';
 export * as aws_dms from './aws-dms';
 export * as aws_docdb from './aws-docdb';
 export * as aws_docdbelastic from './aws-docdbelastic';
+export * as aws_dsql from './aws-dsql';
 export * as aws_dynamodb from './aws-dynamodb';
 export * as aws_ec2 from './aws-ec2';
 export * as aws_ecr from './aws-ecr';
diff --git a/packages/aws-cdk-lib/package.json b/packages/aws-cdk-lib/package.json
@@ -136,7 +136,7 @@
   },
   "devDependencies": {
     "@aws-cdk/lambda-layer-kubectl-v31": "^2.0.3",
-    "@aws-cdk/aws-service-spec": "^0.1.66",
+    "@aws-cdk/aws-service-spec": "^0.1.67",
     "@aws-cdk/cdk-build-tools": "0.0.0",
     "@aws-cdk/custom-resource-handlers": "0.0.0",
     "@aws-cdk/pkglint": "0.0.0",
@@ -300,6 +300,7 @@
     "./aws-dms": "./aws-dms/index.js",
     "./aws-docdb": "./aws-docdb/index.js",
     "./aws-docdbelastic": "./aws-docdbelastic/index.js",
+    "./aws-dsql": "./aws-dsql/index.js",
     "./aws-dynamodb": "./aws-dynamodb/index.js",
     "./aws-ec2": "./aws-ec2/index.js",
     "./aws-ecr": "./aws-ecr/index.js",
diff --git a/packages/aws-cdk-lib/scripts/scope-map.json b/packages/aws-cdk-lib/scripts/scope-map.json
@@ -233,6 +233,9 @@
   "aws-docdbelastic": [
     "AWS::DocDBElastic"
   ],
+  "aws-dsql": [
+    "AWS::DSQL"
+  ],
   "aws-dynamodb": [
     "AWS::DynamoDB"
   ],
diff --git a/tools/@aws-cdk/spec2cdk/package.json b/tools/@aws-cdk/spec2cdk/package.json
@@ -32,9 +32,9 @@
   },
   "license": "Apache-2.0",
   "dependencies": {
-    "@aws-cdk/aws-service-spec": "^0.1.66",
+    "@aws-cdk/aws-service-spec": "^0.1.67",
     "@aws-cdk/service-spec-importers": "^0.0.75",
-    "@aws-cdk/service-spec-types": "^0.0.132",
+    "@aws-cdk/service-spec-types": "^0.0.133",
     "@cdklabs/tskb": "^0.0.3",
     "@cdklabs/typewriter": "^0.0.5",
     "camelcase": "^6",
diff --git a/yarn.lock b/yarn.lock
@@ -66,12 +66,12 @@
     "@aws-cdk/service-spec-types" "^0.0.128"
     "@cdklabs/tskb" "^0.0.3"
 
-"@aws-cdk/aws-service-spec@^0.1.66":
-  version "0.1.66"
-  resolved "https://registry.npmjs.org/@aws-cdk/aws-service-spec/-/aws-service-spec-0.1.66.tgz#db2f3c3dd3305c1a6d894b41bbc7bfaf9c000224"
-  integrity sha512-ghBGil4pYn9zdQ5SJ0dJnl+v1q4MS7pdUf7D2AphIfWTeSuw/2QscBS9hMbBBHCI6d0THS1jaBiKnRv3+uJECw==
+"@aws-cdk/aws-service-spec@^0.1.67":
+  version "0.1.67"
+  resolved "https://registry.npmjs.org/@aws-cdk/aws-service-spec/-/aws-service-spec-0.1.67.tgz#61c265fe9a1363de473d06b22a72cde8767da00b"
+  integrity sha512-X02ntivyBSPM/V3yfxmWi4DiXKVQ7sAmSkvl5o5mRr4lt4GCIfIsuLyElNSlrRhYm6wAX4HdWDtnbZEaly1e0g==
   dependencies:
-    "@aws-cdk/service-spec-types" "^0.0.132"
+    "@aws-cdk/service-spec-types" "^0.0.133"
     "@cdklabs/tskb" "^0.0.3"
 
 "@aws-cdk/cloud-assembly-schema@^41.0.0":
@@ -147,6 +147,13 @@
   dependencies:
     "@cdklabs/tskb" "^0.0.3"
 
+"@aws-cdk/service-spec-types@^0.0.133":
+  version "0.0.133"
+  resolved "https://registry.npmjs.org/@aws-cdk/service-spec-types/-/service-spec-types-0.0.133.tgz#a2e5a14e9dcd359a67800e9db1c982627f7e189c"
+  integrity sha512-pFcKB8DL02/QCZfSv0KxvIdx9J5606VG9i/wCRtSRBwkFMj152MZEx4GSo3iH3rlcxYd9R+O84Yvv85KtqmwWA==
+  dependencies:
+    "@cdklabs/tskb" "^0.0.3"
+
 "@aws-crypto/crc32@5.2.0":
   version "5.2.0"
   resolved "https://registry.npmjs.org/@aws-crypto/crc32/-/crc32-5.2.0.tgz#cfcc22570949c98c6689cfcbd2d693d36cdae2e1"

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,2 @@`
	`1`	`+// AWS::DSQL Cloudformation Resources`
	`2`	`+export * from './dsql.generated';`