feat(sources): update documentation

[aws-cdk-automation]

⚠️ 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

[github-actions]

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 2342
git switch -c fix-pr-2342 && git push -u origin HEAD
gh pr create -t "fix: PR #2342" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/2342"

[github-actions]

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

├[~] service aws-arcregionswitch
│ └ resources
│    └[~]  resource AWS::ARCRegionSwitch::Plan
│       ├ properties
│       │  └ ReportConfiguration: (documentation changed)
│       └ types
│          ├[~] type DocumentDbConfiguration
│          │ ├      - documentation: undefined
│          │ │      + documentation: Configuration for Amazon DocumentDB global clusters used in a Region switch plan.
│          │ └ properties
│          │    ├ Behavior: (documentation changed)
│          │    ├ CrossAccountRole: (documentation changed)
│          │    ├ DatabaseClusterArns: (documentation changed)
│          │    ├ ExternalId: (documentation changed)
│          │    ├ GlobalClusterIdentifier: (documentation changed)
│          │    ├ TimeoutMinutes: (documentation changed)
│          │    └ Ungraceful: (documentation changed)
│          ├[~] type DocumentDbUngraceful
│          │ ├      - documentation: undefined
│          │ │      + documentation: Configuration for handling failures when performing operations on DocumentDB global clusters.
│          │ └ properties
│          │    └ Ungraceful: (documentation changed)
│          ├[~] type ReportConfiguration
│          │ ├      - documentation: undefined
│          │ │      + documentation: Configuration for automatic report generation for plan executions. When configured, Region switch automatically generates a report after each plan execution that includes execution events, plan configuration, and CloudWatch alarm states.
│          │ └ properties
│          │    └ ReportOutput: (documentation changed)
│          ├[~] type ReportOutputConfiguration
│          │ ├      - documentation: undefined
│          │ │      + documentation: Configuration for report output destinations used in a Region switch plan.
│          │ └ properties
│          │    └ S3Configuration: (documentation changed)
│          └[~] type S3ReportOutputConfiguration
│            ├      - documentation: undefined
│            │      + documentation: Configuration for delivering generated reports to an Amazon S3 bucket.
│            └ properties
│               ├ BucketOwner: (documentation changed)
│               └ BucketPath: (documentation changed)
├[~] service aws-ec2
│ └ resources
│    ├[~]  resource AWS::EC2::IPAM
│    │  ├      - documentation: IPAM is a VPC feature that you can use to automate your IP address management workflows including assigning, tracking, troubleshooting, and auditing IP addresses across AWS Regions and accounts throughout your AWS Organization. For more information, see [What is IPAM?](https://docs.aws.amazon.com//vpc/latest/ipam/what-is-it-ipam.html) in the *Amazon VPC IPAM User Guide* .
│    │  │      There are AWS Identity and Access Management (IAM) permissions required to fully manage an IPAM in CloudFormation. For more information, see [Example policy](https://docs.aws.amazon.com//vpc/latest/ipam/iam-ipam-policy-examples.html) in the *Amazon VPC IPAM User Guide* .
│    │  │      + documentation: IPAM is a VPC feature that you can use to automate your IP address management workflows including assigning, tracking, troubleshooting, and auditing IP addresses across AWS Regions and accounts throughout your AWS Organization. For more information, see [What is IPAM?](https://docs.aws.amazon.com/vpc/latest/ipam/what-is-it-ipam.html) in the *Amazon VPC IPAM User Guide* .
│    │  │      There are AWS Identity and Access Management (IAM) permissions required to fully manage an IPAM in CloudFormation. For more information, see [Example policy](https://docs.aws.amazon.com/vpc/latest/ipam/iam-ipam-policy-examples.html) in the *Amazon VPC IPAM User Guide* .
│    │  └ properties
│    │     └ Tier: (documentation changed)
│    ├[~]  resource AWS::EC2::VPNConcentrator
│    │  ├      - documentation: Resource Type definition for AWS::EC2::VPNConcentrator
│    │  │      + documentation: Describes a VPN concentrator.
│    │  ├ properties
│    │  │  ├ TransitGatewayId: (documentation changed)
│    │  │  └ Type: (documentation changed)
│    │  └ attributes
│    │     ├ TransitGatewayAttachmentId: (documentation changed)
│    │     └ VpnConcentratorId: (documentation changed)
│    └[~]  resource AWS::EC2::VPNConnection
│       └ properties
│          └ VpnConcentratorId: (documentation changed)
├[~] service aws-ecr
│ └ resources
│    └[~]  resource AWS::ECR::RepositoryCreationTemplate
│       └ properties
│          └ AppliedFor: (documentation changed)
├[~] service aws-observabilityadmin
│ └ resources
│    └[~]  resource AWS::ObservabilityAdmin::TelemetryPipelines
│       └ types
│          └[~] type TelemetryPipelineConfiguration
│            └      - documentation: Defines the configuration for a telemetry pipeline, including how data flows from sources through processors to destinations.
│                   + documentation: Defines the configuration for a pipeline, including how data flows from sources through processors to destinations. The configuration is specified in YAML format and must include a valid pipeline definition with required source and sink components. This pipeline enables end-to-end telemetry data collection, transformation, and delivery while supporting optional processing steps and extensions for enhanced functionality.
│                   The primary pipeline configuration section are:
│                   - *Source:* Defines where log data originates from (S3 buckets, CloudWatch Logs, third-party APIs). Each pipeline must have exactly one source.
│                   - *Processors (optional):* Transform, parse, and enrich log data as it flows through the pipeline. Processors are applied sequentially in the order they are defined.
│                   - *Sink:* Defines the destination where processed log data is sent. Each pipeline must have exactly one sink.
│                   - *Extensions (optional):* Provide additional functionality such as AWS Secrets Manager integration for credential management.
│                   For more details on each configuration section see [CloudWatch pipelines User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-pipelines.html) . Additional comprehensive configuration examples can be found in the [CreateTelemetryPipeline API docs](https://docs.aws.amazon.com/cloudwatch/latest/observabilityadmin/API_CreateTelemetryPipeline.html#API_CreateTelemetryPipeline_Examples) .
├[~] service aws-pcs
│ └ resources
│    └[~]  resource AWS::PCS::Cluster
│       └ types
│          ├[~] type Accounting
│          │ └ properties
│          │    └ Mode: (documentation changed)
│          └[~] type SlurmRest
│            └ properties
│               └ Mode: (documentation changed)
└[~] service aws-s3
  └ resources
     └[~]  resource AWS::S3::StorageLens
        └ types
           ├[~] type AccountLevel
           │ └ properties
           │    └ AdvancedPerformanceMetrics: (documentation changed)
           ├[~] type AdvancedPerformanceMetrics
           │ ├      - documentation: Advanced Performance Metrics.
           │ │      + documentation: A property for S3 Storage Lens advanced performance metrics. Advanced performance metrics provide insights into application performance such as access patterns and network originality metrics.
           │ └ properties
           │    └ IsEnabled: (documentation changed)
           ├[~] type BucketLevel
           │ └ properties
           │    └ AdvancedPerformanceMetrics: (documentation changed)
           ├[~] type DataExport
           │ └ properties
           │    └ StorageLensTableDestination: (documentation changed)
           ├[~] type StorageLensConfiguration
           │ └ properties
           │    └ ExpandedPrefixesDataExport: (documentation changed)
           ├[~] type StorageLensExpandedPrefixesDataExport
           │ ├      - documentation: Expanded Prefixes Data Export.
           │ │      + documentation: This resource specifies the properties of your S3 Storage Lens Expanded Prefixes metrics export.
           │ └ properties
           │    ├ S3BucketDestination: (documentation changed)
           │    └ StorageLensTableDestination: (documentation changed)
           └[~] type StorageLensTableDestination
             ├      - documentation: S3 Tables destination settings for the Amazon S3 Storage Lens metrics export.
             │      + documentation: This resource configures your S3 Storage Lens reports to export to read-only S3 table buckets. With this resource, you can store your Storage Lens metrics in S3 Tables that are created in a read-only S3 table bucket called aws-s3.
             └ properties
                ├ Encryption: (documentation changed)
                └ IsEnabled: (documentation changed)