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 (aws#33579)
Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec` **L1 CloudFormation resource definition changes:** ``` ├[~] service aws-bedrock │ └ resources │ └[~] resource AWS::Bedrock::Agent │ ├ properties │ │ ├[+] AgentCollaboration: string │ │ ├[+] AgentCollaborators: Array<AgentCollaborator> │ │ ├[+] CustomOrchestration: CustomOrchestration │ │ ├[+] MemoryConfiguration: MemoryConfiguration │ │ └[+] OrchestrationType: string │ └ types │ ├[+] type AgentCollaborator │ │ ├ documentation: An agent collaborator. │ │ │ name: AgentCollaborator │ │ └ properties │ │ ├ AgentDescriptor: AgentDescriptor (required) │ │ ├ CollaborationInstruction: string (required) │ │ ├ CollaboratorName: string (required) │ │ └ RelayConversationHistory: string │ ├[+] type AgentDescriptor │ │ ├ documentation: An agent descriptor. │ │ │ name: AgentDescriptor │ │ └ properties │ │ └ AliasArn: string │ ├[+] type CustomOrchestration │ │ ├ documentation: Details of custom orchestration. │ │ │ name: CustomOrchestration │ │ └ properties │ │ └ Executor: OrchestrationExecutor │ ├[+] type MemoryConfiguration │ │ ├ documentation: Details of the memory configuration. │ │ │ name: MemoryConfiguration │ │ └ properties │ │ ├ EnabledMemoryTypes: Array<string> │ │ ├ StorageDays: number │ │ └ SessionSummaryConfiguration: SessionSummaryConfiguration │ ├[+] type OrchestrationExecutor │ │ ├ documentation: Contains details about the Lambda function containing the orchestration logic carried out upon invoking the custom orchestration. │ │ │ name: OrchestrationExecutor │ │ └ properties │ │ └ Lambda: string (required) │ ├[~] type PromptConfiguration │ │ └ properties │ │ └[+] FoundationModel: string │ └[+] type SessionSummaryConfiguration │ ├ documentation: Configuration for SESSION_SUMMARY memory type enabled for the agent. │ │ name: SessionSummaryConfiguration │ └ properties │ └ MaxRecentSessions: number ├[~] service aws-chatbot │ └ resources │ ├[~] resource AWS::Chatbot::CustomAction │ │ ├ - documentation: The `AWS::Chatbot::CustomAction` resource creates a custom action that can be invoked as an alias or as a button on a notification. │ │ │ + documentation: > AWS Chatbot is now . [Learn more](https://docs.aws.amazon.com//chatbot/latest/adminguide/service-rename.html) │ │ │ > │ │ │ > `Type` attribute values remain unchanged. │ │ ├ properties │ │ │ └ AliasName: (documentation changed) │ │ └ types │ │ ├[~] type CustomActionAttachment │ │ │ └ - documentation: Defines when a custom action button should be attached to a notification. │ │ │ + documentation: > AWS Chatbot is now . [Learn more](https://docs.aws.amazon.com//chatbot/latest/adminguide/service-rename.html) │ │ │ > │ │ │ > `Type` attribute values remain unchanged. │ │ │ Defines when a custom action button should be attached to a notification. │ │ ├[~] type CustomActionAttachmentCriteria │ │ │ └ - documentation: A criteria for when a button should be shown based on values in the notification. │ │ │ + documentation: > AWS Chatbot is now . [Learn more](https://docs.aws.amazon.com//chatbot/latest/adminguide/service-rename.html) │ │ │ > │ │ │ > `Type` attribute values remain unchanged. │ │ │ A criteria for when a button should be shown based on values in the notification. │ │ └[~] type CustomActionDefinition │ │ └ - documentation: The definition of the command to run when invoked as an alias or as an action button. │ │ + documentation: > AWS Chatbot is now . [Learn more](https://docs.aws.amazon.com//chatbot/latest/adminguide/service-rename.html) │ │ > │ │ > `Type` attribute values remain unchanged. │ │ The definition of the command to run when invoked as an alias or as an action button. │ ├[~] resource AWS::Chatbot::MicrosoftTeamsChannelConfiguration │ │ ├ - documentation: The `AWS::Chatbot::MicrosoftTeamsChannelConfiguration` resource configures a Microsoft Teams channel to allow users to use AWS Chatbot with AWS CloudFormation templates. │ │ │ This resource requires some setup to be done in the AWS Chatbot console. To provide the required Microsoft Teams team and tenant IDs, you must perform the initial authorization flow with Microsoft Teams in the AWS Chatbot console, then copy and paste the IDs from the console. For more details, see [Configure a Microsoft Teams client](https://docs.aws.amazon.com/chatbot/latest/adminguide/teams-setup.html#teams-client-setup) in the *AWS Chatbot Administrator Guide* . │ │ │ + documentation: > AWS Chatbot is now . [Learn more](https://docs.aws.amazon.com//chatbot/latest/adminguide/service-rename.html) │ │ │ > │ │ │ > `Type` attribute values remain unchanged. │ │ │ The `AWS::Chatbot::MicrosoftTeamsChannelConfiguration` resource configures a Microsoft Teams channel to allow users to use with AWS CloudFormation templates. │ │ │ This resource requires some setup to be done in the in chat applications console. To provide the required Microsoft Teams team and tenant IDs, you must perform the initial authorization flow with Microsoft Teams in the in chat applications console, then copy and paste the IDs from the console. For more details, see steps 1-3 in [Get started with Microsoft Teams](https://docs.aws.amazon.com/chatbot/latest/adminguide/teams-setup.html#teams-client-setup) in the *in chat applications Administrator Guide* . │ │ └ properties │ │ ├ CustomizationResourceArns: (documentation changed) │ │ ├ IamRoleArn: (documentation changed) │ │ ├ SnsTopicArns: (documentation changed) │ │ ├ TeamId: (documentation changed) │ │ ├ TeamsChannelId: (documentation changed) │ │ └ TeamsTenantId: (documentation changed) │ └[~] resource AWS::Chatbot::SlackChannelConfiguration │ ├ - documentation: The `AWS::Chatbot::SlackChannelConfiguration` resource configures a Slack channel to allow users to use AWS Chatbot with AWS CloudFormation templates. │ │ This resource requires some setup to be done in the AWS Chatbot console. To provide the required Slack workspace ID, you must perform the initial authorization flow with Slack in the AWS Chatbot console, then copy and paste the workspace ID from the console. For more details, see [Configure a Slack client](https://docs.aws.amazon.com/chatbot/latest/adminguide/slack-setup.html#slack-client-setup) in the *AWS Chatbot User Guide* . │ │ + documentation: > AWS Chatbot is now . [Learn more](https://docs.aws.amazon.com//chatbot/latest/adminguide/service-rename.html) │ │ > │ │ > `Type` attribute values remain unchanged. │ │ The `AWS::Chatbot::SlackChannelConfiguration` resource configures a Slack channel to allow users to use with AWS CloudFormation templates. │ │ This resource requires some setup to be done in the in chat applications console. To provide the required Slack workspace ID, you must perform the initial authorization flow with Slack in the in chat applications console, then copy and paste the workspace ID from the console. For more details, see steps 1-3 in [Tutorial: Get started with Slack](https://docs.aws.amazon.com/chatbot/latest/adminguide/slack-setup.html#slack-client-setup) in the *in chat applications User Guide* . │ └ properties │ ├ CustomizationResourceArns: (documentation changed) │ ├ IamRoleArn: (documentation changed) │ ├ SlackWorkspaceId: (documentation changed) │ └ SnsTopicArns: (documentation changed) ├[~] service aws-cloudformation │ └ resources │ ├[~] resource AWS::CloudFormation::GuardHook │ │ └ properties │ │ ├ StackFilters: (documentation changed) │ │ └ TargetFilters: (documentation changed) │ └[~] resource AWS::CloudFormation::LambdaHook │ └ properties │ ├ StackFilters: (documentation changed) │ └ TargetFilters: (documentation changed) ├[~] service aws-config │ └ resources │ └[~] resource AWS::Config::ConfigRule │ └ properties │ └ Scope: (documentation changed) ├[~] service aws-dynamodb │ └ resources │ └[~] resource AWS::DynamoDB::Table │ └ properties │ └ BillingMode: (documentation changed) ├[~] service aws-ecs │ └ resources │ ├[~] resource AWS::ECS::Cluster │ │ └ types │ │ └[~] type ServiceConnectDefaults │ │ └ properties │ │ └ Namespace: (documentation changed) │ ├[~] resource AWS::ECS::Service │ │ └ types │ │ └[~] type AwsVpcConfiguration │ │ └ properties │ │ └ AssignPublicIp: (documentation changed) │ ├[~] resource AWS::ECS::TaskDefinition │ │ └ properties │ │ └ Cpu: (documentation changed) │ └[~] resource AWS::ECS::TaskSet │ └ types │ └[~] type AwsVpcConfiguration │ └ properties │ └ AssignPublicIp: (documentation changed) ├[~] service aws-eks │ └ resources │ └[~] resource AWS::EKS::Nodegroup │ ├ - documentation: Creates a managed node group for an Amazon EKS cluster. │ │ You can only create a node group for your cluster that is equal to the current Kubernetes version for the cluster. All node groups are created with the latest AMI release version for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using a launch template. For more information about using launch templates, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) . │ │ An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that are managed by AWS for an Amazon EKS cluster. For more information, see [Managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) in the *Amazon EKS User Guide* . │ │ > Windows AMI types are only supported for commercial AWS Regions that support Windows on Amazon EKS. │ │ + documentation: Creates a managed node group for an Amazon EKS cluster. │ │ You can only create a node group for your cluster that is equal to the current Kubernetes version for the cluster. All node groups are created with the latest AMI release version for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using a launch template. │ │ For later updates, you will only be able to update a node group using a launch template only if it was originally deployed with a launch template. Additionally, the launch template ID or name must match what was used when the node group was created. You can update the launch template version with necessary changes. For more information about using launch templates, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) . │ │ An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that are managed by AWS for an Amazon EKS cluster. For more information, see [Managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) in the *Amazon EKS User Guide* . │ │ > Windows AMI types are only supported for commercial AWS Regions that support Windows on Amazon EKS. │ ├ properties │ │ └ LaunchTemplate: (documentation changed) │ └ types │ └[~] type LaunchTemplateSpecification │ └ properties │ ├ Id: (documentation changed) │ ├ Name: (documentation changed) │ └ Version: (documentation changed) ├[~] service aws-iot │ └ resources │ └[~] resource AWS::IoT::Logging │ └ - documentation: Configure logging. │ > If you already set the log function of AWS IoT Core , you can't deploy the AWS Cloud Development Kit (AWS CDK) to change the logging settings. You can change the logging settings by either: │ > │ > - Importing a role into your AWS CloudFormation stack, such as with the [infrastructure as code generator (IaC generator)](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/generate-IaC.html) . │ > - [Deleting the existing role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage_delete.html#roles-managingrole-deleting-console) . │ + documentation: Configure logging. │ > If you already set the log function of AWS IoT Core , you can't deploy the AWS Cloud Development Kit (AWS CDK) to change the logging settings. You can change the logging settings by either: │ > │ > - Importing the existing logging resource into your AWS CloudFormation stack, such as with the [infrastructure as code generator (IaC generator)](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/generate-IaC.html) . │ > - Calling `aws iot set-v2-logging-options --disable-all-logs` before creating a new CloudFormation stack. This command disables all AWS IoT logging. As a result, no AWS IoT logs will be delivered to Amazon CloudWatch until you re-enable logging. ├[~] service aws-mediapackagev2 │ └ resources │ └[~] resource AWS::MediaPackageV2::Channel │ ├ properties │ │ ├[+] InputSwitchConfiguration: InputSwitchConfiguration │ │ └[+] OutputHeaderConfiguration: OutputHeaderConfiguration │ └ types │ ├[+] type InputSwitchConfiguration │ │ ├ documentation: <p>The configuration for input switching based on the media quality confidence score (MQCS) as provided from AWS Elemental MediaLive.</p> │ │ │ name: InputSwitchConfiguration │ │ └ properties │ │ └ MQCSInputSwitching: boolean │ └[+] type OutputHeaderConfiguration │ ├ documentation: <p>The settings for what common media server data (CMSD) headers AWS Elemental MediaPackage includes in responses to the CDN.</p> │ │ name: OutputHeaderConfiguration │ └ properties │ └ PublishMQCS: boolean ├[~] service aws-networkfirewall │ └ resources │ └[~] resource AWS::NetworkFirewall::RuleGroup │ └ types │ ├[~] type RulesSource │ │ └ properties │ │ └ StatefulRules: (documentation changed) │ └[~] type StatefulRule │ └ - documentation: A single Suricata rules specification, for use in a stateful rule group. Use this option to specify a simple Suricata rule with protocol, source and destination, ports, direction, and rule options. For information about the Suricata `Rules` format, see [Rules Format](https://docs.aws.amazon.com/https://suricata.readthedocs.io/en/suricata-6.0.9/rules/intro.html) . │ + documentation: A single Suricata rules specification, for use in a stateful rule group. Use this option to specify a simple Suricata rule with protocol, source and destination, ports, direction, and rule options. For information about the Suricata `Rules` format, see [Rules Format](https://docs.aws.amazon.com/https://suricata.readthedocs.io/en/suricata-7.0.3/rules/intro.html) . ├[~] service aws-opensearchserverless │ └ resources │ └[~] resource AWS::OpenSearchServerless::SecurityConfig │ ├ properties │ │ └ IamIdentityCenterOptions: (documentation changed) │ ├ attributes │ │ ├ IamIdentityCenterOptions.ApplicationArn: (documentation changed) │ │ ├ IamIdentityCenterOptions.ApplicationDescription: (documentation changed) │ │ └ IamIdentityCenterOptions.ApplicationName: (documentation changed) │ └ types │ ├[~] type IamIdentityCenterConfigOptions │ │ ├ - documentation: Describes IAM Identity Center options for an OpenSearch Serverless security configuration in the form of a key-value map │ │ │ + documentation: Describes IAM Identity Center options for an OpenSearch Serverless security configuration in the form of a key-value map. │ │ └ properties │ │ ├ ApplicationArn: (documentation changed) │ │ ├ ApplicationDescription: (documentation changed) │ │ ├ ApplicationName: (documentation changed) │ │ ├ GroupAttribute: (documentation changed) │ │ ├ InstanceArn: (documentation changed) │ │ └ UserAttribute: (documentation changed) │ └[~] type SamlConfigOptions │ └ properties │ └ OpenSearchServerlessEntityId: (documentation changed) ├[~] service aws-organizations │ └ resources │ └[~] resource AWS::Organizations::Policy │ └ properties │ └ Content: (documentation changed) ├[~] service aws-pcaconnectorscep │ └ resources │ └[~] resource AWS::PCAConnectorSCEP::Challenge │ └ - documentation: For general-purpose connectors. Creates a *challenge password* for the specified connector. The SCEP protocol uses a challenge password to authenticate a request before issuing a certificate from a certificate authority (CA). Your SCEP clients include the challenge password as part of their certificate request to Connector for SCEP. To retrieve the connector Amazon Resource Names (ARNs) for the connectors in your account, call [ListConnectors](https://docs.aws.amazon.com/C4SCEP_API/pca-connector-scep/latest/APIReference/API_ListConnectors.html) . │ To create additional challenge passwords for the connector, call `CreateChallenge` again. We recommend frequently rotating your challenge passwords. │ + documentation: For general-purpose connectors. Creates a *challenge password* for the specified connector. The SCEP protocol uses a challenge password to authenticate a request before issuing a certificate from a certificate authority (CA). Your SCEP clients include the challenge password as part of their certificate request to Connector for SCEP. To retrieve the connector Amazon Resource Names (ARNs) for the connectors in your account, call [ListConnectors](https://docs.aws.amazon.com/pca-connector-scep/latest/APIReference/API_ListConnectors.html) . │ To create additional challenge passwords for the connector, call `CreateChallenge` again. We recommend frequently rotating your challenge passwords. ├[~] service aws-rds │ └ resources │ └[~] resource AWS::RDS::DBInstance │ └ properties │ └ StorageType: (documentation changed) ├[~] service aws-ssm │ └ resources │ └[~] resource AWS::SSM::PatchBaseline │ └ properties │ └ DefaultBaseline: (documentation changed) ├[~] service aws-transfer │ └ resources │ └[~] resource AWS::Transfer::Server │ └ attributes │ ├ As2ServiceManagedEgressIpAddresses: (documentation changed) │ └ State: (documentation changed) └[~] service aws-wisdom └ resources └[~] resource AWS::Wisdom::AIAgent └ types ├[~] type AIAgentConfiguration │ └ properties │ └[+] SessionSummarizationAIAgentConfiguration: SessionSummarizationAIAgentConfiguration ├[~] type AnswerRecommendationAIAgentConfiguration │ └ properties │ └[+] Locale: string ├[~] type ManualSearchAIAgentConfiguration │ └ properties │ └[+] Locale: string └[+] type SessionSummarizationAIAgentConfiguration ├ name: SessionSummarizationAIAgentConfiguration └ properties ├ SessionSummarizationAIPromptId: string └ Locale: string ```
- Loading branch information
1 parent
9ac3084
commit a6bfe3c