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 (#32540)
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::DomainNameV2 │ └ properties │ └[-] ManagementPolicy: json | string ├[~] service aws-applicationautoscaling │ └ resources │ └[~] resource AWS::ApplicationAutoScaling::ScalingPolicy │ └ types │ ├[~] type PredictiveScalingCustomizedLoadMetric │ │ └ properties │ │ └ MetricDataQueries: (documentation changed) │ ├[~] type PredictiveScalingCustomizedScalingMetric │ │ └ - documentation: undefined │ │ + documentation: One or more metric data queries to provide data points for a metric specification. │ └[~] type PredictiveScalingPolicyConfiguration │ └ - documentation: Represents a predictive scaling policy configuration. │ + documentation: Represents a predictive scaling policy configuration. Predictive scaling is supported on Amazon ECS services. ├[~] service aws-batch │ └ resources │ └[~] resource AWS::Batch::JobDefinition │ ├ properties │ │ ├ Parameters: - json │ │ │ + Map<string, string> ⇐ json │ │ ├ Tags: - json (immutable) │ │ │ + Map<string, string> ⇐ json (immutable) │ │ └ Timeout: - Timeout │ │ + JobTimeout ⇐ Timeout │ └ types │ ├[~] type ContainerProperties │ │ └ properties │ │ ├ MountPoints: - Array<MountPoints> │ │ │ + Array<MountPoint> ⇐ Array<MountPoints> │ │ └ Volumes: - Array<Volumes> │ │ + Array<Volume> ⇐ Array<Volumes> │ ├[~] type EcsTaskProperties │ │ └ properties │ │ └ Volumes: - Array<Volumes> │ │ + Array<Volume> ⇐ Array<Volumes> │ ├[+] type EFSAuthorizationConfig │ │ ├ name: EFSAuthorizationConfig │ │ └ properties │ │ ├Iam: string │ │ └AccessPointId: string │ ├[+] type EFSVolumeConfiguration │ │ ├ name: EFSVolumeConfiguration │ │ └ properties │ │ ├TransitEncryption: string │ │ ├AuthorizationConfig: EFSAuthorizationConfig │ │ ├FileSystemId: string (required) │ │ ├RootDirectory: string │ │ └TransitEncryptionPort: integer │ ├[+] type EksMetadata │ │ ├ name: EksMetadata │ │ └ properties │ │ └Labels: Map<string, string> │ ├[+] type EksPodProperties │ │ ├ name: EksPodProperties │ │ └ properties │ │ ├InitContainers: Array<EksContainer> │ │ ├Volumes: Array<EksVolume> │ │ ├DnsPolicy: string │ │ ├Containers: Array<EksContainer> │ │ ├Metadata: EksMetadata │ │ ├ServiceAccountName: string │ │ ├ImagePullSecrets: Array<ImagePullSecret> │ │ ├HostNetwork: boolean │ │ └ShareProcessNamespace: boolean │ ├[~] type EksProperties │ │ └ properties │ │ └ PodProperties: - PodProperties │ │ + EksPodProperties ⇐ PodProperties │ ├[+] type Host │ │ ├ name: Host │ │ └ properties │ │ └SourcePath: string │ ├[~] type ImagePullSecret │ │ └ properties │ │ └ Name: - string (required) │ │ + string │ ├[+] type JobTimeout │ │ ├ name: JobTimeout │ │ └ properties │ │ └AttemptDurationSeconds: integer │ ├[~] type LogConfiguration │ │ └ properties │ │ └ Options: - json │ │ + Map<string, string> ⇐ json │ ├[+] type MountPoint │ │ ├ name: MountPoint │ │ └ properties │ │ ├ReadOnly: boolean │ │ ├SourceVolume: string │ │ └ContainerPath: string │ ├[+] type MultiNodeContainerProperties │ │ ├ name: MultiNodeContainerProperties │ │ └ properties │ │ ├RepositoryCredentials: RepositoryCredentials │ │ ├User: string │ │ ├Secrets: Array<Secret> │ │ ├Memory: integer │ │ ├Privileged: boolean │ │ ├LinuxParameters: LinuxParameters │ │ ├JobRoleArn: string │ │ ├ReadonlyRootFilesystem: boolean │ │ ├Vcpus: integer │ │ ├Image: string (required) │ │ ├ResourceRequirements: Array<ResourceRequirement> │ │ ├LogConfiguration: LogConfiguration │ │ ├MountPoints: Array<MountPoint> │ │ ├ExecutionRoleArn: string │ │ ├RuntimePlatform: RuntimePlatform │ │ ├Volumes: Array<Volume> │ │ ├Command: Array<string> │ │ ├Environment: Array<Environment> │ │ ├Ulimits: Array<Ulimit> │ │ ├InstanceType: string │ │ └EphemeralStorage: EphemeralStorage │ ├[+] type MultiNodeEcsProperties │ │ ├ name: MultiNodeEcsProperties │ │ └ properties │ │ └TaskProperties: Array<MultiNodeEcsTaskProperties> (required) │ ├[+] type MultiNodeEcsTaskProperties │ │ ├ name: MultiNodeEcsTaskProperties │ │ └ properties │ │ ├ExecutionRoleArn: string │ │ ├TaskRoleArn: string │ │ ├IpcMode: string │ │ ├Volumes: Array<Volume> │ │ ├Containers: Array<TaskContainerProperties> │ │ └PidMode: string │ ├[~] type NodeRangeProperty │ │ └ properties │ │ ├ Container: - ContainerProperties │ │ │ + MultiNodeContainerProperties ⇐ ContainerProperties │ │ └ EcsProperties: - EcsProperties │ │ + MultiNodeEcsProperties ⇐ EcsProperties │ ├[~] type Resources │ │ └ properties │ │ ├ Limits: - json │ │ │ + Map<string, string> ⇐ json │ │ └ Requests: - json │ │ + Map<string, string> ⇐ json │ ├[~] type TaskContainerProperties │ │ └ properties │ │ └ MountPoints: - Array<MountPoints> │ │ + Array<MountPoint> ⇐ Array<MountPoints> │ └[+] type Volume │ ├ name: Volume │ └ properties │ ├Host: Host │ ├EfsVolumeConfiguration: EFSVolumeConfiguration │ └Name: string ├[~] service aws-bedrock │ └ resources │ ├[~] resource AWS::Bedrock::DataSource │ │ └ types │ │ ├[~] type BedrockFoundationModelConfiguration │ │ │ └ properties │ │ │ └ ModelArn: (documentation changed) │ │ ├[~] type ParsingConfiguration │ │ │ ├ - documentation: Settings for parsing document contents. By default, the service converts the contents of each document into text before splitting it into chunks. To improve processing of PDF files with tables and images, you can configure the data source to convert the pages of text into images and use a model to describe the contents of each page. │ │ │ │ To use a model to parse PDF documents, set the parsing strategy to `BEDROCK_FOUNDATION_MODEL` and specify the model or [inference profile](https://docs.aws.amazon.com/bedrock/latest/userguide/cross-region-inference.html) to use by ARN. You can also override the default parsing prompt with instructions for how to interpret images and tables in your documents. The following models are supported. │ │ │ │ - Anthropic Claude 3 Sonnet - `anthropic.claude-3-sonnet-20240229-v1:0` │ │ │ │ - Anthropic Claude 3 Haiku - `anthropic.claude-3-haiku-20240307-v1:0` │ │ │ │ You can get the ARN of a model with the [ListFoundationModels](https://docs.aws.amazon.com/bedrock/latest/APIReference/API_ListFoundationModels.html) action. Standard model usage charges apply for the foundation model parsing strategy. │ │ │ │ + documentation: Settings for parsing document contents. If you exclude this field, the default parser converts the contents of each document into text before splitting it into chunks. Specify the parsing strategy to use in the `parsingStrategy` field and include the relevant configuration, or omit it to use the Amazon Bedrock default parser. For more information, see [Parsing options for your data source](https://docs.aws.amazon.com/bedrock/latest/userguide/kb-advanced-parsing.html) . │ │ │ │ > If you specify `BEDROCK_DATA_AUTOMATION` or `BEDROCK_FOUNDATION_MODEL` and it fails to parse a file, the Amazon Bedrock default parser will be used instead. │ │ │ └ properties │ │ │ └ BedrockFoundationModelConfiguration: (documentation changed) │ │ ├[~] type S3Location │ │ │ ├ - documentation: An Amazon S3 location. │ │ │ │ + documentation: A storage location in an S3 bucket. │ │ │ └ properties │ │ │ └ URI: (documentation changed) │ │ └[~] type VectorIngestionConfiguration │ │ └ properties │ │ └ ParsingConfiguration: (documentation changed) │ └[~] resource AWS::Bedrock::Guardrail │ └ types │ └[~] type PiiEntityConfig │ └ properties │ └ Type: (documentation changed) ├[~] service aws-cleanrooms │ └ resources │ └[~] resource AWS::CleanRooms::ConfiguredTable │ └ types │ ├[+] type AthenaTableReference │ │ ├ documentation: A reference to a table within Athena. │ │ │ name: AthenaTableReference │ │ └ properties │ │ ├WorkGroup: string (required) │ │ ├OutputLocation: string │ │ ├DatabaseName: string (required) │ │ └TableName: string (required) │ ├[+] type SnowflakeTableReference │ │ ├ documentation: A reference to a table within Snowflake. │ │ │ name: SnowflakeTableReference │ │ └ properties │ │ ├SecretArn: string (required) │ │ ├AccountIdentifier: string (required) │ │ ├DatabaseName: string (required) │ │ ├TableName: string (required) │ │ ├SchemaName: string (required) │ │ └TableSchema: SnowflakeTableSchema (required) │ ├[+] type SnowflakeTableSchema │ │ ├ documentation: The schema of a Snowflake table. │ │ │ name: SnowflakeTableSchema │ │ └ properties │ │ └V1: Array<SnowflakeTableSchemaV1> (required) │ ├[+] type SnowflakeTableSchemaV1 │ │ ├ documentation: The Snowflake table schema. │ │ │ name: SnowflakeTableSchemaV1 │ │ └ properties │ │ ├ColumnName: string (required) │ │ └ColumnType: string (required) │ └[~] type TableReference │ └ properties │ ├[+] Athena: AthenaTableReference │ ├ Glue: - GlueTableReference (required, immutable) │ │ + GlueTableReference (immutable) │ └[+] Snowflake: SnowflakeTableReference ├[~] service aws-cloudformation │ └ resources │ ├[~] resource AWS::CloudFormation::CustomResource │ │ └ - documentation: In a CloudFormation template, you use the `AWS::CloudFormation::CustomResource` or `Custom:: *String*` resource type to specify custom resources. │ │ Custom resources provide a way for you to write custom provisioning logic in CloudFormation template and have CloudFormation run it during a stack operation, such as when you create, update or delete a stack. For more information, see [Custom resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html) . │ │ > If you use the [VPC endpoints](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html) feature, custom resources in the VPC must have access to CloudFormation -specific Amazon Simple Storage Service ( Amazon S3 ) buckets. Custom resources must send responses to a presigned Amazon S3 URL. If they can't send responses to Amazon S3 , CloudFormation won't receive a response and the stack operation fails. For more information, see [Setting up VPC endpoints for AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-vpce-bucketnames.html) . │ │ + documentation: The `AWS::CloudFormation::CustomResource` resource creates a custom resource. Custom resources provide a way for you to write custom provisioning logic into your CloudFormation templates and have CloudFormation run it anytime you create, update (if you changed the custom resource), or delete a stack. │ │ For more information, see [Create custom provisioning logic with custom resources](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-custom-resources.html) in the *AWS CloudFormation User Guide* . │ │ > If you use AWS PrivateLink , custom resources in the VPC must have access to CloudFormation -specific Amazon S3 buckets. Custom resources must send responses to a presigned Amazon S3 URL. If they can't send responses to Amazon S3 , CloudFormation won't receive a response and the stack operation fails. For more information, see [Access CloudFormation using an interface endpoint ( AWS PrivateLink )](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/vpc-interface-endpoints.html) in the *AWS CloudFormation User Guide* . │ ├[~] resource AWS::CloudFormation::GuardHook │ │ ├ - documentation: The `AWS::CloudFormation::GuardHook` resource creates a Guard Hook with the specified attributes within your CloudFormation template. Using the Guard domain specific language (DSL), you can author Hooks to evaluate your resources before allowing stack creation, modification, or deletion. For more information, see [Guard Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/guard-hooks.html) in the *AWS CloudFormation Hooks User Guide* . │ │ │ + documentation: The `AWS::CloudFormation::GuardHook` resource creates a Guard Hook. Using the Guard domain specific language (DSL), you can author Guard Hooks to evaluate your resources before allowing stack operations. │ │ │ For more information, see [Guard Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/guard-hooks.html) in the *AWS CloudFormation Hooks User Guide* . │ │ └ types │ │ └[~] type TargetFilters │ │ └ - documentation: The `TargetFilters` property type specifies the target filters for the Hook. │ │ For more information, see [AWS CloudFormation Hook target filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/specify-hook-configuration-targetfilters.html) . │ │ + documentation: The `TargetFilters` property type specifies the target filters for the Hook. │ │ For more information, see [AWS CloudFormation Hook target filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-target-filtering.html) . │ ├[~] resource AWS::CloudFormation::HookDefaultVersion │ │ ├ - documentation: The `HookDefaultVersion` resource specifies the default version of the Hook. The default version of the Hook is used in CloudFormation operations for this AWS account and AWS Region . │ │ │ + documentation: The `AWS::CloudFormation::HookDefaultVersion` resource specifies the default version of a Hook. The default version of the Hook is used in CloudFormation operations for this AWS account and AWS Region . │ │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ │ │ This resource type is not compatible with Guard and Lambda Hooks. │ │ └ attributes │ │ └ Arn: (documentation changed) │ ├[~] resource AWS::CloudFormation::HookTypeConfig │ │ ├ - documentation: The `HookTypeConfig` resource specifies the configuration of a Hook. │ │ │ + documentation: The `AWS::CloudFormation::HookTypeConfig` resource specifies the configuration of an activated Hook. │ │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ │ └ properties │ │ └ ConfigurationAlias: (documentation changed) │ ├[~] resource AWS::CloudFormation::HookVersion │ │ ├ - documentation: The `HookVersion` resource publishes new or first Hook version to the AWS CloudFormation registry. │ │ │ + documentation: The `AWS::CloudFormation::HookVersion` resource publishes new or first version of a Hook to the CloudFormation registry. │ │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ │ │ This resource type is not compatible with Guard and Lambda Hooks. │ │ ├ properties │ │ │ └ SchemaHandlerPackage: (documentation changed) │ │ └ attributes │ │ └ Visibility: (documentation changed) │ ├[~] resource AWS::CloudFormation::LambdaHook │ │ ├ - documentation: The `AWS::CloudFormation::LambdaHook` resource creates a Lambda Hook with the specified attributes within your CloudFormation template. You can use a Lambda Hook to evaluate your resources before allowing stack creation, modification, or deletion. This resource forwards requests for resource evaluation to a Lambda function. For more information, see [Lambda Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/lambda-hooks.html) in the *AWS CloudFormation Hooks User Guide* . │ │ │ + documentation: The `AWS::CloudFormation::LambdaHook` resource creates a Lambda Hook. You can use a Lambda Hook to evaluate your resources before allowing stack operations. This resource forwards requests for resource evaluation to a Lambda function. │ │ │ For more information, see [Lambda Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/lambda-hooks.html) in the *AWS CloudFormation Hooks User Guide* . │ │ └ types │ │ └[~] type TargetFilters │ │ └ - documentation: The `TargetFilters` property type specifies the target filters for the Hook. │ │ For more information, see [AWS CloudFormation Hook target filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/specify-hook-configuration-targetfilters.html) . │ │ + documentation: The `TargetFilters` property type specifies the target filters for the Hook. │ │ For more information, see [AWS CloudFormation Hook target filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-target-filtering.html) . │ ├[~] resource AWS::CloudFormation::Macro │ │ ├ - documentation: The `AWS::CloudFormation::Macro` resource is a CloudFormation resource type that creates a CloudFormation macro to perform custom processing on CloudFormation templates. For more information, see [Using AWS CloudFormation macros to perform custom processing on templates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-macros.html) . │ │ │ + documentation: The `AWS::CloudFormation::Macro` resource is a CloudFormation resource type that creates a CloudFormation macro to perform custom processing on CloudFormation templates. │ │ │ For more information, see [Perform custom processing on CloudFormation templates with template macros](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-macros.html) in the *AWS CloudFormation User Guide* . │ │ └ properties │ │ ├ FunctionName: (documentation changed) │ │ ├ LogGroupName: (documentation changed) │ │ └ LogRoleARN: (documentation changed) │ ├[~] resource AWS::CloudFormation::ModuleDefaultVersion │ │ └ - documentation: Specifies the default version of a module. The default version of the module will be used in CloudFormation operations for this account and Region. │ │ To register a module version, use the `[`AWS::CloudFormation::ModuleVersion`](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudformation-moduleversion.html)` resource. │ │ For more information using modules, see [Using modules to encapsulate and reuse resource configurations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/modules.html) and [Registering extensions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html#registry-register) in the *AWS CloudFormation User Guide* . For information on developing modules, see [Developing modules](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/modules.html) in the *AWS CloudFormation CLI User Guide* . │ │ + documentation: Specifies the default version of a module. The default version of the module will be used in CloudFormation operations for this account and Region. │ │ For more information, see [Create reusable resource configurations that can be included across templates with CloudFormation modules](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/modules.html) in the *AWS CloudFormation User Guide* . │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ ├[~] resource AWS::CloudFormation::ModuleVersion │ │ ├ - documentation: Registers the specified version of the module with the CloudFormation service. Registering a module makes it available for use in CloudFormation templates in your AWS account and Region. │ │ │ To specify a module version as the default version, use the `[`AWS::CloudFormation::ModuleDefaultVersion`](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudformation-moduledefaultversion.html)` resource. │ │ │ For more information using modules, see [Using modules to encapsulate and reuse resource configurations](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/modules.html) and [Registering extensions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html#registry-register) in the *CloudFormation User Guide* . For information on developing modules, see [Developing modules](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/modules.html) in the *CloudFormation CLI User Guide* . │ │ │ + documentation: The `AWS::CloudFormation::ModuleVersion` resource registers the specified version of the module with the CloudFormation registry. Registering a module makes it available for use in CloudFormation templates in your AWS account and Region. │ │ │ For more information, see [Create reusable resource configurations that can be included across templates with CloudFormation modules](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/modules.html) in the *CloudFormation User Guide* . │ │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ │ ├ properties │ │ │ └ ModulePackage: (documentation changed) │ │ └ attributes │ │ ├ Arn: (documentation changed) │ │ ├ Description: (documentation changed) │ │ ├ IsDefaultVersion: (documentation changed) │ │ ├ Schema: (documentation changed) │ │ ├ TimeCreated: (documentation changed) │ │ └ Visibility: (documentation changed) │ ├[~] resource AWS::CloudFormation::PublicTypeVersion │ │ ├ - documentation: Tests and publishes a registered extension as a public, third-party extension. │ │ │ CloudFormation first tests the extension to make sure it meets all necessary requirements for being published in the CloudFormation registry. If it does, CloudFormation then publishes it to the registry as a public third-party extension in this Region. Public extensions are available for use by all CloudFormation users. │ │ │ - For resource types, testing includes passing all contracts tests defined for the type. │ │ │ - For modules, testing includes determining if the module's model meets all necessary requirements. │ │ │ For more information, see [Testing your public extension prior to publishing](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension.html#publish-extension-testing) in the *CloudFormation CLI User Guide* . │ │ │ If you don't specify a version, CloudFormation uses the default version of the extension in your account and Region for testing. │ │ │ To perform testing, CloudFormation assumes the execution role specified when the type was registered. │ │ │ An extension must have a test status of `PASSED` before it can be published. For more information, see [Publishing extensions to make them available for public use](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/resource-type-publish.html) in the *CloudFormation CLI User Guide* . │ │ │ + documentation: The `AWS::CloudFormation::PublicTypeVersion` resource tests and publishes a registered extension as a public, third-party extension. │ │ │ CloudFormation first tests the extension to make sure it meets all necessary requirements for being published in the CloudFormation registry. If it does, CloudFormation then publishes it to the registry as a public third-party extension in this Region. Public extensions are available for use by all CloudFormation users. │ │ │ - For resource types, testing includes passing all contracts tests defined for the type. │ │ │ - For modules, testing includes determining if the module's model meets all necessary requirements. │ │ │ For more information, see [Testing your public extension prior to publishing](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension.html#publish-extension-testing) in the *AWS CloudFormation Command Line Interface (CLI) User Guide* . │ │ │ If you don't specify a version, CloudFormation uses the default version of the extension in your account and Region for testing. │ │ │ To perform testing, CloudFormation assumes the execution role specified when the type was registered. │ │ │ An extension must have a test status of `PASSED` before it can be published. For more information, see [Publishing extensions to make them available for public use](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension.html) in the *AWS CloudFormation Command Line Interface (CLI) User Guide* . │ │ └ properties │ │ └ LogDeliveryBucket: (documentation changed) │ ├[~] resource AWS::CloudFormation::Publisher │ │ └ - documentation: Registers your account as a publisher of public extensions in the CloudFormation registry. Public extensions are available for use by all CloudFormation users. │ │ For information on requirements for registering as a public extension publisher, see [Registering your account to publish CloudFormation extensions](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension.html#publish-extension-prereqs) in the *CloudFormation CLI User Guide* . │ │ + documentation: The `AWS::CloudFormation::Publisher` resource registers your account as a publisher of public extensions in the CloudFormation registry. Public extensions are available for use by all CloudFormation users. │ │ For information on requirements for registering as a public extension publisher, see [Publishing extensions to make them available for public use](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/publish-extension.htm) in the *AWS CloudFormation Command Line Interface (CLI) User Guide* . │ ├[~] resource AWS::CloudFormation::ResourceDefaultVersion │ │ └ - documentation: Specifies the default version of a resource. The default version of a resource will be used in CloudFormation operations. │ │ + documentation: The `AWS::CloudFormation::ResourceDefaultVersion` resource specifies the default version of a resource. The default version of a resource will be used in CloudFormation operations. │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ ├[~] resource AWS::CloudFormation::ResourceVersion │ │ ├ - documentation: Registers a resource version with the CloudFormation service. Registering a resource version makes it available for use in CloudFormation templates in your AWS account , and includes: │ │ │ - Validating the resource schema. │ │ │ - Determining which handlers, if any, have been specified for the resource. │ │ │ - Making the resource available for use in your account. │ │ │ For more information on how to develop resources and ready them for registration, see [Creating Resource Providers](https://docs.aws.amazon.com/cloudformation-cli/latest/userguide/resource-types.html) in the *CloudFormation CLI User Guide* . │ │ │ You can have a maximum of 50 resource versions registered at a time. This maximum is per account and per Region. │ │ │ + documentation: The `AWS::CloudFormation::ResourceVersion` resource registers a resource version with the CloudFormation registry. Registering a resource version makes it available for use in CloudFormation templates in your AWS account , and includes: │ │ │ - Validating the resource schema. │ │ │ - Determining which handlers, if any, have been specified for the resource. │ │ │ - Making the resource available for use in your account. │ │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ │ │ You can have a maximum of 50 resource versions registered at a time. This maximum is per account and per Region. │ │ ├ properties │ │ │ ├ ExecutionRoleArn: (documentation changed) │ │ │ └ SchemaHandlerPackage: (documentation changed) │ │ └ attributes │ │ ├ Arn: (documentation changed) │ │ ├ IsDefaultVersion: (documentation changed) │ │ ├ TypeArn: (documentation changed) │ │ ├ VersionId: (documentation changed) │ │ └ Visibility: (documentation changed) │ ├[~] resource AWS::CloudFormation::Stack │ │ ├ - documentation: The `AWS::CloudFormation::Stack` resource nests a stack as a resource in a top-level template. │ │ │ You can add output values from a nested stack within the containing template. You use the [GetAtt](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-getatt.html) function with the nested stack's logical name and the name of the output value in the nested stack in the format `Outputs. *NestedStackOutputName*` . │ │ │ > We strongly recommend that updates to nested stacks are run from the parent stack. │ │ │ When you apply template changes to update a top-level stack, CloudFormation updates the top-level stack and initiates an update to its nested stacks. CloudFormation updates the resources of modified nested stacks, but doesn't update the resources of unmodified nested stacks. For more information, see [CloudFormation stack updates](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html) . │ │ │ > You must acknowledge IAM capabilities for nested stacks that contain IAM resources. Also, verify that you have cancel update stack permissions, which is required if an update rolls back. For more information about IAM and CloudFormation , see [Controlling access with AWS Identity and Access Management](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-iam-template.html) . > A subset of `AWS::CloudFormation::Stack` resource type properties listed below are available to customers using AWS CloudFormation , AWS CDK , and AWS Cloud Control API to configure. │ │ │ > │ │ │ > - `NotificationARNs` │ │ │ > - `Parameters` │ │ │ > - `Tags` │ │ │ > - `TemplateURL` │ │ │ > - `TimeoutInMinutes` │ │ │ > │ │ │ > These properties can be configured only when using AWS Cloud Control API . This is because the below properties are set by the parent stack, and thus cannot be configured using AWS CloudFormation or AWS CDK but only AWS Cloud Control API . │ │ │ > │ │ │ > - `Capabilities` │ │ │ > - `Description` │ │ │ > - `DisableRollback` │ │ │ > - `EnableTerminationProtection` │ │ │ > - `RoleARN` │ │ │ > - `StackName` │ │ │ > - `StackPolicyBody` │ │ │ > - `StackPolicyURL` │ │ │ > - `StackStatusReason` │ │ │ > - `TemplateBody` │ │ │ > │ │ │ > Customers that configure `AWS::CloudFormation::Stack` using AWS CloudFormation and AWS CDK can do so for nesting a CloudFormation stack as a resource in their top-level template. │ │ │ > │ │ │ > These read-only properties can be accessed only when using AWS Cloud Control API . │ │ │ > │ │ │ > - `ChangeSetId` │ │ │ > - `CreationTime` │ │ │ > - `LastUpdateTime` │ │ │ > - `Outputs` │ │ │ > - `ParentId` │ │ │ > - `RootId` │ │ │ > - `StackId` │ │ │ > - `StackStatus` │ │ │ + documentation: The `AWS::CloudFormation::Stack` resource nests a stack as a resource in a top-level template. │ │ │ For more information, see [Embed stacks within other stacks using nested stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-nested-stacks.html) in the *AWS CloudFormation User Guide* . │ │ │ You can add output values from a nested stack within the containing template. You use the [GetAtt](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-getatt.html) function with the nested stack's logical name and the name of the output value in the nested stack in the format `Outputs. *NestedStackOutputName*` . │ │ │ We strongly recommend that updates to nested stacks are run from the parent stack. │ │ │ When you apply template changes to update a top-level stack, CloudFormation updates the top-level stack and initiates an update to its nested stacks. CloudFormation updates the resources of modified nested stacks, but doesn't update the resources of unmodified nested stacks. │ │ │ You must acknowledge IAM capabilities for nested stacks that contain IAM resources. Also, verify that you have cancel update stack permissions, which is required if an update rolls back. For more information about IAM and CloudFormation , see [Controlling access with AWS Identity and Access Management](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/control-access-with-iam.html) in the *AWS CloudFormation User Guide* . │ │ │ > A subset of `AWS::CloudFormation::Stack` resource type properties listed below are available to customers using CloudFormation , AWS CDK , and AWS Cloud Control API to configure. │ │ │ > │ │ │ > - `NotificationARNs` │ │ │ > - `Parameters` │ │ │ > - `Tags` │ │ │ > - `TemplateURL` │ │ │ > - `TimeoutInMinutes` │ │ │ > │ │ │ > These properties can be configured only when using AWS Cloud Control API . This is because the below properties are set by the parent stack, and thus cannot be configured using CloudFormation or AWS CDK but only AWS Cloud Control API . │ │ │ > │ │ │ > - `Capabilities` │ │ │ > - `Description` │ │ │ > - `DisableRollback` │ │ │ > - `EnableTerminationProtection` │ │ │ > - `RoleARN` │ │ │ > - `StackName` │ │ │ > - `StackPolicyBody` │ │ │ > - `StackPolicyURL` │ │ │ > - `StackStatusReason` │ │ │ > - `TemplateBody` │ │ │ > │ │ │ > Customers that configure `AWS::CloudFormation::Stack` using CloudFormation and AWS CDK can do so for nesting a CloudFormation stack as a resource in their top-level template. │ │ │ > │ │ │ > These read-only properties can be accessed only when using AWS Cloud Control API . │ │ │ > │ │ │ > - `ChangeSetId` │ │ │ > - `CreationTime` │ │ │ > - `LastUpdateTime` │ │ │ > - `Outputs` │ │ │ > - `ParentId` │ │ │ > - `RootId` │ │ │ > - `StackId` │ │ │ > - `StackStatus` │ │ ├ properties │ │ │ └ TemplateURL: (documentation changed) │ │ └ attributes │ │ ├ ParentId: (documentation changed) │ │ └ RootId: (documentation changed) │ ├[~] resource AWS::CloudFormation::StackSet │ │ ├ - documentation: The `AWS::CloudFormation::StackSet` enables you to provision stacks into AWS accounts and across Regions by using a single CloudFormation template. In the stack set, you specify the template to use, in addition to any parameters and capabilities that the template requires. │ │ │ > Run deployments to nested StackSets from the parent stack, not directly through the StackSet API. │ │ │ + documentation: The `AWS::CloudFormation::StackSet` resource enables you to provision stacks into AWS accounts and across Regions by using a single CloudFormation template. In the stack set, you specify the template to use, in addition to any parameters and capabilities that the template requires. │ │ │ > Run deployments to nested StackSets from the parent stack, not directly through the StackSet API. │ │ ├ properties │ │ │ ├ AdministrationRoleARN: (documentation changed) │ │ │ ├ Capabilities: (documentation changed) │ │ │ ├ ExecutionRoleName: (documentation changed) │ │ │ ├ OperationPreferences: (documentation changed) │ │ │ ├ PermissionModel: (documentation changed) │ │ │ └ TemplateURL: (documentation changed) │ │ └ types │ │ ├[~] type OperationPreferences │ │ │ ├ - documentation: The user-specified preferences for how AWS CloudFormation performs a stack set operation. For more information on maximum concurrent accounts and failure tolerance, see [Stack set operation options](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html#stackset-ops-options) . │ │ │ │ + documentation: The user-specified preferences for how CloudFormation performs a stack set operation. For more information on maximum concurrent accounts and failure tolerance, see [Stack set operation options](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-concepts.html#stackset-ops-options) in the *AWS CloudFormation User Guide* . │ │ │ └ properties │ │ │ ├ FailureToleranceCount: (documentation changed) │ │ │ ├ FailureTolerancePercentage: (documentation changed) │ │ │ └ MaxConcurrentPercentage: (documentation changed) │ │ └[~] type Parameter │ │ └ properties │ │ └ ParameterKey: (documentation changed) │ ├[~] resource AWS::CloudFormation::TypeActivation │ │ ├ - documentation: Activates a public third-party extension, making it available for use in stack templates. Once you have activated a public third-party extension in your account and Region, use [SetTypeConfiguration](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_SetTypeConfiguration.html) to specify configuration properties for the extension. For more information, see [Using public extensions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry-public.html) in the *AWS CloudFormation User Guide* . │ │ │ + documentation: The `AWS::CloudFormation::TypeActivation` resource activates a public third-party extension, making it available for use in stack templates. │ │ │ For information about the CloudFormation registry, see [Managing extensions with the CloudFormation registry](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/registry.html) in the *AWS CloudFormation User Guide* . │ │ └ properties │ │ ├ ExecutionRoleArn: - string (immutable) │ │ │ + string │ │ ├ PublicTypeArn: - string (immutable) │ │ │ + string │ │ ├ PublisherId: - string (immutable) │ │ │ + string │ │ ├ Type: - string (immutable) │ │ │ + string │ │ ├ TypeName: - string (immutable) │ │ │ + string │ │ └ TypeNameAlias: - string (immutable) │ │ + string │ ├[~] resource AWS::CloudFormation::WaitCondition │ │ ├ - documentation: > For Amazon EC2 and Auto Scaling resources, we recommend that you use a `CreationPolicy` attribute instead of wait conditions. Add a CreationPolicy attribute to those resources, and use the cfn-signal helper script to signal when an instance creation process has completed successfully. │ │ │ You can use a wait condition for situations like the following: │ │ │ - To coordinate stack resource creation with configuration actions that are external to the stack creation. │ │ │ - To track the status of a configuration process. │ │ │ For these situations, we recommend that you associate a [CreationPolicy](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-creationpolicy.html) attribute with the wait condition so that you don't have to use a wait condition handle. For more information and an example, see [Creating wait conditions in a template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-waitcondition.html) . If you use a CreationPolicy with a wait condition, don't specify any of the wait condition's properties. │ │ │ > If you use the [VPC endpoints](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints.html) feature, resources in the VPC that respond to wait conditions must have access to CloudFormation , specific Amazon Simple Storage Service ( Amazon S3 ) buckets. Resources must send wait condition responses to a presigned Amazon S3 URL. If they can't send responses to Amazon S3 , CloudFormation won't receive a response and the stack operation fails. For more information, see [Setting up VPC endpoints for AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-vpce-bucketnames.html) . │ │ │ + documentation: The `AWS::CloudFormation::WaitCondition` resource provides a way to coordinate stack resource creation with configuration actions that are external to the stack creation or to track the status of a configuration process. In these situations, we recommend that you associate a `CreationPolicy` attribute with the wait condition instead of using a wait condition handle. For more information and an example, see [CreationPolicy attribute](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-creationpolicy.html) in the *AWS CloudFormation User Guide* . If you use a `CreationPolicy` with a wait condition, don't specify any of the wait condition's properties. │ │ │ > If you use AWS PrivateLink , resources in the VPC that respond to wait conditions must have access to CloudFormation , specific Amazon S3 buckets. Resources must send wait condition responses to a presigned Amazon S3 URL. If they can't send responses to Amazon S3 , CloudFormation won't receive a response and the stack operation fails. For more information, see [Access CloudFormation using an interface endpoint ( AWS PrivateLink )](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/vpc-interface-endpoints.html) in the *AWS CloudFormation User Guide* . > For Amazon EC2 and Auto Scaling resources, we recommend that you use a `CreationPolicy` attribute instead of wait conditions. Add a `CreationPolicy` attribute to those resources, and use the `cfn-signal` helper script to signal when an instance creation process has completed successfully. │ │ └ properties │ │ └ Handle: (documentation changed) │ └[~] resource AWS::CloudFormation::WaitConditionHandle │ └ - documentation: > For Amazon EC2 and Auto Scaling resources, we recommend that you use a `CreationPolicy` attribute instead of wait conditions. Add a `CreationPolicy` attribute to those resources, and use the cfn-signal helper script to signal when an instance creation process has completed successfully. │ > │ > For more information, see [Deploying applications on Amazon EC2 with AWS CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/deploying.applications.html) . │ The `AWS::CloudFormation::WaitConditionHandle` type has no properties. When you reference the `WaitConditionHandle` resource by using the `Ref` function, AWS CloudFormation returns a presigned URL. You pass this URL to applications or scripts that are running on your Amazon EC2 instances to send signals to that URL. An associated `AWS::CloudFormation::WaitCondition` resource checks the URL for the required number of success signals or for a failure signal. │ > Anytime you add a `WaitCondition` resource during a stack update or update a resource with a wait condition, you must associate the wait condition with a new `WaitConditionHandle` resource. Don't reuse an old wait condition handle that has already been defined in the template. If you reuse a wait condition handle, the wait condition might evaluate old signals from a previous create or update stack command. > Updates aren't supported for this resource. │ + documentation: The `AWS::CloudFormation::WaitConditionHandle` type has no properties. When you reference the `WaitConditionHandle` resource by using the `Ref` function, CloudFormation returns a presigned URL. You pass this URL to applications or scripts that are running on your Amazon EC2 instances to send signals to that URL. An associated `AWS::CloudFormation::WaitCondition` resource checks the URL for the required number of success signals or for a failure signal. │ For more information, see [Create wait conditions in a CloudFormation template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-waitcondition.html) in the *AWS CloudFormation User Guide* . │ Anytime you add a `WaitCondition` resource during a stack update or update a resource with a wait condition, you must associate the wait condition with a new `WaitConditionHandle` resource. Don't reuse an old wait condition handle that has already been defined in the template. If you reuse a wait condition handle, the wait condition might evaluate old signals from a previous create or update stack command. │ Updates aren't supported for this resource. ├[~] service aws-cloudfront │ └ resources │ └[~] resource AWS::CloudFront::Distribution │ └ types │ ├[~] type CacheBehavior │ │ └ properties │ │ └[+] GrpcConfig: GrpcConfig │ ├[~] type DefaultCacheBehavior │ │ └ properties │ │ └[+] GrpcConfig: GrpcConfig │ ├[+] type GrpcConfig │ │ ├ name: GrpcConfig │ │ └ properties │ │ └Enabled: boolean (required) │ ├[~] type Logging │ │ └ properties │ │ └ Bucket: - string (required) │ │ + string │ └[~] type OriginGroup │ └ properties │ └[+] SelectionCriteria: string ├[~] service aws-codepipeline │ └ resources │ └[~] resource AWS::CodePipeline::Pipeline │ └ types │ └[~] type ActionTypeId │ └ properties │ └ Category: (documentation changed) ├[~] service aws-cognito │ └ resources │ ├[~] resource AWS::Cognito::ManagedLoginBranding │ │ ├ - documentation: Creates a new set of branding settings for a user pool style and associates it with an app client. This operation is the programmatic option for the creation of a new style in the branding designer. │ │ │ Provides values for UI customization in a `Settings` JSON object and image files in an `Assets` array. To send the JSON object `Document` type parameter in `Settings` , you might need to update to the most recent version of your AWS SDK. │ │ │ This operation has a 2-megabyte request-size limit and include the CSS settings and image assets for your app client. Your branding settings might exceed 2MB in size. Amazon Cognito doesn't require that you pass all parameters in one request and preserves existing style settings that you don't specify. If your request is larger than 2MB, separate it into multiple requests, each with a size smaller than the limit. │ │ │ As a best practice, modify the output of [DescribeManagedLoginBrandingByClient](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_DescribeManagedLoginBrandingByClient.html) into the request parameters for this operation. To get all settings, set `ReturnMergedResources` to `true` . For more information, see [API and SDK operations for managed login branding](https://docs.aws.amazon.com/cognito/latest/developerguide/managed-login-brandingdesigner.html#branding-designer-api) │ │ │ > Amazon Cognito evaluates AWS Identity and Access Management (IAM) policies in requests for this API operation. For this operation, you must use IAM credentials to authorize requests, and you must grant yourself the corresponding IAM permission in a policy. │ │ │ > │ │ │ > **Learn more** - [Signing AWS API Requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-signing.html) │ │ │ > - [Using the Amazon Cognito user pools API and user pool endpoints](https://docs.aws.amazon.com/cognito/latest/developerguide/user-pools-API-operations.html) │ │ │ + documentation: Creates a new set of branding settings for a user pool style and associates it with an app client. This operation is the programmatic option for the creation of a new style in the branding designer. │ │ │ Provides values for UI customization in a `Settings` JSON object and image files in an `Assets` array. To send the JSON object `Document` type parameter in `Settings` , you might need to update to the most recent version of your AWS SDK. │ │ │ This operation has a 2-megabyte request-size limit and include the CSS settings and image assets for your app client. Your branding settings might exceed 2MB in size. Amazon Cognito doesn't require that you pass all parameters in one request and preserves existing style settings that you don't specify. If your request is larger than 2MB, separate it into multiple requests, each with a size smaller than the limit. │ │ │ As a best practice, modify the output of [DescribeManagedLoginBrandingByClient](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_DescribeManagedLoginBrandingByClient.html) into the request parameters for this operation. To get all settings, set `ReturnMergedResources` to `true` . For more information, see [API and SDK operations for managed login branding](https://docs.aws.amazon.com/cognito/latest/developerguide/managed-login-brandingdesigner.html#branding-designer-api) │ │ └ properties │ │ ├ ClientId: (documentation changed) │ │ ├ ReturnMergedResources: (documentation changed) │ │ └ UseCognitoProvidedValues: (documentation changed) │ ├[~] resource AWS::Cognito::UserPool │ │ ├ properties │ │ │ ├ AliasAttributes: (documentation changed) │ │ │ ├ AutoVerifiedAttributes: (documentation changed) │ │ │ ├ DeviceConfiguration: (documentation changed) │ │ │ ├ Schema: (documentation changed) │ │ │ ├ SmsConfiguration: (documentation changed) │ │ │ ├ UsernameConfiguration: (documentation changed) │ │ │ ├ UserPoolName: (documentation changed) │ │ │ ├ WebAuthnRelyingPartyID: (documentation changed) │ │ │ └ WebAuthnUserVerification: (documentation changed) │ │ └ types │ │ ├[~] type AdvancedSecurityAdditionalFlows │ │ │ ├ - documentation: undefined │ │ │ │ + documentation: Advanced security configuration options for additional authentication types in your user pool, including custom authentication. │ │ │ └ properties │ │ │ └ CustomAuthMode: (documentation changed) │ │ ├[~] type Policies │ │ │ └ properties │ │ │ └ SignInPolicy: (documentation changed) │ │ ├[~] type SignInPolicy │ │ │ ├ - documentation: undefined │ │ │ │ + documentation: The policy for allowed types of authentication in a user pool. │ │ │ │ This data type is a request and response parameter of [CreateUserPool](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_CreateUserPool.html) and [UpdateUserPool](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_UpdateUserPool.html) , and a response parameter of [DescribeUserPool](https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_DescribeUserPool.html) . │ │ │ └ properties │ │ │ └ AllowedFirstAuthFactors: (documentation changed) │ │ └[~] type UserPoolAddOns │ │ └ properties │ │ └ AdvancedSecurityAdditionalFlows: (documentation changed) │ ├[~] resource AWS::Cognito::UserPoolClient │ │ └ properties │ │ ├ AllowedOAuthScopes: (documentation changed) │ │ ├ AnalyticsConfiguration: (documentation changed) │ │ ├ CallbackURLs: (documentation changed) │ │ ├ ClientName: (documentation changed) │ │ ├ DefaultRedirectURI: (documentation changed) │ │ ├ GenerateSecret: (documentation changed) │ │ ├ LogoutURLs: (documentation changed) │ │ ├ SupportedIdentityProviders: (documentation changed) │ │ ├ TokenValidityUnits: (documentation changed) │ │ └ UserPoolId: (documentation changed) │ ├[~] resource AWS::Cognito::UserPoolGroup │ │ └ properties │ │ ├ Description: (documentation changed) │ │ ├ GroupName: (documentation changed) │ │ ├ RoleArn: (documentation changed) │ │ └ UserPoolId: (documentation changed) │ ├[~] resource AWS::Cognito::UserPoolIdentityProvider │ │ └ properties │ │ ├ AttributeMapping: (documentation changed) │ │ ├ IdpIdentifiers: (documentation changed) │ │ ├ ProviderName: (documentation changed) │ │ ├ ProviderType: (documentation changed) │ │ └ UserPoolId: (documentation changed) │ ├[~] resource AWS::Cognito::UserPoolResourceServer │ │ └ properties │ │ └ UserPoolId: (documentation changed) │ ├[~] resource AWS::Cognito::UserPoolUICustomizationAttachment │ │ └ properties │ │ └ UserPoolId: (documentation changed) │ ├[~] resource AWS::Cognito::UserPoolUser │ │ └ properties │ │ ├ ClientMetadata: (documentation changed) │ │ ├ DesiredDeliveryMediums: (documentation changed) │ │ ├ ForceAliasCreation: (documentation changed) │ │ ├ MessageAction: (documentation changed) │ │ └ UserPoolId: (documentation changed) │ └[~] resource AWS::Cognito::UserPoolUserToGroupAttachment │ └ properties │ └ UserPoolId: (documentation changed) ├[~] service aws-connect │ └ resources │ ├[~] resource AWS::Connect::Queue │ │ ├ properties │ │ │ └[+] OutboundEmailConfig: OutboundEmailConfig │ │ └ types │ │ └[+] type OutboundEmailConfig │ │ ├ documentation: The outbound email address Id. │ │ │ name: OutboundEmailConfig │ │ └ properties │ │ └OutboundEmailAddressId: string │ ├[~] resource AWS::Connect::Rule │ │ └ types │ │ ├[~] type CreateCaseAction │ │ │ ├ - documentation: The definition for create case action. │ │ │ │ + documentation: undefined │ │ │ └ properties │ │ │ └ TemplateId: (documentation changed) │ │ ├[~] type Field │ │ │ ├ - documentation: The field of the case. │ │ │ │ + documentation: undefined │ │ │ └ properties │ │ │ ├ Id: (documentation changed) │ │ │ └ Value: (documentation changed) │ │ ├[~] type FieldValue │ │ │ └ properties │ │ │ ├ BooleanValue: (documentation changed) │ │ │ ├ DoubleValue: (documentation changed) │ │ │ ├ EmptyValue: (documentation changed) │ │ │ └ StringValue: (documentation changed) │ │ ├[~] type SubmitAutoEvaluationAction │ │ │ ├ - documentation: The definition of submit auto evaluation action. │ │ │ │ + documentation: undefined │ │ │ └ properties │ │ │ └ EvaluationFormArn: (documentation changed) │ │ └[~] type UpdateCaseAction │ │ └ - documentation: The definition for update case action. │ │ + documentation: undefined │ ├[~] resource AWS::Connect::TaskTemplate │ │ └ properties │ │ └[+] SelfAssignContactFlowArn: string │ └[~] resource AWS::Connect::User │ └ types │ └[~] type UserIdentityInfo │ └ properties │ ├ FirstName: (documentation changed) │ └ LastName: (documentation changed) ├[~] service aws-connectcampaignsv2 │ └ resources │ └[~] resource AWS::ConnectCampaignsV2::Campaign │ └ types │ ├[+] type EventTrigger │ │ ├ documentation: The event trigger of the campaign │ │ │ name: EventTrigger │ │ └ properties │ │ └CustomerProfilesDomainArn: string │ └[~] type Source │ └ properties │ ├ CustomerProfilesSegmentArn: - string (required) │ │ + string │ └[+] EventTrigger: EventTrigger ├[~] service aws-ec2 │ └ resources │ ├[~] resource AWS::EC2::Instance │ │ └ properties │ │ └ PropagateTagsToVolumeOnCreation: (documentation changed) │ ├[~] resource AWS::EC2::LaunchTemplate │ │ └ types │ │ ├[-] type BaselinePerformanceFactors │ │ │ ├ documentation: The baseline performance to consider, using an instance family as a baseline reference. The instance family establishes the lowest acceptable level of performance. Amazon EC2 uses this baseline to guide instance type selection, but there is no guarantee that the selected instance types will always exceed the baseline for every application. │ │ │ │ Currently, this parameter only supports CPU performance as a baseline performance factor. For example, specifying `c6i` would use the CPU performance of the `c6i` family as the baseline reference. │ │ │ │ name: BaselinePerformanceFactors │ │ │ └ properties │ │ │ └Cpu: Cpu │ │ ├[-] type ConnectionTrackingSpecification │ │ │ ├ documentation: A security group connection tracking specification that enables you to set the idle timeout for connection tracking on an Elastic network interface. For more information, see [Connection tracking timeouts](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-connection-tracking.html#connection-tracking-timeouts) in the *Amazon EC2 User Guide* . │ │ │ │ name: ConnectionTrackingSpecification │ │ │ └ properties │ │ │ ├UdpTimeout: integer │ │ │ ├TcpEstablishedTimeout: integer │ │ │ └UdpStreamTimeout: integer │ │ ├[-] type Cpu │ │ │ ├ name: Cpu │ │ │ └ properties │ │ │ └References: Array<Reference> │ │ ├[-] type EnaSrdSpecification │ │ │ ├ documentation: ENA Express uses AWS Scalable Reliable Datagram (SRD) technology to increase the maximum bandwidth used per stream and minimize tail latency of network traffic between EC2 instances. With ENA Express, you can communicate between two EC2 instances in the same subnet within the same account, or in different accounts. Both sending and receiving instances must have ENA Express enabled. │ │ │ │ To improve the reliability of network packet delivery, ENA Express reorders network packets on the receiving end by default. However, some UDP-based applications are designed to handle network packets that are out of order to reduce the overhead for packet delivery at the network layer. When ENA Express is enabled, you can specify whether UDP network traffic uses it. │ │ │ │ name: EnaSrdSpecification │ │ │ └ properties │ │ │ ├EnaSrdEnabled: boolean │ │ │ └EnaSrdUdpSpecification: EnaSrdUdpSpecification │ │ ├[-] type EnaSrdUdpSpecification │ │ │ ├ documentation: ENA Express is compatible with both TCP and UDP transport protocols. When it's enabled, TCP traffic automatically uses it. However, some UDP-based applications are designed to handle network packets that are out of order, without a need for retransmission, such as live video broadcasting or other near-real-time applications. For UDP traffic, you can specify whether to use ENA Express, based on your application environment needs. │ │ │ │ name: EnaSrdUdpSpecification │ │ │ └ properties │ │ │ └EnaSrdUdpEnabled: boolean │ │ ├[~] type InstanceRequirements │ │ │ └ properties │ │ │ ├[-] BaselinePerformanceFactors: BaselinePerformanceFactors │ │ │ └[-] MaxSpotPriceAsPercentageOfOptimalOnDemandPrice: integer │ │ ├[~] type NetworkInterface │ │ │ └ properties │ │ │ ├[-] ConnectionTrackingSpecification: ConnectionTrackingSpecification │ │ │ └[-] EnaSrdSpecification: EnaSrdSpecification │ │ └[-] type Reference │ │ ├ name: Reference │ │ └ properties │ │ └InstanceFamily: string │ ├[~] resource AWS::EC2::SecurityGroupIngress │ │ └ properties │ │ └ GroupName: (documentation changed) │ └[~] resource AWS::EC2::SpotFleet │ └ types │ └[~] type InstanceNetworkInterfaceSpecification │ └ properties │ └ SecondaryPrivateIpAddressCount: (documentation changed) ├[~] service aws-ecs │ └ resources │ ├[~] resource AWS::ECS::Service │ │ ├ properties │ │ │ └ CapacityProviderStrategy: (documentation changed) │ │ └ types │ │ └[~] type DeploymentConfiguration │ │ └ properties │ │ ├ MaximumPercent: (documentation changed) │ │ └ MinimumHealthyPercent: (documentation changed) │ ├[~] resource AWS::ECS::TaskDefinition │ │ └ properties │ │ └[+] EnableFaultInjection: boolean (immutable) │ └[~] resource AWS::ECS::TaskSet │ └ types │ └[~] type CapacityProviderStrategyItem │ └ - documentation: The details of a capacity provider strategy. A capacity provider strategy can be set when using the [RunTask](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html) or [CreateCluster](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html) APIs or as the default capacity provider strategy for a cluster with the `CreateCluster` API. │ Only capacity providers that are already associated with a cluster and have an `ACTIVE` or `UPDATING` status can be used in a capacity provider strategy. The [PutClusterCapacityProviders](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html) API is used to associate a capacity provider with a cluster. │ If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the [CreateClusterCapacityProvider](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateClusterCapacityProvider.html) API operation. │ To use a AWS Fargate capacity provider, specify either the `FARGATE` or `FARGATE_SPOT` capacity providers. The AWS Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy. │ With `FARGATE_SPOT` , you can run interruption tolerant tasks at a rate that's discounted compared to the `FARGATE` price. `FARGATE_SPOT` runs tasks on spare compute capacity. When AWS needs the capacity back, your tasks are interrupted with a two-minute warning. `FARGATE_SPOT` supports Linux tasks with the X86_64 architecture on platform version 1.3.0 or later. `FARGATE_SPOT` supports Linux tasks with the ARM64 architecture on platform version 1.4.0 or later. │ A capacity provider strategy may contain a maximum of 6 capacity providers. │ + documentation: The details of a capacity provider strategy. A capacity provider strategy can be set when using the [RunTask](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html) or [CreateCluster](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_CreateCluster.html) APIs or as the default capacity provider strategy for a cluster with the `CreateCluster` API. │ Only capacity providers that are already associated with a cluster and have an `ACTIVE` or `UPDATING` status can be used in a capacity provider strategy. The [PutClusterCapacityProviders](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_PutClusterCapacityProviders.html) API is used to associate a capacity provider with a cluster. │ If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. New Auto Scaling group capacity providers can be created with the [CreateClusterCapacityProvider](https:…
- Loading branch information
1 parent
f42e2cc
commit 2e3b2ac