Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: update L1 CloudFormation resource definitions (#30973)
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-backup │ └ resources │ └[~] resource AWS::Backup::BackupVault │ └ properties │ └ BackupVaultName: (documentation changed) ├[~] service aws-cleanrooms │ └ resources │ └[~] resource AWS::CleanRooms::PrivacyBudgetTemplate │ ├ properties │ │ └ Parameters: (documentation changed) │ └ types │ └[~] type Parameters │ └ - documentation: Specifies the epislon and noise parameters for the privacy budget template. │ + documentation: Specifies the epsilon and noise parameters for the privacy budget template. ├[~] service aws-cloudformation │ └ resources │ └[~] resource AWS::CloudFormation::StackSet │ └ types │ └[~] type DeploymentTargets │ └ properties │ └ AccountFilterType: (documentation changed) ├[~] service aws-cloudfront │ └ resources │ ├[~] resource AWS::CloudFront::ContinuousDeploymentPolicy │ │ └ types │ │ ├[~] type SingleHeaderPolicyConfig │ │ │ ├ - documentation: undefined │ │ │ │ + documentation: Defines a single header policy for a CloudFront distribution. │ │ │ │ > This property is legacy. We recommend that you use [TrafficConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html) and specify the [SingleHeaderConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html#cfn-cloudfront-continuousdeploymentpolicy-trafficconfig-singleheaderconfig) property instead. │ │ │ └ properties │ │ │ ├ Header: (documentation changed) │ │ │ └ Value: (documentation changed) │ │ └[~] type SingleWeightPolicyConfig │ │ ├ - documentation: undefined │ │ │ + documentation: Configure a policy that CloudFront uses to route requests to different origins or use different cache settings, based on the weight assigned to each option. │ │ │ > This property is legacy. We recommend that you use [TrafficConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html) and specify the [SingleWeightConfig](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-continuousdeploymentpolicy-trafficconfig.html#cfn-cloudfront-continuousdeploymentpolicy-trafficconfig-singleweightconfig) property instead. │ │ └ properties │ │ ├ SessionStickinessConfig: (documentation changed) │ │ └ Weight: (documentation changed) │ └[~] resource AWS::CloudFront::Distribution │ └ types │ ├[~] type DistributionConfig │ │ └ properties │ │ ├ CNAMEs: (documentation changed) │ │ ├ CustomOrigin: (documentation changed) │ │ └ S3Origin: (documentation changed) │ ├[~] type LegacyCustomOrigin │ │ ├ - documentation: undefined │ │ │ + documentation: A custom origin. A custom origin is any origin that is *not* an Amazon S3 bucket, with one exception. An Amazon S3 bucket that is [configured with static website hosting](https://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html) *is* a custom origin. │ │ │ > This property is legacy. We recommend that you use [Origin](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-origin.html) instead. │ │ └ properties │ │ ├ DNSName: (documentation changed) │ │ ├ HTTPPort: (documentation changed) │ │ ├ HTTPSPort: (documentation changed) │ │ ├ OriginProtocolPolicy: (documentation changed) │ │ └ OriginSSLProtocols: (documentation changed) │ └[~] type LegacyS3Origin │ ├ - documentation: undefined │ │ + documentation: The origin as an Amazon S3 bucket. │ │ > This property is legacy. We recommend that you use [Origin](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-cloudfront-distribution-origin.html) instead. │ └ properties │ ├ DNSName: (documentation changed) │ └ OriginAccessIdentity: (documentation changed) ├[~] service aws-cloudtrail │ └ resources │ ├[~] resource AWS::CloudTrail::EventDataStore │ │ └ types │ │ └[~] type AdvancedFieldSelector │ │ └ properties │ │ └ Field: (documentation changed) │ └[~] resource AWS::CloudTrail::Trail │ └ types │ └[~] type AdvancedFieldSelector │ └ properties │ └ Field: (documentation changed) ├[~] service aws-ec2 │ └ resources │ └[~] resource AWS::EC2::IPAMPool │ └ properties │ └ Locale: (documentation changed) ├[~] service aws-entityresolution │ └ resources │ ├[~] resource AWS::EntityResolution::IdMappingWorkflow │ │ ├ properties │ │ │ └ IdMappingTechniques: (documentation changed) │ │ └ types │ │ ├[~] type IdMappingTechniques │ │ │ └ - documentation: An object which defines the ID mapping techniques and provider configurations. │ │ │ + documentation: An object which defines the ID mapping technique and any additional configurations. │ │ └[~] type IdMappingWorkflowInputSource │ │ └ properties │ │ ├ InputSourceARN: (documentation changed) │ │ └ Type: (documentation changed) │ ├[~] resource AWS::EntityResolution::IdNamespace │ │ ├ properties │ │ │ └ Type: (documentation changed) │ │ └ types │ │ ├[~] type IdNamespaceIdMappingWorkflowProperties │ │ │ └ - documentation: An object containing `IdMappingType` and `ProviderProperties` . │ │ │ + documentation: An object containing `IdMappingType` , `ProviderProperties` , and `RuleBasedProperties` . │ │ └[~] type IdNamespaceInputSource │ │ └ properties │ │ └ InputSourceARN: (documentation changed) │ ├[~] resource AWS::EntityResolution::MatchingWorkflow │ │ └ types │ │ └[~] type RuleBasedProperties │ │ ├ - documentation: An object which defines the list of matching rules to run and has a field `Rules` , which is a list of rule objects. │ │ │ + documentation: An object which defines the list of matching rules to run in a matching workflow. RuleBasedProperties contain a `Rules` field, which is a list of rule objects. │ │ └ properties │ │ └ AttributeMatchingModel: (documentation changed) │ └[~] resource AWS::EntityResolution::SchemaMapping │ └ types │ └[~] type SchemaInputAttribute │ ├ - documentation: An object containing `FieldName` , `Type` , `GroupName` , `MatchKey` , and `SubType` . │ │ + documentation: An object containing `FieldName` , `Type` , `GroupName` , `MatchKey` , `Hashing` , and `SubType` . │ └ properties │ └ MatchKey: (documentation changed) ├[~] service aws-iam │ └ resources │ ├[~] resource AWS::IAM::ManagedPolicy │ │ └ attributes │ │ ├ AttachmentCount: (documentation changed) │ │ ├ CreateDate: (documentation changed) │ │ ├ DefaultVersionId: (documentation changed) │ │ ├ IsAttachable: (documentation changed) │ │ ├ PermissionsBoundaryUsageCount: (documentation changed) │ │ ├ PolicyId: (documentation changed) │ │ └ UpdateDate: (documentation changed) │ └[~] resource AWS::IAM::OIDCProvider │ └ properties │ └ ThumbprintList: (documentation changed) ├[~] service aws-iotsitewise │ └ resources │ ├[~] resource AWS::IoTSiteWise::AssetModel │ │ └ properties │ │ └ AssetModelName: (documentation changed) │ └[~] resource AWS::IoTSiteWise::Gateway │ └ properties │ └ GatewayName: (documentation changed) ├[~] service aws-mwaa │ └ resources │ └[~] resource AWS::MWAA::Environment │ └ properties │ └ AirflowVersion: (documentation changed) ├[~] service aws-pipes │ └ resources │ └[~] resource AWS::Pipes::Pipe │ └ types │ └[~] type SelfManagedKafkaAccessConfigurationVpc │ └ properties │ └ SecurityGroup: (documentation changed) ├[~] service aws-rds │ └ resources │ ├[~] resource AWS::RDS::DBCluster │ │ ├ - documentation: The `AWS::RDS::DBCluster` resource creates an Amazon Aurora DB cluster or Multi-AZ DB cluster. │ │ │ For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide* . │ │ │ For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide* . │ │ │ > You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported. │ │ │ *Updating DB clusters* │ │ │ When properties labeled " *Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement) " are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster. │ │ │ > We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure: │ │ │ > │ │ │ > - Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance. │ │ │ > - Create a snapshot of the DB cluster. For more information, see [Creating a DB Cluster Snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html) . │ │ │ > - If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the `SnapshotIdentifier` property with the ID of the DB cluster snapshot that you want to use. │ │ │ > │ │ │ > After you restore a DB cluster with a `SnapshotIdentifier` property, you must specify the same `SnapshotIdentifier` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the `SnapshotIdentifier` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified `SnapshotIdentifier` property, and the original DB cluster is deleted. │ │ │ > - Update the stack. │ │ │ Currently, when you are updating the stack for an Aurora Serverless DB cluster, you can't include changes to any other properties when you specify one of the following properties: `PreferredBackupWindow` , `PreferredMaintenanceWindow` , and `Port` . This limitation doesn't apply to provisioned DB clusters. │ │ │ For more information about updating other properties of this resource, see `[ModifyDBCluster](https://docs.aws.amazon.com//AmazonRDS/latest/APIReference/API_ModifyDBCluster.html)` . For more information about updating stacks, see [AWS CloudFormation Stacks Updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ │ *Deleting DB clusters* │ │ │ The default `DeletionPolicy` for `AWS::RDS::DBCluster` resources is `Snapshot` . For more information about how AWS CloudFormation deletes resources, see [DeletionPolicy Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html) . │ │ │ + documentation: The `AWS::RDS::DBCluster` resource creates an Amazon Aurora DB cluster or Multi-AZ DB cluster. │ │ │ For more information about creating an Aurora DB cluster, see [Creating an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.CreateInstance.html) in the *Amazon Aurora User Guide* . │ │ │ For more information about creating a Multi-AZ DB cluster, see [Creating a Multi-AZ DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/create-multi-az-db-cluster.html) in the *Amazon RDS User Guide* . │ │ │ > You can only create this resource in AWS Regions where Amazon Aurora or Multi-AZ DB clusters are supported. │ │ │ *Updating DB clusters* │ │ │ When properties labeled " *Update requires:* [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement) " are updated, AWS CloudFormation first creates a replacement DB cluster, then changes references from other dependent resources to point to the replacement DB cluster, and finally deletes the old DB cluster. │ │ │ > We highly recommend that you take a snapshot of the database before updating the stack. If you don't, you lose the data when AWS CloudFormation replaces your DB cluster. To preserve your data, perform the following procedure: │ │ │ > │ │ │ > - Deactivate any applications that are using the DB cluster so that there's no activity on the DB instance. │ │ │ > - Create a snapshot of the DB cluster. For more information, see [Creating a DB cluster snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_CreateSnapshotCluster.html) . │ │ │ > - If you want to restore your DB cluster using a DB cluster snapshot, modify the updated template with your DB cluster changes and add the `SnapshotIdentifier` property with the ID of the DB cluster snapshot that you want to use. │ │ │ > │ │ │ > After you restore a DB cluster with a `SnapshotIdentifier` property, you must specify the same `SnapshotIdentifier` property for any future updates to the DB cluster. When you specify this property for an update, the DB cluster is not restored from the DB cluster snapshot again, and the data in the database is not changed. However, if you don't specify the `SnapshotIdentifier` property, an empty DB cluster is created, and the original DB cluster is deleted. If you specify a property that is different from the previous snapshot restore property, a new DB cluster is restored from the specified `SnapshotIdentifier` property, and the original DB cluster is deleted. │ │ │ > - Update the stack. │ │ │ Currently, when you are updating the stack for an Aurora Serverless DB cluster, you can't include changes to any other properties when you specify one of the following properties: `PreferredBackupWindow` , `PreferredMaintenanceWindow` , and `Port` . This limitation doesn't apply to provisioned DB clusters. │ │ │ For more information about updating other properties of this resource, see `[ModifyDBCluster](https://docs.aws.amazon.com//AmazonRDS/latest/APIReference/API_ModifyDBCluster.html)` . For more information about updating stacks, see [AWS CloudFormation Stacks Updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ │ *Deleting DB clusters* │ │ │ The default `DeletionPolicy` for `AWS::RDS::DBCluster` resources is `Snapshot` . For more information about how AWS CloudFormation deletes resources, see [DeletionPolicy Attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-deletionpolicy.html) . │ │ └ properties │ │ ├ BacktrackWindow: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBClusterParameterGroup │ │ ├ - documentation: The `AWS::RDS::DBClusterParameterGroup` resource creates a new Amazon RDS DB cluster parameter group. │ │ │ For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide* . │ │ │ > If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting. │ │ │ > │ │ │ > If you apply a change to parameter group associated with a stopped DB cluster, then the update stack waits until the DB cluster is started. │ │ │ + documentation: The `AWS::RDS::DBClusterParameterGroup` resource creates a new Amazon RDS DB cluster parameter group. │ │ │ For information about configuring parameters for Amazon Aurora DB clusters, see [Working with parameter groups](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.html) in the *Amazon Aurora User Guide* . │ │ │ > If you apply a parameter group to a DB cluster, then its DB instances might need to reboot. This can result in an outage while the DB instances are rebooting. │ │ │ > │ │ │ > If you apply a change to parameter group associated with a stopped DB cluster, then the updated stack waits until the DB cluster is started. │ │ └ properties │ │ ├ DBClusterParameterGroupName: (documentation changed) │ │ ├ Description: (documentation changed) │ │ ├ Family: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBInstance │ │ └ properties │ │ ├ DBClusterIdentifier: (documentation changed) │ │ ├ DBSnapshotIdentifier: (documentation changed) │ │ ├ DBSubnetGroupName: (documentation changed) │ │ ├ DeletionProtection: (documentation changed) │ │ ├ MonitoringInterval: (documentation changed) │ │ ├ MultiAZ: (documentation changed) │ │ ├ Port: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBParameterGroup │ │ └ properties │ │ ├ Family: (documentation changed) │ │ ├ Parameters: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBProxy │ │ ├ properties │ │ │ └ EngineFamily: (documentation changed) │ │ ├ attributes │ │ │ ├ DBProxyArn: (documentation changed) │ │ │ └ Endpoint: (documentation changed) │ │ └ types │ │ ├[~] type AuthFormat │ │ │ └ properties │ │ │ ├ AuthScheme: (documentation changed) │ │ │ └ IAMAuth: (documentation changed) │ │ └[~] type TagFormat │ │ ├ - documentation: Metadata assigned to a DB proxy consisting of a key-value pair. │ │ │ + documentation: Metadata assigned to an Amazon RDS resource consisting of a key-value pair. │ │ │ For more information, see [Tagging Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Tagging.html) in the *Amazon RDS User Guide* or [Tagging Amazon Aurora and Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_Tagging.html) in the *Amazon Aurora User Guide* . │ │ └ properties │ │ ├ Key: (documentation changed) │ │ └ Value: (documentation changed) │ ├[~] resource AWS::RDS::DBProxyEndpoint │ │ ├ properties │ │ │ └ TargetRole: (documentation changed) │ │ ├ attributes │ │ │ ├ DBProxyEndpointArn: (documentation changed) │ │ │ ├ Endpoint: (documentation changed) │ │ │ ├ IsDefault: (documentation changed) │ │ │ └ VpcId: (documentation changed) │ │ └ types │ │ └[~] type TagFormat │ │ ├ - documentation: Metadata assigned to a DB proxy endpoint consisting of a key-value pair. │ │ │ + documentation: Metadata assigned to an Amazon RDS resource consisting of a key-value pair. │ │ │ For more information, see [Tagging Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Tagging.html) in the *Amazon RDS User Guide* or [Tagging Amazon Aurora and Amazon RDS Resources](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_Tagging.html) in the *Amazon Aurora User Guide* . │ │ └ properties │ │ ├ Key: (documentation changed) │ │ └ Value: (documentation changed) │ ├[~] resource AWS::RDS::DBProxyTargetGroup │ │ └ properties │ │ └ ConnectionPoolConfigurationInfo: (documentation changed) │ ├[~] resource AWS::RDS::DBSecurityGroup │ │ └ properties │ │ ├ EC2VpcId: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::DBSubnetGroup │ │ └ properties │ │ ├ DBSubnetGroupName: (documentation changed) │ │ └ Tags: (documentation changed) │ ├[~] resource AWS::RDS::EventSubscription │ │ └ properties │ │ ├ SourceIds: (documentation changed) │ │ └ SourceType: (documentation changed) │ ├[~] resource AWS::RDS::Integration │ │ └ properties │ │ └ Tags: (documentation changed) │ └[~] resource AWS::RDS::OptionGroup │ └ properties │ ├ OptionConfigurations: (documentation changed) │ └ Tags: (documentation changed) ├[~] service aws-s3 │ └ resources │ └[~] resource AWS::S3::Bucket │ ├ properties │ │ └ VersioningConfiguration: (documentation changed) │ └ types │ └[~] type VersioningConfiguration │ └ - documentation: Describes the versioning state of an Amazon S3 bucket. For more information, see [PUT Bucket versioning](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTVersioningStatus.html) in the *Amazon S3 API Reference* . │ + documentation: Describes the versioning state of an Amazon S3 bucket. For more information, see [PUT Bucket versioning](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTVersioningStatus.html) in the *Amazon S3 API Reference* . │ > When you enable versioning on a bucket for the first time, it might take a short amount of time for the change to be fully propagated. We recommend that you wait for 15 minutes after enabling versioning before issuing write operations ( `PUT` or `DELETE` ) on objects in the bucket. └[~] service aws-stepfunctions └ resources └[~] resource AWS::StepFunctions::StateMachineAlias └ types └[~] type DeploymentPreference └ properties └ Alarms: (documentation changed) ```
- Loading branch information
1 parent
439feaf
commit 63c45e4