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 (#29798)
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec`
**L1 CloudFormation resource definition changes:**
```
├[~] service aws-amplify
│ └ resources
│ └[~] resource AWS::Amplify::Domain
│ ├ properties
│ │ ├[-] Certificate: Certificate
│ │ └[-] UpdateStatus: string
│ └ attributes
│ ├[+] Certificate: Certificate
│ └[+] UpdateStatus: string
├[~] service aws-appconfig
│ └ resources
│ ├[~] resource AWS::AppConfig::Application
│ │ └ - documentation: The `AWS::AppConfig::Application` resource creates an application. In AWS AppConfig , an application is simply an organizational construct like a folder. This organizational construct has a relationship with some unit of executable code. For example, you could create an application called MyMobileApp to organize and manage configuration data for a mobile application installed by your users.
│ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ - Create an application
│ │ - Create an environment
│ │ - Create a configuration profile
│ │ - Create a deployment strategy
│ │ - Deploy the configuration
│ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ + documentation: The `AWS::AppConfig::Application` resource creates an application. In AWS AppConfig , an application is simply an organizational construct like a folder. This organizational construct has a relationship with some unit of executable code. For example, you could create an application called MyMobileApp to organize and manage configuration data for a mobile application installed by your users.
│ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ - Create an application
│ │ - Create an environment
│ │ - Create a configuration profile
│ │ - Choose a pre-defined deployment strategy or create your own
│ │ - Deploy the configuration
│ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ ├[~] resource AWS::AppConfig::ConfigurationProfile
│ │ ├ - documentation: The `AWS::AppConfig::ConfigurationProfile` resource creates a configuration profile that enables AWS AppConfig to access the configuration source. Valid configuration sources include AWS Systems Manager (SSM) documents, SSM Parameter Store parameters, and Amazon S3 . A configuration profile includes the following information.
│ │ │ - The Uri location of the configuration data.
│ │ │ - The AWS Identity and Access Management ( IAM ) role that provides access to the configuration data.
│ │ │ - A validator for the configuration data. Available validators include either a JSON Schema or the Amazon Resource Name (ARN) of an AWS Lambda function.
│ │ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ │ - Create an application
│ │ │ - Create an environment
│ │ │ - Create a configuration profile
│ │ │ - Create a deployment strategy
│ │ │ - Deploy the configuration
│ │ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ │ + documentation: The `AWS::AppConfig::ConfigurationProfile` resource creates a configuration profile that enables AWS AppConfig to access the configuration source. Valid configuration sources include AWS Systems Manager (SSM) documents, SSM Parameter Store parameters, and Amazon S3 . A configuration profile includes the following information.
│ │ │ - The Uri location of the configuration data.
│ │ │ - The AWS Identity and Access Management ( IAM ) role that provides access to the configuration data.
│ │ │ - A validator for the configuration data. Available validators include either a JSON Schema or the Amazon Resource Name (ARN) of an AWS Lambda function.
│ │ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ │ - Create an application
│ │ │ - Create an environment
│ │ │ - Create a configuration profile
│ │ │ - Choose a pre-defined deployment strategy or create your own
│ │ │ - Deploy the configuration
│ │ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ └ attributes
│ │ └ KmsKeyArn: (documentation changed)
│ ├[~] resource AWS::AppConfig::Deployment
│ │ ├ - documentation: The `AWS::AppConfig::Deployment` resource starts a deployment. Starting a deployment in AWS AppConfig calls the `StartDeployment` API action. This call includes the IDs of the AWS AppConfig application, the environment, the configuration profile, and (optionally) the configuration data version to deploy. The call also includes the ID of the deployment strategy to use, which determines how the configuration data is deployed.
│ │ │ AWS AppConfig monitors the distribution to all hosts and reports status. If a distribution fails, then AWS AppConfig rolls back the configuration.
│ │ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ │ - Create an application
│ │ │ - Create an environment
│ │ │ - Create a configuration profile
│ │ │ - Create a deployment strategy
│ │ │ - Deploy the configuration
│ │ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ │ + documentation: The `AWS::AppConfig::Deployment` resource starts a deployment. Starting a deployment in AWS AppConfig calls the `StartDeployment` API action. This call includes the IDs of the AWS AppConfig application, the environment, the configuration profile, and (optionally) the configuration data version to deploy. The call also includes the ID of the deployment strategy to use, which determines how the configuration data is deployed.
│ │ │ AWS AppConfig monitors the distribution to all hosts and reports status. If a distribution fails, then AWS AppConfig rolls back the configuration.
│ │ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ │ - Create an application
│ │ │ - Create an environment
│ │ │ - Create a configuration profile
│ │ │ - Choose a pre-defined deployment strategy or create your own
│ │ │ - Deploy the configuration
│ │ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ ├ properties
│ │ │ └ DynamicExtensionParameters: (documentation changed)
│ │ └ types
│ │ └[~] type DynamicExtensionParameters
│ │ ├ - documentation: undefined
│ │ │ + documentation: A map of dynamic extension parameter names to values to pass to associated extensions with `PRE_START_DEPLOYMENT` actions.
│ │ └ properties
│ │ ├ ExtensionReference: (documentation changed)
│ │ ├ ParameterName: (documentation changed)
│ │ └ ParameterValue: (documentation changed)
│ ├[~] resource AWS::AppConfig::DeploymentStrategy
│ │ ├ - documentation: The `AWS::AppConfig::DeploymentStrategy` resource creates an AWS AppConfig deployment strategy. A deployment strategy defines important criteria for rolling out your configuration to the designated targets. A deployment strategy includes: the overall duration required, a percentage of targets to receive the deployment during each interval, an algorithm that defines how percentage grows, and bake time.
│ │ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ │ - Create an application
│ │ │ - Create an environment
│ │ │ - Create a configuration profile
│ │ │ - Create a deployment strategy
│ │ │ - Deploy the configuration
│ │ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ │ + documentation: The `AWS::AppConfig::DeploymentStrategy` resource creates an AWS AppConfig deployment strategy. A deployment strategy defines important criteria for rolling out your configuration to the designated targets. A deployment strategy includes: the overall duration required, a percentage of targets to receive the deployment during each interval, an algorithm that defines how percentage grows, and bake time.
│ │ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ │ - Create an application
│ │ │ - Create an environment
│ │ │ - Create a configuration profile
│ │ │ - Choose a pre-defined deployment strategy or create your own
│ │ │ - Deploy the configuration
│ │ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ └ attributes
│ │ └ Id: (documentation changed)
│ ├[~] resource AWS::AppConfig::Environment
│ │ └ - documentation: The `AWS::AppConfig::Environment` resource creates an environment, which is a logical deployment group of AWS AppConfig targets, such as applications in a `Beta` or `Production` environment. You define one or more environments for each AWS AppConfig application. You can also define environments for application subcomponents such as the `Web` , `Mobile` and `Back-end` components for your application. You can configure Amazon CloudWatch alarms for each environment. The system monitors alarms during a configuration deployment. If an alarm is triggered, the system rolls back the configuration.
│ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ - Create an application
│ │ - Create an environment
│ │ - Create a configuration profile
│ │ - Create a deployment strategy
│ │ - Deploy the configuration
│ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ │ + documentation: The `AWS::AppConfig::Environment` resource creates an environment, which is a logical deployment group of AWS AppConfig targets, such as applications in a `Beta` or `Production` environment. You define one or more environments for each AWS AppConfig application. You can also define environments for application subcomponents such as the `Web` , `Mobile` and `Back-end` components for your application. You can configure Amazon CloudWatch alarms for each environment. The system monitors alarms during a configuration deployment. If an alarm is triggered, the system rolls back the configuration.
│ │ AWS AppConfig requires that you create resources and deploy a configuration in the following order:
│ │ - Create an application
│ │ - Create an environment
│ │ - Create a configuration profile
│ │ - Choose a pre-defined deployment strategy or create your own
│ │ - Deploy the configuration
│ │ For more information, see [AWS AppConfig](https://docs.aws.amazon.com/appconfig/latest/userguide/what-is-appconfig.html) in the *AWS AppConfig User Guide* .
│ └[~] resource AWS::AppConfig::Extension
│ └ types
│ └[~] type Action
│ ├ - documentation: An action defines the tasks that the extension performs during the AWS AppConfig workflow. Each action includes an action point such as `ON_CREATE_HOSTED_CONFIGURATION` , `PRE_DEPLOYMENT` , or `ON_DEPLOYMENT` . Each action also includes a name, a URI to an AWS Lambda function, and an Amazon Resource Name (ARN) for an AWS Identity and Access Management assume role. You specify the name, URI, and ARN for each *action point* defined in the extension. You can specify the following actions for an extension:
│ │ - `PRE_CREATE_HOSTED_CONFIGURATION_VERSION`
│ │ - `PRE_START_DEPLOYMENT`
│ │ - `ON_DEPLOYMENT_START`
│ │ - `ON_DEPLOYMENT_STEP`
│ │ - `ON_DEPLOYMENT_BAKING`
│ │ - `ON_DEPLOYMENT_COMPLETE`
│ │ - `ON_DEPLOYMENT_ROLLED_BACK`
│ │ + documentation: The actions defined in the extension.
│ └ properties
│ └ Description: (documentation changed)
├[~] service aws-apprunner
│ └ resources
│ └[~] resource AWS::AppRunner::VpcConnector
│ └ properties
│ └ Tags: (documentation changed)
├[~] service aws-aps
│ └ resources
│ ├[~] resource AWS::APS::RuleGroupsNamespace
│ │ └ properties
│ │ └ Workspace: (documentation changed)
│ └[~] resource AWS::APS::Scraper
│ ├ - documentation: Resource Type definition for AWS::APS::Scraper
│ │ + documentation: A scraper is a fully-managed agentless collector that discovers and pulls metrics automatically. A scraper pulls metrics from Prometheus-compatible sources within an Amazon EKS cluster, and sends them to your Amazon Managed Service for Prometheus workspace. Scrapers are flexible. You can configure the scraper to control what metrics are collected, the frequency of collection, what transformations are applied to the metrics, and more.
│ │ An IAM role will be created for you that Amazon Managed Service for Prometheus uses to access the metrics in your cluster. You must configure this role with a policy that allows it to scrape metrics from your cluster. For more information, see [Configuring your Amazon EKS cluster](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html#AMP-collector-eks-setup) in the *Amazon Managed Service for Prometheus User Guide* .
│ │ The `scrapeConfiguration` parameter contains the YAML configuration for the scraper.
│ │ > For more information about collectors, including what metrics are collected, and how to configure the scraper, see [Using an AWS managed collector](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html) in the *Amazon Managed Service for Prometheus User Guide* .
│ ├ properties
│ │ ├ Alias: (documentation changed)
│ │ ├ Destination: (documentation changed)
│ │ ├ ScrapeConfiguration: (documentation changed)
│ │ ├ Source: (documentation changed)
│ │ └ Tags: (documentation changed)
│ ├ attributes
│ │ ├ Arn: (documentation changed)
│ │ ├ RoleArn: (documentation changed)
│ │ └ ScraperId: (documentation changed)
│ └ types
│ ├[~] type AmpConfiguration
│ │ ├ - documentation: Configuration for Amazon Managed Prometheus metrics destination
│ │ │ + documentation: The `AmpConfiguration` structure defines the Amazon Managed Service for Prometheus instance a scraper should send metrics to.
│ │ └ properties
│ │ └ WorkspaceArn: (documentation changed)
│ ├[~] type Destination
│ │ ├ - documentation: Scraper metrics destination
│ │ │ + documentation: Where to send the metrics from a scraper.
│ │ └ properties
│ │ └ AmpConfiguration: (documentation changed)
│ ├[~] type EksConfiguration
│ │ ├ - documentation: Configuration for EKS metrics source
│ │ │ + documentation: The `EksConfiguration` structure describes the connection to the Amazon EKS cluster from which a scraper collects metrics.
│ │ └ properties
│ │ ├ ClusterArn: (documentation changed)
│ │ ├ SecurityGroupIds: (documentation changed)
│ │ └ SubnetIds: (documentation changed)
│ ├[~] type ScrapeConfiguration
│ │ ├ - documentation: Scraper configuration
│ │ │ + documentation: A scrape configuration for a scraper, base 64 encoded. For more information, see [Scraper configuration](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-collector-how-to.html#AMP-collector-configuration) in the *Amazon Managed Service for Prometheus User Guide* .
│ │ └ properties
│ │ └ ConfigurationBlob: (documentation changed)
│ └[~] type Source
│ ├ - documentation: Scraper metrics source
│ │ + documentation: The source of collected metrics for a scraper.
│ └ properties
│ └ EksConfiguration: (documentation changed)
├[~] service aws-b2bi
│ └ resources
│ ├[~] resource AWS::B2BI::Capability
│ │ └ types
│ │ └[~] type X12Details
│ │ └ properties
│ │ └ Version: (documentation changed)
│ └[~] resource AWS::B2BI::Transformer
│ └ types
│ └[~] type X12Details
│ └ properties
│ └ Version: (documentation changed)
├[~] service aws-backup
│ └ resources
│ ├[~] resource AWS::Backup::BackupVault
│ │ └ properties
│ │ └ BackupVaultTags: (documentation changed)
│ ├[~] resource AWS::Backup::Framework
│ │ └ properties
│ │ └ FrameworkTags: (documentation changed)
│ ├[~] resource AWS::Backup::RestoreTestingPlan
│ │ └ types
│ │ └[~] type RestoreTestingRecoveryPointSelection
│ │ ├ - documentation: Required: Algorithm; Required: Recovery point types; IncludeVaults(one or more). Optional: SelectionWindowDays ('30' if not specified);ExcludeVaults (list of selectors), defaults to empty list if not listed.
│ │ │ + documentation: `RecoveryPointSelection` has five parameters (three required and two optional). The values you specify determine which recovery point is included in the restore test. You must indicate with `Algorithm` if you want the latest recovery point within your `SelectionWindowDays` or if you want a random recovery point, and you must indicate through `IncludeVaults` from which vaults the recovery points can be chosen.
│ │ │ `Algorithm` ( *required* ) Valid values: " `LATEST_WITHIN_WINDOW` " or " `RANDOM_WITHIN_WINDOW` ".
│ │ │ `Recovery point types` ( *required* ) Valid values: " `SNAPSHOT` " and/or " `CONTINUOUS` ". Include `SNAPSHOT` to restore only snapshot recovery points; include `CONTINUOUS` to restore continuous recovery points (point in time restore / PITR); use both to restore either a snapshot or a continuous recovery point. The recovery point will be determined by the value for `Algorithm` .
│ │ │ `IncludeVaults` ( *required* ). You must include one or more backup vaults. Use the wildcard ["*"] or specific ARNs.
│ │ │ `SelectionWindowDays` ( *optional* ) Value must be an integer (in days) from 1 to 365. If not included, the value defaults to `30` .
│ │ │ `ExcludeVaults` ( *optional* ). You can choose to input one or more specific backup vault ARNs to exclude those vaults' contents from restore eligibility. Or, you can include a list of selectors. If this parameter and its value are not included, it defaults to empty list.
│ │ └ properties
│ │ └ RecoveryPointTypes: (documentation changed)
│ └[~] resource AWS::Backup::RestoreTestingSelection
│ └ types
│ └[~] type KeyValue
│ └ properties
│ ├ Key: (documentation changed)
│ └ Value: (documentation changed)
├[~] service aws-batch
│ └ resources
│ └[~] resource AWS::Batch::JobDefinition
│ └ types
│ ├[+] type ImagePullSecret
│ │ ├ name: ImagePullSecret
│ │ └ properties
│ │ └Name: string (required)
│ ├[~] type PodProperties
│ │ └ properties
│ │ └[+] ImagePullSecrets: Array<ImagePullSecret>
│ └[~] type SecurityContext
│ └ properties
│ └[+] AllowPrivilegeEscalation: boolean
├[+] service aws-bcmdataexports
│ ├ capitalized: BCMDataExports
│ │ cloudFormationNamespace: AWS::BCMDataExports
│ │ name: aws-bcmdataexports
│ │ shortName: bcmdataexports
│ └ resources
│ └resource AWS::BCMDataExports::Export
│ ├ name: Export
│ │ cloudFormationType: AWS::BCMDataExports::Export
│ │ documentation: Creates a data export and specifies the data query, the delivery preference, and any optional resource tags.
│ │ A `DataQuery` consists of both a `QueryStatement` and `TableConfigurations` .
│ │ The `QueryStatement` is an SQL statement. Data Exports only supports a limited subset of the SQL syntax. For more information on the SQL syntax that is supported, see [Data query](https://docs.aws.amazon.com/cur/latest/userguide/de-data-query.html) . To view the available tables and columns, see the [Data Exports table dictionary](https://docs.aws.amazon.com/cur/latest/userguide/de-table-dictionary.html) .
│ │ The `TableConfigurations` is a collection of specified `TableProperties` for the table being queried in the `QueryStatement` . TableProperties are additional configurations you can provide to change the data and schema of a table. Each table can have different TableProperties. However, tables are not required to have any TableProperties. Each table property has a default value that it assumes if not specified. For more information on table configurations, see [Data query](https://docs.aws.amazon.com/cur/latest/userguide/de-data-query.html) . To view the table properties available for each table, see the [Data Exports table dictionary](https://docs.aws.amazon.com/cur/latest/userguide/de-table-dictionary.html) or use the `ListTables` API to get a response of all tables and their available properties.
│ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│ ├ properties
│ │ ├Export: Export (required)
│ │ └Tags: Array<ResourceTag>
│ ├ attributes
│ │ └ExportArn: string
│ └ types
│ ├type Export
│ │├ documentation: The details that are available for an export.
│ ││ name: Export
│ │└ properties
│ │ ├ExportArn: string
│ │ ├Name: string (required, immutable)
│ │ ├Description: string
│ │ ├DataQuery: DataQuery (required)
│ │ ├DestinationConfigurations: DestinationConfigurations (required)
│ │ └RefreshCadence: RefreshCadence (required, immutable)
│ ├type DataQuery
│ │├ documentation: The SQL query of column selections and row filters from the data table you want.
│ ││ name: DataQuery
│ │└ properties
│ │ ├QueryStatement: string (required)
│ │ └TableConfigurations: Map<string, Map<string, string>> (immutable)
│ ├type DestinationConfigurations
│ │├ documentation: The destinations used for data exports.
│ ││ name: DestinationConfigurations
│ │└ properties
│ │ └S3Destination: S3Destination (required)
│ ├type S3Destination
│ │├ documentation: Describes the destination Amazon Simple Storage Service (Amazon S3) bucket name and object keys of a data exports file.
│ ││ name: S3Destination
│ │└ properties
│ │ ├S3Bucket: string (required)
│ │ ├S3Prefix: string (required)
│ │ ├S3Region: string (required)
│ │ └S3OutputConfigurations: S3OutputConfigurations (required)
│ ├type S3OutputConfigurations
│ │├ documentation: The compression type, file format, and overwrite preference for the data export.
│ ││ name: S3OutputConfigurations
│ │└ properties
│ │ ├OutputType: string (required)
│ │ ├Format: string (required)
│ │ ├Compression: string (required)
│ │ └Overwrite: string (required)
│ ├type RefreshCadence
│ │├ documentation: The cadence for AWS to update the data export in your S3 bucket.
│ ││ name: RefreshCadence
│ │└ properties
│ │ └Frequency: string (required)
│ └type ResourceTag
│ ├ documentation: The tag structure that contains a tag key and value.
│ │ name: ResourceTag
│ └ properties
│ ├Key: string (required)
│ └Value: string (required)
├[+] service aws-bedrock
│ ├ capitalized: Bedrock
│ │ cloudFormationNamespace: AWS::Bedrock
│ │ name: aws-bedrock
│ │ shortName: bedrock
│ └ resources
│ ├resource AWS::Bedrock::Agent
│ │├ name: Agent
│ ││ cloudFormationType: AWS::Bedrock::Agent
│ ││ documentation: Specifies an agent as a resource in a top-level template. Minimally, you must specify the following properties:
│ ││ - AgentName – Specify a name for the agent.
│ ││ - AgentResourceRoleArn – Specify the Amazon Resource Name (ARN) of the service role with permissions to invoke API operations on the agent. For more information, see [Create a service role for Agents for Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/agents-permissions.html) .
│ ││ - FoundationModel – Specify the model ID of a foundation model to use when invoking the agent. For more information, see [Supported regions and models for Agents for Amazon Bedrock](https://docs.aws.amazon.com//bedrock/latest/userguide/agents-supported.html) .
│ ││ For more information about using agents in Amazon Bedrock , see [Agents for Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/agents.html) .
│ ││ See the *Properties* section below for descriptions of both the required and optional properties.
│ ││ tagInformation: {"tagPropertyName":"Tags","variant":"map"}
│ │├ properties
│ ││ ├ActionGroups: Array<AgentActionGroup>
│ ││ ├AgentName: string (required)
│ ││ ├AgentResourceRoleArn: string
│ ││ ├AutoPrepare: boolean (default=false)
│ ││ ├CustomerEncryptionKeyArn: string
│ ││ ├SkipResourceInUseCheckOnDelete: boolean (default=false)
│ ││ ├Description: string
│ ││ ├FoundationModel: string
│ ││ ├IdleSessionTTLInSeconds: number
│ ││ ├Instruction: string
│ ││ ├KnowledgeBases: Array<AgentKnowledgeBase>
│ ││ ├PromptOverrideConfiguration: PromptOverrideConfiguration
│ ││ └Tags: Map<string, string>
│ │├ attributes
│ ││ ├AgentArn: string
│ ││ ├AgentId: string
│ ││ ├AgentStatus: string
│ ││ ├AgentVersion: string
│ ││ ├CreatedAt: string
│ ││ ├FailureReasons: Array<string>
│ ││ ├PreparedAt: string
│ ││ ├RecommendedActions: Array<string>
│ ││ └UpdatedAt: string
│ │└ types
│ │ ├type AgentActionGroup
│ │ │├ documentation: Contains details about an action group.
│ │ ││ name: AgentActionGroup
│ │ │└ properties
│ │ │ ├ActionGroupName: string (required)
│ │ │ ├Description: string
│ │ │ ├ParentActionGroupSignature: string
│ │ │ ├ActionGroupExecutor: ActionGroupExecutor
│ │ │ ├ApiSchema: APISchema
│ │ │ ├ActionGroupState: string
│ │ │ └SkipResourceInUseCheckOnDelete: boolean (default=false)
│ │ ├type ActionGroupExecutor
│ │ │├ documentation: Contains details about the Lambda function containing the business logic that is carried out upon invoking the action.
│ │ ││ name: ActionGroupExecutor
│ │ │└ properties
│ │ │ └Lambda: string (required)
│ │ ├type APISchema
│ │ │├ documentation: Contains details about the OpenAPI schema for the action group. For more information, see [Action group OpenAPI schemas](https://docs.aws.amazon.com/bedrock/latest/userguide/agents-api-schema.html) . You can either include the schema directly in the `payload` field or you can upload it to an S3 bucket and specify the S3 bucket location in the `s3` field.
│ │ ││ name: APISchema
│ │ │└ properties
│ │ │ ├S3: S3Identifier
│ │ │ └Payload: string
│ │ ├type S3Identifier
│ │ │├ documentation: Contains information about the S3 object containing the resource.
│ │ ││ name: S3Identifier
│ │ │└ properties
│ │ │ ├S3BucketName: string
│ │ │ └S3ObjectKey: string
│ │ ├type AgentKnowledgeBase
│ │ │├ documentation: Contains details about a knowledge base that is associated with an agent.
│ │ ││ name: AgentKnowledgeBase
│ │ │└ properties
│ │ │ ├KnowledgeBaseId: string (required)
│ │ │ ├Description: string (required)
│ │ │ └KnowledgeBaseState: string
│ │ ├type PromptOverrideConfiguration
│ │ │├ documentation: Contains configurations to override prompts in different parts of an agent sequence. For more information, see [Advanced prompts](https://docs.aws.amazon.com/bedrock/latest/userguide/advanced-prompts.html) .
│ │ ││ name: PromptOverrideConfiguration
│ │ │└ properties
│ │ │ ├PromptConfigurations: Array<PromptConfiguration> (required)
│ │ │ └OverrideLambda: string
│ │ ├type PromptConfiguration
│ │ │├ documentation: Contains configurations to override a prompt template in one part of an agent sequence. For more information, see [Advanced prompts](https://docs.aws.amazon.com/bedrock/latest/userguide/advanced-prompts.html) .
│ │ ││ name: PromptConfiguration
│ │ │└ properties
│ │ │ ├PromptType: string
│ │ │ ├PromptCreationMode: string
│ │ │ ├PromptState: string
│ │ │ ├BasePromptTemplate: string
│ │ │ ├InferenceConfiguration: InferenceConfiguration
│ │ │ └ParserMode: string
│ │ └type InferenceConfiguration
│ │ ├ documentation: Contains inference parameters to use when the agent invokes a foundation model in the part of the agent sequence defined by the `promptType` . For more information, see [Inference parameters for foundation models](https://docs.aws.amazon.com/bedrock/latest/userguide/model-parameters.html) .
│ │ │ name: InferenceConfiguration
│ │ └ properties
│ │ ├Temperature: number
│ │ ├TopP: number
│ │ ├TopK: number
│ │ ├MaximumLength: number
│ │ └StopSequences: Array<string>
│ ├resource AWS::Bedrock::AgentAlias
│ │├ name: AgentAlias
│ ││ cloudFormationType: AWS::Bedrock::AgentAlias
│ ││ documentation: Specifies an agent alias as a resource in a top-level template. Minimally, you must specify the following properties:
│ ││ - AgentAliasName – Specify a name for the alias.
│ ││ For more information about creating aliases for an agent in Amazon Bedrock , see [Deploy an Amazon Bedrock agent](https://docs.aws.amazon.com/bedrock/latest/userguide/agents-deploy.html) .
│ ││ See the *Properties* section below for descriptions of both the required and optional properties.
│ ││ tagInformation: {"tagPropertyName":"Tags","variant":"map"}
│ │├ properties
│ ││ ├AgentAliasName: string (required)
│ ││ ├AgentId: string (required, immutable)
│ ││ ├Description: string
│ ││ ├RoutingConfiguration: Array<AgentAliasRoutingConfigurationListItem>
│ ││ └Tags: Map<string, string>
│ │├ attributes
│ ││ ├AgentAliasArn: string
│ ││ ├AgentAliasHistoryEvents: Array<AgentAliasHistoryEvent>
│ ││ ├AgentAliasId: string
│ ││ ├AgentAliasStatus: string
│ ││ ├CreatedAt: string
│ ││ └UpdatedAt: string
│ │└ types
│ │ ├type AgentAliasHistoryEvent
│ │ │├ documentation: Contains details about the history of the alias.
│ │ ││ name: AgentAliasHistoryEvent
│ │ │└ properties
│ │ │ ├RoutingConfiguration: Array<AgentAliasRoutingConfigurationListItem>
│ │ │ ├EndDate: string
│ │ │ └StartDate: string
│ │ └type AgentAliasRoutingConfigurationListItem
│ │ ├ documentation: Contains details about the routing configuration of the alias.
│ │ │ name: AgentAliasRoutingConfigurationListItem
│ │ └ properties
│ │ └AgentVersion: string (required)
│ ├resource AWS::Bedrock::DataSource
│ │├ name: DataSource
│ ││ cloudFormationType: AWS::Bedrock::DataSource
│ ││ documentation: Specifies a data source as a resource in a top-level template. Minimally, you must specify the following properties:
│ ││ - Name – Specify a name for the data source.
│ ││ - KnowledgeBaseId – Specify the ID of the knowledge base for the data source to belong to.
│ ││ - DataSourceConfiguration – Specify information about the Amazon S3 bucket containing the data source. The following sub-properties are required:
│ ││ - Type – Specify the value `S3` .
│ ││ For more information about setting up data sources in Amazon Bedrock , see [Set up a data source for your knowledge base](https://docs.aws.amazon.com/bedrock/latest/userguide/knowledge-base-ds.html) .
│ ││ See the *Properties* section below for descriptions of both the required and optional properties.
│ │├ properties
│ ││ ├DataSourceConfiguration: DataSourceConfiguration (required)
│ ││ ├Description: string
│ ││ ├KnowledgeBaseId: string (required, immutable)
│ ││ ├Name: string (required)
│ ││ ├ServerSideEncryptionConfiguration: ServerSideEncryptionConfiguration
│ ││ └VectorIngestionConfiguration: VectorIngestionConfiguration (immutable)
│ │├ attributes
│ ││ ├DataSourceId: string
│ ││ ├DataSourceStatus: string
│ ││ ├CreatedAt: string
│ ││ └UpdatedAt: string
│ │└ types
│ │ ├type DataSourceConfiguration
│ │ │├ documentation: Contains details about how a data source is stored.
│ │ ││ name: DataSourceConfiguration
│ │ │└ properties
│ │ │ ├Type: string (required)
│ │ │ └S3Configuration: S3DataSourceConfiguration (required)
│ │ ├type S3DataSourceConfiguration
│ │ │├ documentation: Contains information about the S3 configuration of the data source.
│ │ ││ name: S3DataSourceConfiguration
│ │ │└ properties
│ │ │ ├BucketArn: string (required)
│ │ │ └InclusionPrefixes: Array<string>
│ │ ├type ServerSideEncryptionConfiguration
│ │ │├ documentation: Contains the configuration for server-side encryption.
│ │ ││ name: ServerSideEncryptionConfiguration
│ │ │└ properties
│ │ │ └KmsKeyArn: string
│ │ ├type VectorIngestionConfiguration
│ │ │├ documentation: Contains details about how to ingest the documents in a data source.
│ │ ││ name: VectorIngestionConfiguration
│ │ │└ properties
│ │ │ └ChunkingConfiguration: ChunkingConfiguration
│ │ ├type ChunkingConfiguration
│ │ │├ documentation: Details about how to chunk the documents in the data source. A *chunk* refers to an excerpt from a data source that is returned when the knowledge base that it belongs to is queried.
│ │ ││ name: ChunkingConfiguration
│ │ │└ properties
│ │ │ ├ChunkingStrategy: string (required)
│ │ │ └FixedSizeChunkingConfiguration: FixedSizeChunkingConfiguration
│ │ └type FixedSizeChunkingConfiguration
│ │ ├ documentation: Configurations for when you choose fixed-size chunking. If you set the `chunkingStrategy` as `NONE` , exclude this field.
│ │ │ name: FixedSizeChunkingConfiguration
│ │ └ properties
│ │ ├MaxTokens: integer (required)
│ │ └OverlapPercentage: integer (required)
│ └resource AWS::Bedrock::KnowledgeBase
│ ├ name: KnowledgeBase
│ │ cloudFormationType: AWS::Bedrock::KnowledgeBase
│ │ documentation: Specifies a knowledge base as a resource in a top-level template. Minimally, you must specify the following properties:
│ │ - Name – Specify a name for the knowledge base.
│ │ - RoleArn – Specify the Amazon Resource Name (ARN) of the IAM role with permissions to invoke API operations on the knowledge base. For more information, see [Create a service role for Knowledge base for Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/kb-permissions.html) .
│ │ - KnowledgeBaseConfiguration – Specify the embeddings configuration of the knowledge base. The following sub-properties are required:
│ │ - Type – Specify the value `VECTOR` .
│ │ - StorageConfiguration – Specify information about the vector store in which the data source is stored. The following sub-properties are required:
│ │ - Type – Specify the vector store service that you are using.
│ │ > Redis Enterprise Cloud vector stores are currently unsupported in AWS CloudFormation .
│ │ For more information about using knowledge bases in Amazon Bedrock , see [Knowledge base for Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/knowledge-base.html) .
│ │ See the *Properties* section below for descriptions of both the required and optional properties.
│ │ tagInformation: {"tagPropertyName":"Tags","variant":"map"}
│ ├ properties
│ │ ├Description: string
│ │ ├KnowledgeBaseConfiguration: KnowledgeBaseConfiguration (required, immutable)
│ │ ├Name: string (required)
│ │ ├RoleArn: string (required)
│ │ └Tags: Map<string, string>
│ ├ attributes
│ │ ├KnowledgeBaseId: string
│ │ ├KnowledgeBaseArn: string
│ │ ├CreatedAt: string
│ │ ├UpdatedAt: string
│ │ ├FailureReasons: Array<string>
│ │ └Status: string
│ └ types
│ ├type KnowledgeBaseConfiguration
│ │├ documentation: Contains details about the embeddings configuration of the knowledge base.
│ ││ name: KnowledgeBaseConfiguration
│ │└ properties
│ │ ├Type: string (required)
│ │ └VectorKnowledgeBaseConfiguration: VectorKnowledgeBaseConfiguration (required)
│ └type VectorKnowledgeBaseConfiguration
│ ├ documentation: Contains details about the model used to create vector embeddings for the knowledge base.
│ │ name: VectorKnowledgeBaseConfiguration
│ └ properties
│ └EmbeddingModelArn: string (required)
├[~] service aws-chatbot
│ └ resources
│ └[~] resource AWS::Chatbot::MicrosoftTeamsChannelConfiguration
│ └ properties
│ └ TeamsChannelId: (documentation changed)
├[~] service aws-cleanrooms
│ └ resources
│ ├[~] resource AWS::CleanRooms::ConfiguredTable
│ │ └ types
│ │ └[~] type DifferentialPrivacy
│ │ ├ - documentation: undefined
│ │ │ + documentation: The analysis method for the configured tables. The only valid value is currently `DIRECT_QUERY`.
│ │ └ properties
│ │ └ Columns: (documentation changed)
│ └[+] resource AWS::CleanRooms::PrivacyBudgetTemplate
│ ├ name: PrivacyBudgetTemplate
│ │ cloudFormationType: AWS::CleanRooms::PrivacyBudgetTemplate
│ │ documentation: An object that defines the privacy budget template.
│ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│ ├ properties
│ │ ├Tags: Array<tag>
│ │ ├AutoRefresh: string (required, immutable)
│ │ ├PrivacyBudgetType: string (required, immutable)
│ │ ├Parameters: Parameters (required)
│ │ └MembershipIdentifier: string (required, immutable)
│ ├ attributes
│ │ ├CollaborationArn: string
│ │ ├CollaborationIdentifier: string
│ │ ├PrivacyBudgetTemplateIdentifier: string
│ │ ├Arn: string
│ │ └MembershipArn: string
│ └ types
│ └type Parameters
│ ├ documentation: Specifies the epislon and noise parameters for the privacy budget template.
│ │ name: Parameters
│ └ properties
│ ├Epsilon: integer (required)
│ └UsersNoisePerQuery: integer (required)
├[+] service aws-cleanroomsml
│ ├ capitalized: CleanRoomsML
│ │ cloudFormationNamespace: AWS::CleanRoomsML
│ │ name: aws-cleanroomsml
│ │ shortName: cleanroomsml
│ └ resources
│ └resource AWS::CleanRoomsML::TrainingDataset
│ ├ name: TrainingDataset
│ │ cloudFormationType: AWS::CleanRoomsML::TrainingDataset
│ │ documentation: Defines the information necessary to create a training dataset. In Clean Rooms ML, the `TrainingDataset` is metadata that points to a Glue table, which is read only during `AudienceModel` creation.
│ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│ ├ properties
│ │ ├Description: string (immutable)
│ │ ├Name: string (required, immutable)
│ │ ├RoleArn: string (required, immutable)
│ │ ├Tags: Array<tag>
│ │ └TrainingData: Array<Dataset> (required, immutable)
│ ├ attributes
│ │ ├Status: string
│ │ └TrainingDatasetArn: string
│ └ types
│ ├type Dataset
│ │├ documentation: Defines where the training dataset is located, what type of data it contains, and how to access the data.
│ ││ name: Dataset
│ │└ properties
│ │ ├Type: string (required)
│ │ └InputConfig: DatasetInputConfig (required)
│ ├type DatasetInputConfig
│ │├ documentation: Defines the Glue data source and schema mapping information.
│ ││ name: DatasetInputConfig
│ │└ properties
│ │ ├Schema: Array<ColumnSchema> (required)
│ │ └DataSource: DataSource (required)
│ ├type ColumnSchema
│ │├ documentation: Metadata for a column.
│ ││ name: ColumnSchema
│ │└ properties
│ │ ├ColumnName: string (required)
│ │ └ColumnTypes: Array<string> (required)
│ ├type DataSource
│ │├ documentation: Defines information about the Glue data source that contains the training data.
│ ││ name: DataSource
│ │└ properties
│ │ └GlueDataSource: GlueDataSource (required)
│ └type GlueDataSource
│ ├ documentation: Defines the Glue data source that contains the training data.
│ │ name: GlueDataSource
│ └ properties
│ ├TableName: string (required)
│ ├DatabaseName: string (required)
│ └CatalogId: string
├[~] service aws-cloudtrail
│ └ resources
│ ├[~] resource AWS::CloudTrail::EventDataStore
│ │ └ properties
│ │ └ AdvancedEventSelectors: (documentation changed)
│ └[~] resource AWS::CloudTrail::Trail
│ └ properties
│ ├ S3BucketName: (documentation changed)
│ └ S3KeyPrefix: (documentation changed)
├[~] service aws-cloudwatch
│ └ resources
│ ├[~] resource AWS::CloudWatch::Alarm
│ │ ├ - tagInformation: undefined
│ │ │ + tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│ │ └ properties
│ │ └[+] Tags: Array<tag>
│ ├[~] resource AWS::CloudWatch::AnomalyDetector
│ │ └ types
│ │ └[~] type SingleMetricAnomalyDetector
│ │ └ properties
│ │ └ AccountId: (documentation changed)
│ └[~] resource AWS::CloudWatch::CompositeAlarm
│ ├ - documentation: The `AWS::CloudWatch::CompositeAlarm` type creates or updates a composite alarm. When you create a composite alarm, you specify a rule expression for the alarm that takes into account the alarm states of other alarms that you have created. The composite alarm goes into ALARM state only if all conditions of the rule are met.
│ │ The alarms specified in a composite alarm's rule expression can include metric alarms and other composite alarms.
│ │ Using composite alarms can reduce alarm noise. You can create multiple metric alarms, and also create a composite alarm and set up alerts only for the composite alarm. For example, you could create a composite alarm that goes into ALARM state only when more than one of the underlying metric alarms are in ALARM state.
│ │ Currently, the only alarm actions that can be taken by composite alarms are notifying SNS topics.
│ │ When this operation creates an alarm, the alarm state is immediately set to INSUFFICIENT_DATA. The alarm is then evaluated and its state is set appropriately. Any actions associated with the new state are then executed. For a composite alarm, this initial time after creation is the only time that the alarm can be in INSUFFICIENT_DATA state.
│ │ When you update an existing alarm, its state is left unchanged, but the update completely overwrites the previous configuration of the alarm.
│ │ + documentation: The `AWS::CloudWatch::CompositeAlarm` type creates or updates a composite alarm. When you create a composite alarm, you specify a rule expression for the alarm that takes into account the alarm states of other alarms that you have created. The composite alarm goes into ALARM state only if all conditions of the rule are met.
│ │ The alarms specified in a composite alarm's rule expression can include metric alarms and other composite alarms.
│ │ Using composite alarms can reduce alarm noise. You can create multiple metric alarms, and also create a composite alarm and set up alerts only for the composite alarm. For example, you could create a composite alarm that goes into ALARM state only when more than one of the underlying metric alarms are in ALARM state.
│ │ When this operation creates an alarm, the alarm state is immediately set to INSUFFICIENT_DATA. The alarm is then evaluated and its state is set appropriately. Any actions associated with the new state are then executed. For a composite alarm, this initial time after creation is the only time that the alarm can be in INSUFFICIENT_DATA state.
│ │ When you update an existing alarm, its state is left unchanged, but the update completely overwrites the previous configuration of the alarm.
│ │ - tagInformation: undefined
│ │ + tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│ └ properties
│ └[+] Tags: Array<tag>
├[~] service aws-codebuild
│ └ resources
│ ├[~] resource AWS::CodeBuild::Project
│ │ └ types
│ │ ├[~] type Environment
│ │ │ └ properties
│ │ │ └ ComputeType: (documentation changed)
│ │ ├[~] type Source
│ │ │ └ properties
│ │ │ └ Location: (documentation changed)
│ │ └[~] type WebhookFilter
│ │ └ properties
│ │ └ Type: (documentation changed)
│ └[~] resource AWS::CodeBuild::SourceCredential
│ └ properties
│ └ Token: (documentation changed)
├[+] service aws-codeconnections
│ ├ capitalized: CodeConnections
│ │ cloudFormationNamespace: AWS::CodeConnections
│ │ name: aws-codeconnections
│ │ shortName: codeconnections
│ └ resources
│ └resource AWS::CodeConnections::Connection
│ ├ name: Connection
│ │ cloudFormationType: AWS::CodeConnections::Connection
│ │ documentation: A resource that is used to connect third-party source providers with services like CodePipeline.
│ │ Note: A connection created through AWS CloudFormation , the CLI, or the SDK is in `PENDING` status by default. You can make its status `AVAILABLE` by updating the connection in the console.
│ │ tagInformation: {"tagPropertyName":"Tags","variant":"standard"}
│ ├ properties
│ │ ├ConnectionName: string (required, immutable)
│ │ ├ProviderType: string (immutable)
│ │ ├HostArn: string (immutable)
│ │ └Tags: Array<tag>
│ └ attributes
│ ├ConnectionArn: string
│ ├ConnectionStatus: string
│ └OwnerAccountId: string
├[+] service aws-deadline
│ ├ capitalized: Deadline
│ │ cloudFormationNamespace: AWS::Deadline
│ │ name: aws-deadline
│ │ shortName: deadline
│ └ resources
│ ├resource AWS::Deadline::Farm
│ │├ name: Farm
│ ││ cloudFormationType: AWS::Deadline::Farm
│ ││ documentation: Creates a farm to allow space for queues and fleets. Farms are the space where the components of your renders gather and are pieced together in the cloud. Farms contain budgets and allow you to enforce permissions. Deadline Cloud farms are a useful container for large projects.
│ │├ properties
│ ││ ├Description: string (default="")
│ ││ ├DisplayName: string (required)
│ ││ └KmsKeyArn: string (immutable)
│ │└ attributes
│ │ ├FarmId: string
│ │ └Arn: string
│ ├resource AWS::Deadline::Fleet
│ │├ name: Fleet
│ ││ cloudFormationType: AWS::Deadline::Fleet
│ ││ documentation: Creates a fleet. Fleets gather information relating to compute, or capacity, for renders within your farms. You can choose to manage your own capacity or opt to have fleets fully managed by Deadline Cloud.
│ │├ properties
│ ││ ├Configuration: FleetConfiguration (required)
│ ││ ├Description: string (default="")
│ ││ ├DisplayName: string (required)
│ ││ ├FarmId: string (immutable)
│ ││ ├MaxWorkerCount: integer (required)
│ ││ ├MinWorkerCount: integer (default=0)
│ ││ └RoleArn: string (required)
│ │├ attributes
│ ││ ├Capabilities: FleetCapabilities
│ ││ ├FleetId: string
│ ││ ├Status: string
│ ││ ├WorkerCount: integer
│ ││ └Arn: string
│ │└ types
│ │ ├type FleetCapabilities
│ │ │├ documentation: The amounts and attributes of fleets.
│ │ ││ name: FleetCapabilities
│ │ │└ properties
│ │ │ ├Amounts: Array<FleetAmountCapability>
│ │ │ └Attributes: Array<FleetAttributeCapability>
│ │ ├type FleetAmountCapability
│ │ │├ documentation: The fleet amount and attribute capabilities.
│ │ ││ name: FleetAmountCapability
│ │ │└ properties
│ │ │ ├Name: string (required)
│ │ │ ├Min: number (required)
│ │ │ └Max: number
│ │ ├type FleetAttributeCapability
│ │ │├ documentation: Defines the fleet's capability name, minimum, and maximum.
│ │ ││ name: FleetAttributeCapability
│ │ │└ properties
│ │ │ ├Name: string (required)
│ │ │ └Values: Array<string> (required)
│ │ ├type FleetConfiguration
│ │ │├ documentation: Fleet configuration details.
│ │ ││ name: FleetConfiguration
│ │ │└ properties
│ │ │ ├CustomerManaged: CustomerManagedFleetConfiguration
│ │ │ └ServiceManagedEc2: ServiceManagedEc2FleetConfiguration
│ │ ├type CustomerManagedFleetConfiguration
│ │ │├ documentation: The details of a customer managed fleet configuration.
│ │ ││ name: CustomerManagedFleetConfiguration
│ │ │└ properties
│ │ │ ├Mode: string (required)
│ │ │ ├WorkerCapabilities: CustomerManagedWorkerCapabilities (required)
│ │ │ └StorageProfileId: string
│ │ ├type CustomerManagedWorkerCapabilities
│ │ │├ documentation: The worker capabilities for a customer managed workflow.
│ │ ││ name: CustomerManagedWorkerCapabilities
│ │ │└ properties
│ │ │ ├VCpuCount: VCpuCountRange (required)
│ │ │ ├MemoryMiB: MemoryMiBRange (required)
│ │ │ ├AcceleratorTypes: Array<string>
│ │ │ ├AcceleratorCount: AcceleratorCountRange
│ │ │ ├AcceleratorTotalMemoryMiB: AcceleratorTotalMemoryMiBRange
│ │ │ ├OsFamily: string (required)
│ │ │ ├CpuArchitectureType: string (required)
│ │ │ ├CustomAmounts: Array<FleetAmountCapability>
│ │ │ └CustomAttributes: Array<FleetAttributeCapability>
│ │ ├type VCpuCountRange
│ │ │├ documentation: The allowable range of vCPU processing power for the fleet.
│ │ ││ name: VCpuCountRange
│ │ │└ properties
│ │ │ ├Min: integer (required)
│ │ │ └Max: integer
│ │ ├type MemoryMiBRange
│ │ │├ documentation: The range of memory in MiB.
│ │ ││ name: MemoryMiBRange
│ │ │└ properties
│ │ │ ├Min: integer (required)
│ │ │ └Max: integer
│ │ ├type AcceleratorCountRange
│ │ │├ documentation: The range for the GPU fleet acceleration.
│ │ ││ name: AcceleratorCountRange
│ │ │└ properties
│ │ │ ├Min: integer (required)
│ │ │ └Max: integer
│ │ ├type AcceleratorTotalMemoryMiBRange
│ │ │├ documentation: The range for memory, in MiB, to use for the accelerator.
│ │ ││ name: AcceleratorTotalMemoryMiBRange
│ │ │└ properties
│ │ │ ├Min: integer (required)
│ │ │ └Max: integer
│ │ ├type ServiceManagedEc2FleetConfiguration
│ │ │├ documentation: The configuration details for a service managed Amazon EC2 fleet.
│ │ ││ name: ServiceManagedEc2FleetConfiguration
│ │ │└ properties
│ │ │ ├InstanceCapabilities: ServiceManagedEc2InstanceCapabilities (required)
│ │ │ └InstanceMarketOptions: ServiceManagedEc2InstanceMarketOptions (required)
│ │ ├type ServiceManagedEc2InstanceCapabilities
│ │ │├ documentation: The Amazon EC2 instance capabilities.
│ │ ││ name: ServiceManagedEc2InstanceCapabilities
│ │ │└ properties
│ │ │ ├VCpuCount: VCpuCountRange (required)
│ │ │ ├MemoryMiB: MemoryMiBRange (required)
│ │ │ ├OsFamily: string (required)
│ │ │ ├CpuArchitectureType: string (required)
│ │ │ ├RootEbsVolume: Ec2EbsVolume
│ │ │ ├AllowedInstanceTypes: Array<string>
│ │ │ ├ExcludedInstanceTypes: Array<string>
│ │ │ ├CustomAmounts: Array<FleetAmountCapability>
│ │ │ └CustomAttributes: Array<FleetAttributeCapability>
│ │ ├type Ec2EbsVolume
│ │ │├ documentation: Specifies the EBS volume.
│ │ ││ name: Ec2EbsVolume
│ │ │└ properties
│ │ │ ├SizeGiB: integer (default=250)
│ │ │ ├Iops: integer (default=3000)
│ │ │ └ThroughputMiB: integer (default=125)
│ │ └type ServiceManagedEc2InstanceMarketOptions
│ │ ├ documentation: The details of the Amazon EC2 instance market options for a service managed fleet.
│ │ │ name: ServiceManagedEc2InstanceMarketOptions
│ │ └ properties
│ │ └Type: string (required)
│ ├resource AWS::Deadline::LicenseEndpoint
│ │├ name: LicenseEndpoint
│ ││ cloudFormationType: AWS::Deadline::LicenseEndpoint
│ ││ documentation: Creates a license endpoint to integrate your various licensed software used for rendering on Deadline Cloud.
│ │├ properties
│ ││ ├SecurityGroupIds: Array<string> (required, immutable)
│ ││ ├SubnetIds: Array<string> (required, immutable)
│ ││ └VpcId: string (required, immutable)
│ │└ attributes
│ │ ├DnsName: string
│ │ ├LicenseEndpointId: string
│ │ ├Status: string
│ │ ├StatusMessage: string
│ │ └Arn: string
│ ├resource AWS::Deadline::MeteredProduct
│ │├ name: MeteredProduct
│ ││ cloudFormationType: AWS::Deadline::MeteredProduct
│ ││ documentation: Adds a metered product.
│ │├ properties
│ ││ ├LicenseEndpointId: string (immutable)
│ ││ ├ProductId: string (immutable)
│ ││ ├Port: integer
│ ││ ├Family: string
│ ││ └Vendor: string
│ │└ attributes
│ │ └Arn: string
│ ├resource AWS::Deadline::Queue
│ │├ name: Queue
│ ││ cloudFormationType: AWS::Deadline::Queue
│ ││ documentation: Creates a queue to coordinate the order in which jobs run on a farm. A queue can also specify where to pull resources and indicate where to output completed jobs.
│ │├ properties
│ ││ ├AllowedStorageProfileIds: Array<string>
│ ││ ├DefaultBudgetAction: string (default="NONE")
│ ││ ├Description: string (default="")
│ ││ ├DisplayName: string (required)
│ ││ ├FarmId: string (immutable)
│ ││ ├JobAttachmentSettings: JobAttachmentSettings
│ ││ ├JobRunAsUser: JobRunAsUser
│ ││ ├RequiredFileSystemLocationNames: Array<string>
│ ││ └RoleArn: string
│ │├ attributes
│ ││ ├QueueId: string
│ ││ └Arn: string
│ │└ types
│ │ ├type JobAttachmentSettings
│ │ │├ documentation: The job attachment settings. These are the Amazon S3 bucket name and the Amazon S3 prefix.
│ │ ││ name: JobAttachmentSettings
│ │ │└ properties
│ │ │ ├S3BucketName: string (required)
│ │ │ └RootPrefix: string (required)
│ │ ├type JobRunAsUser
│ │ │├ documentation: Identifies the user for a job.
│ │ ││ name: JobRunAsUser
│ │ │└ properties
│ │ │ ├Posix: PosixUser
│ │ │ ├Windows: WindowsUser
│ │ │ └RunAs: string (required)
│ │ ├type PosixUser
│ │ │├ documentation: The POSIX user.
│ │ ││ name: PosixUser
│ │ │└ properties
│ │ │ ├User: string (required)
│ │ │ └Group: string (required)
│ │ └type WindowsUser
│ │ ├ documentation: The Windows user details.
│ │ │ name: WindowsUser
│ │ └ properties
│ │ ├User: string (required)
│ │ └PasswordArn: string (required)
│ ├resource AWS::Deadline::QueueEnvironment
│ │├ name: QueueEnvironment
│ ││ cloudFormationType: AWS::Deadline::QueueEnvironment
│ ││ documentation: Creates an environment for a queue that defines how jobs in the queue run.
│ │├ properties
│ ││ ├FarmId: string (required, immutable)
│ ││ ├Priority: integer (required)
│ ││ ├QueueId: string (required, immutable)
│ ││ ├Template: string (required)
│ ││ └TemplateType: string (required)
│ │└ attributes
│ │ ├Name: string
│ │ └QueueEnvironmentId: string
│ ├resource AWS::Deadline::QueueFleetAssociation
│ │├ name: QueueFleetAssociation
│ ││ cloudFormationType: AWS::Deadline::QueueFleetAssociation
│ ││ documentation: Creates an association between a queue and a fleet.
│ │└ properties
│ │ ├FarmId: string (required, immutable)
│ │ ├FleetId: string (required, immutable)
│ │ └QueueId: string (required, immutable)
│ └resource AWS::Deadline::StorageProfile
│ ├ name: StorageProfile
│ │ cloudFormationType: AWS::Deadline::StorageProfile
│ │ documentation: Creates a storage profile that specifies the operating system, file type, and file location of resources used on a farm.
│ ├ properties
│ │ ├DisplayName: string (required)
│ │ ├FarmId: string (immutable)
│ │ ├FileSystemLocations: Array<FileSystemLocation>
│ │ └OsFamily: string (required)
│ ├ attributes
│ │ └StorageProfileId: string
│ └ types
│ └type FileSystemLocation
│ ├ documentation: The details of the file system location for the resource.
│ │ name: FileSystemLocation
│ └ properties
│ ├Name: string (required)
│ ├Path: string (required)
│ └Type: string (required)
├[~] service aws-ec2
│ └ resources
│ ├[~] resource AWS::EC2::CustomerGateway
│ │ └ properties
│ │ └[+] CertificateArn: string (immutable)
│ ├[~] resource AWS::EC2::Instance
│ │ ├ properties
│ │ │ ├ ElasticGpuSpecifications: (documentation changed)
│ │ │ ├ ElasticInferenceAccelerators: (documentation changed)
│ │ │ └ SubnetId: (documentation changed)
│ │ ├ attributes
│ │ │ └[-] Id: string
│ │ └ types
│ │ ├[~] type LaunchTemplateSpecification
│ │ │ └ - documentation: Specifies a launch template to use when launching an Amazon EC2 instance.
│ │ │ You must specify the following:
│ │ │ - The ID or the name of the launch template, but not both.
│ │ │ - The version of the launch template.
│ │ │ `LaunchTemplateSpecification` is a property of the [AWS::EC2::Instance](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html) resource.
│ │ │ For information about creating a launch template, see [AWS::EC2::LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) and [Create a launch template](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html#create-launch-template) in the *Amazon EC2 User Guide* .
│ │ │ For examples of launch templates, see [Examples](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html#aws-resource-ec2-launchtemplate--examples) .
│ │ │ + documentation: Specifies a launch template to use when launching an Amazon EC2 instance.
│ │ │ You must specify the following:
│ │ │ - The ID or the name of the launch template, but not both.
│ │ │ - The version of the launch template.
│ │ │ For information about creating a launch template, see [AWS::EC2::LaunchTemplate](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html) and [Create a launch template](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-templates.html#create-launch-template) in the *Amazon EC2 User Guide* .
│ │ │ For example launch templates, see the [Examples](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ec2-launchtemplate.html#aws-resource-ec2-launchtemplate--examples) for `AWS::EC2::LaunchTemplate` .
│ │ └[~] type NetworkInterface
│ │ └ properties
│ │ └ SubnetId: (documentation changed)
│ ├[~] resource AWS::EC2::LaunchTemplate
│ │ └ types
│ │ ├[~] type LaunchTemplateData
│ │ │ └ properties
│ │ │ ├ NetworkInterfaces: (documentation changed)
│ │ │ ├ SecurityGroupIds: (documentation changed)
│ │ │ └ SecurityGroups: (documentation changed)
│ │ └[~] type MaintenanceOptions
│ │ └ properties
│ │ └[-] RebootMigration: string
│ ├[~] resource AWS::EC2::SecurityGroup
│ │ ├ - documentation: Specifies a security group. To create a security group, use the [VpcId](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-security-group.html#cfn-ec2-securitygroup-vpcid) property to specify the VPC for which to create the security group.
│ │ │ If you do not specify an egress rule, we add egress rules that allow 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 later remove your egress rules, we restore the default 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. To create a security group, use the [VpcId](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-security-group.html#cfn-ec2-securitygroup-vpcid) property to specify the VPC for which to create the security group.
│ │ │ If you do not specify an egress rule, we add egress rules that allow 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.
│ │ └ types
│ │ └[~] type Egress
│ │ └ properties
│ │ └[-] SourceSecurityGroupId: string
│ ├[~] resource AWS::EC2::SpotFleet
│ │ ├ - documentation: Specifies a Spot Fleet request.
│ │ │ The Spot Fleet request specifies the total target capacity and the On-Demand target capacity. Amazon EC2 calculates the difference between the total capacity and On-Demand capacity, and launches the difference as Spot capacity.
│ │ │ You can submit a single request that includes multiple launch specifications that vary by instance type, AMI, Availability Zone, or subnet.
│ │ │ By default, the Spot Fleet requests Spot Instances in the Spot Instance pool where the price per unit is the lowest. Each launch specification can include its own instance weighting that reflects the value of the instance type to your application workload.
│ │ │ Alternatively, you can specify that the Spot Fleet distribute the target capacity across the Spot pools included in its launch specifications. By ensuring that the Spot Instances in your Spot Fleet are in different Spot pools, you can improve the availability of your fleet.
│ │ │ You can specify tags for the Spot Fleet request and instances launched by the fleet. You cannot tag other resource types in a Spot Fleet request because only the `spot-fleet-request` and `instance` resource types are supported.
│ │ │ For more information, see [Spot Fleet](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html) in the *Amazon EC2 User Guide for Linux Instances* .
│ │ │ > We strongly discourage using the RequestSpotFleet API because it is a legacy API wit…- Loading branch information
1 parent
df019dc
commit 7103fed