Skip to content

Conversation

@aws-cdk-automation
Copy link
Contributor

⚠️ This Pull Request updates daily and will overwrite all manual changes pushed to the branch

Updates the documentation source from upstream. See details in workflow run.


Automatically created by projen via the "update-source-documentation" workflow

> ⚠️ This Pull Request updates daily and will overwrite **all** manual changes pushed to the branch

Updates the documentation source from upstream. See details in [workflow run].

[Workflow Run]: https://github.com/cdklabs/awscdk-service-spec/actions/runs/20325232175

------

*Automatically created by projen via the "update-source-documentation" workflow*

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@github-actions
Copy link
Contributor

To work on this Pull Request, please create a new branch and PR. This prevents your work from being deleted by the automation.

Run the following commands inside the repo:

gh co 2314
git switch -c fix-pr-2314 && git push -u origin HEAD
gh pr create -t "fix: PR #2314" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/2314"

@github-actions
Copy link
Contributor

@aws-cdk/aws-service-spec: Model database diff detected
📁 Download full diff

├[~] service aws-codedeploy
│ └ resources
│    └[~]  resource AWS::CodeDeploy::DeploymentGroup
│       ├ properties
│       │  └ TerminationHookEnabled: (documentation changed)
│       └ types
│          └[~] type GreenFleetProvisioningOption
│            └ properties
│               └ Action: (documentation changed)
├[~] service aws-deadline
│ └ resources
│    └[~]  resource AWS::Deadline::Fleet
│       └ types
│          ├[~] type AcceleratorCapabilities
│          │ ├      - documentation: Provides information about the GPU accelerators used for jobs processed by a fleet.
│          │ │      + documentation: Provides information about the GPU accelerators used for jobs processed by a fleet.
│          │ │      > Accelerator capabilities cannot be used with wait-and-save fleets. If you specify accelerator capabilities, you must use either spot or on-demand instance market options. > Each accelerator type maps to specific EC2 instance families:
│          │ │      > 
│          │ │      > - `t4` : Uses G4dn instance family
│          │ │      > - `a10g` : Uses G5 instance family
│          │ │      > - `l4` : Uses G6 and Gr6 instance families
│          │ │      > - `l40s` : Uses G6e instance family
│          │ └ properties
│          │    ├ Count: (documentation changed)
│          │    └ Selections: (documentation changed)
│          └[~] type AcceleratorSelection
│            └ properties
│               ├ Name: (documentation changed)
│               └ Runtime: (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 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 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.
│       └ types
│          └[~] type ScalingConfig
│            └      - documentation: An object representing the scaling configuration details for the Amazon EC2 Auto Scaling group that is associated with your node group. When creating a node group, you must specify all or none of the properties. When updating a node group, you can specify any or none of the properties.
│                   + documentation: An object representing the scaling configuration details for the Auto Scaling group that is associated with your node group. When creating a node group, you must specify all or none of the properties. When updating a node group, you can specify any or none of the properties.
├[~] service aws-iotanalytics
│ └ resources
│    ├[~]  resource AWS::IoTAnalytics::Channel
│    │  ├      - documentation: The AWS::IoTAnalytics::Channel resource collects data from an MQTT topic and archives the raw, unprocessed messages before publishing the data to a pipeline. For more information, see [How to Use AWS IoT Analytics](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *AWS IoT Analytics User Guide* .
│    │  │      + documentation: The AWS::IoTAnalytics::Channel resource collects data from an MQTT topic and archives the raw, unprocessed messages before publishing the data to a pipeline. For more information, see [How to Use](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *User Guide* .
│    │  └ types
│    │     ├[~] type ChannelStorage
│    │     │ └ properties
│    │     │    └ ServiceManagedS3: (documentation changed)
│    │     └[~] type CustomerManagedS3
│    │       └ properties
│    │          └ RoleArn: (documentation changed)
│    ├[~]  resource AWS::IoTAnalytics::Dataset
│    │  ├      - documentation: The AWS::IoTAnalytics::Dataset resource stores data retrieved from a data store by applying a `queryAction` (an SQL query) or a `containerAction` (executing a containerized application). The data set can be populated manually by calling `CreateDatasetContent` or automatically according to a `trigger` you specify. For more information, see [How to Use AWS IoT Analytics](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *AWS IoT Analytics User Guide* .
│    │  │      + documentation: The AWS::IoTAnalytics::Dataset resource stores data retrieved from a data store by applying a `queryAction` (an SQL query) or a `containerAction` (executing a containerized application). The data set can be populated manually by calling `CreateDatasetContent` or automatically according to a `trigger` you specify. For more information, see [How to Use](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *User Guide* .
│    │  ├ properties
│    │  │  └ VersioningConfiguration: (documentation changed)
│    │  └ types
│    │     ├[~] type DeltaTimeSessionWindowConfiguration
│    │     │ ├      - documentation: A structure that contains the configuration information of a delta time session window.
│    │     │ │      [`DeltaTime`](https://docs.aws.amazon.com/iotanalytics/latest/APIReference/API_DeltaTime.html) specifies a time interval. You can use `DeltaTime` to create dataset contents with data that has arrived in the data store since the last execution. For an example of `DeltaTime` , see [Creating a SQL dataset with a delta window (CLI)](https://docs.aws.amazon.com/iotanalytics/latest/userguide/automate-create-dataset.html#automate-example6) in the *AWS IoT Analytics User Guide* .
│    │     │ │      + documentation: A structure that contains the configuration information of a delta time session window.
│    │     │ │      [`DeltaTime`](https://docs.aws.amazon.com/iotanalytics/latest/APIReference/API_DeltaTime.html) specifies a time interval. You can use `DeltaTime` to create dataset contents with data that has arrived in the data store since the last execution. For an example of `DeltaTime` , see [Creating a SQL dataset with a delta window (CLI)](https://docs.aws.amazon.com/iotanalytics/latest/userguide/automate-create-dataset.html#automate-example6) in the *ITA User Guide* .
│    │     │ └ properties
│    │     │    └ TimeoutInMinutes: (documentation changed)
│    │     ├[~] type IotEventsDestinationConfiguration
│    │     │ └ properties
│    │     │    └ RoleArn: (documentation changed)
│    │     └[~] type S3DestinationConfiguration
│    │       └ properties
│    │          └ RoleArn: (documentation changed)
│    ├[~]  resource AWS::IoTAnalytics::Datastore
│    │  ├      - documentation: AWS::IoTAnalytics::Datastore resource is a repository for messages. For more information, see [How to Use AWS IoT Analytics](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *AWS IoT Analytics User Guide* .
│    │  │      + documentation: AWS::IoTAnalytics::Datastore resource is a repository for messages. For more information, see [How to Use](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *User Guide* .
│    │  ├ properties
│    │  │  └ FileFormatConfiguration: (documentation changed)
│    │  └ types
│    │     ├[~] type CustomerManagedS3
│    │     │ └ properties
│    │     │    └ RoleArn: (documentation changed)
│    │     ├[~] type DatastoreStorage
│    │     │ └ properties
│    │     │    └ ServiceManagedS3: (documentation changed)
│    │     └[~] type FileFormatConfiguration
│    │       └      - documentation: Contains the configuration information of file formats. AWS IoT Analytics data stores support JSON and [Parquet](https://docs.aws.amazon.com/https://parquet.apache.org/) .
│    │              The default file format is JSON. You can specify only one format.
│    │              You can't change the file format after you create the data store.
│    │              + documentation: Contains the configuration information of file formats. ITA data stores support JSON and [Parquet](https://docs.aws.amazon.com/https://parquet.apache.org/) .
│    │              The default file format is JSON. You can specify only one format.
│    │              You can't change the file format after you create the data store.
│    └[~]  resource AWS::IoTAnalytics::Pipeline
│       └      - documentation: The AWS::IoTAnalytics::Pipeline resource consumes messages from one or more channels and allows you to process the messages before storing them in a data store. You must specify both a `channel` and a `datastore` activity and, optionally, as many as 23 additional activities in the `pipelineActivities` array. For more information, see [How to Use AWS IoT Analytics](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *AWS IoT Analytics User Guide* .
│              + documentation: The AWS::IoTAnalytics::Pipeline resource consumes messages from one or more channels and allows you to process the messages before storing them in a data store. You must specify both a `channel` and a `datastore` activity and, optionally, as many as 23 additional activities in the `pipelineActivities` array. For more information, see [How to Use](https://docs.aws.amazon.com/iotanalytics/latest/userguide/welcome.html#aws-iot-analytics-how) in the *User Guide* .
└[~] service aws-route53resolver
  └ resources
     └[~]  resource AWS::Route53Resolver::ResolverEndpoint
        └ properties
           ├ RniEnhancedMetricsEnabled: (documentation changed)
           └ TargetNameServerMetricsEnabled: (documentation changed)

@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Dec 18, 2025
Merged via the queue into main with commit df53041 Dec 18, 2025
13 checks passed
@aws-cdk-automation aws-cdk-automation deleted the update-source/documentation branch December 18, 2025 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant