Merge pull request #2178 from quixoticmonk/docs-auto-wave3

docs: autogenerated documentation by bedrock

docs/resources/appconfig_extension_association.md

@@ -1,5 +1,5 @@
+
 ---
-# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "awscc_appconfig_extension_association Resource - terraform-provider-awscc"
 subcategory: ""
 description: |-
@@ -10,7 +10,52 @@ description: |-
 
 An example resource schema demonstrating some basic constructs and validation rules.
 
+## Example Usage
+
+### AppConfig Extension Association with Lambda Integration
+
+Creates an AppConfig extension association that links an AppConfig environment with AWS Lambda pre-built extension, enabling Lambda function integration during the deployment process.
+
+~> This example is generated by LLM using Amazon Bedrock and validated using terraform validate, apply and destroy. While we strive for accuracy and quality, please note that the information provided may not be entirely error-free or up-to-date. We recommend independently verifying the content.
 
+```terraform
+# Data sources for AWS account and region
+data "aws_caller_identity" "current" {}
+data "aws_region" "current" {}
+
+# Create AppConfig Application
+resource "awscc_appconfig_application" "example" {
+  name = "example-app"
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+
+# Create AppConfig Environment
+resource "awscc_appconfig_environment" "example" {
+  name           = "example-env"
+  application_id = awscc_appconfig_application.example.id
+  description    = "Example environment"
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+
+# Create AppConfig Extension Association using AWS Lambda pre-built extension
+resource "awscc_appconfig_extension_association" "example" {
+  extension_identifier = "arn:aws:appconfig:${data.aws_region.current.name}:aws:lambda:1"
+  resource_identifier = "arn:aws:appconfig:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:application/${awscc_appconfig_application.example.id}/environment/${awscc_appconfig_environment.example.id}"
+  parameters = {
+    "FunctionARN" = "arn:aws:lambda:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:function:example-function"
+  }
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema

docs/resources/appconfig_hosted_configuration_version.md

@@ -1,5 +1,5 @@
+
 ---
-# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "awscc_appconfig_hosted_configuration_version Resource - terraform-provider-awscc"
 subcategory: ""
 description: |-
@@ -10,7 +10,49 @@ description: |-
 
 Resource Type definition for AWS::AppConfig::HostedConfigurationVersion
 
+## Example Usage
+
+### AppConfig Hosted Configuration Version
+
+Creates an AppConfig hosted configuration version with JSON content type, requiring an existing AppConfig application and configuration profile, allowing you to manage application configurations with version control and rollout strategies.
+
+~> This example is generated by LLM using Amazon Bedrock and validated using terraform validate, apply and destroy. While we strive for accuracy and quality, please note that the information provided may not be entirely error-free or up-to-date. We recommend independently verifying the content.
 
+```terraform
+# Data sources for AWS account and region information
+data "aws_caller_identity" "current" {}
+data "aws_region" "current" {}
+
+# Create AppConfig application first
+resource "awscc_appconfig_application" "example" {
+  name        = "example-app-test-123"
+  description = "Example AppConfig Application"
+}
+
+# Create AppConfig configuration profile
+resource "awscc_appconfig_configuration_profile" "example" {
+  application_id = awscc_appconfig_application.example.application_id
+  name           = "example-profile"
+  location_uri   = "hosted"
+  description    = "Example configuration profile"
+}
+
+# Create the hosted configuration version
+resource "awscc_appconfig_hosted_configuration_version" "example" {
+  application_id           = awscc_appconfig_application.example.application_id
+  configuration_profile_id = awscc_appconfig_configuration_profile.example.configuration_profile_id
+  content_type             = "application/json"
+  content = jsonencode({
+    "environment" : "production",
+    "database" : {
+      "connection_timeout" : 30,
+      "retry_attempts" : 3
+    }
+  })
+  description   = "Example hosted configuration version"
+  version_label = "v1.0.0"
+}
+```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema

docs/resources/apprunner_vpc_ingress_connection.md

@@ -1,5 +1,5 @@
+
 ---
-# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "awscc_apprunner_vpc_ingress_connection Resource - terraform-provider-awscc"
 subcategory: ""
 description: |-
@@ -10,7 +10,134 @@ description: |-
 
 The AWS::AppRunner::VpcIngressConnection resource is an App Runner resource that specifies an App Runner VpcIngressConnection.
 
-
+## Example Usage
+
+### Configure VPC Ingress for App Runner Service
+
+This configuration establishes a private connection between your VPC and App Runner service using VPC endpoint and VPC ingress connection, enabling secure access to your App Runner service from within your VPC infrastructure.
+
+~> This example is generated by LLM using Amazon Bedrock and validated using terraform validate, apply and destroy. While we strive for accuracy and quality, please note that the information provided may not be entirely error-free or up-to-date. We recommend independently verifying the content.
+
+```terraform
+data "aws_caller_identity" "current" {}
+data "aws_region" "current" {}
+
+# VPC Resources
+resource "aws_vpc" "main" {
+  cidr_block           = "10.0.0.0/16"
+  enable_dns_hostnames = true
+  enable_dns_support   = true
+
+  tags = {
+    Name = "app-runner-vpc"
+  }
+}
+
+resource "awscc_ec2_subnet" "private" {
+  vpc_id     = aws_vpc.main.id
+  cidr_block = "10.0.1.0/24"
+
+  tags = [{
+    key   = "Name"
+    value = "app-runner-private"
+  }]
+}
+
+# VPC Endpoint
+resource "awscc_ec2_vpc_endpoint" "apprunner" {
+  vpc_id             = aws_vpc.main.id
+  service_name       = "com.amazonaws.${data.aws_region.current.name}.apprunner.requests"
+  vpc_endpoint_type  = "Interface"
+  subnet_ids         = [awscc_ec2_subnet.private.id]
+  security_group_ids = [awscc_ec2_security_group.endpoint.id]
+
+  tags = [{
+    key   = "Name"
+    value = "app-runner-endpoint"
+  }]
+}
+
+# Security Group
+resource "awscc_ec2_security_group" "endpoint" {
+  group_name        = "app-runner-endpoint-sg"
+  group_description = "Security group for App Runner VPC endpoint"
+  vpc_id            = aws_vpc.main.id
+  security_group_ingress = [{
+    description = "HTTPS from VPC"
+    from_port   = 443
+    to_port     = 443
+    ip_protocol = "tcp"
+    cidr_ipv4   = aws_vpc.main.cidr_block
+  }]
+
+  tags = [{
+    key   = "Name"
+    value = "app-runner-endpoint-sg"
+  }]
+}
+
+# IAM Role for App Runner Service
+resource "awscc_iam_role" "apprunner_service" {
+  role_name = "app-runner-service-role"
+  assume_role_policy_document = jsonencode({
+    Version = "2012-10-17"
+    Statement = [
+      {
+        Action = "sts:AssumeRole"
+        Effect = "Allow"
+        Principal = {
+          Service = "build.apprunner.amazonaws.com"
+        }
+      }
+    ]
+  })
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+
+# App Runner Service
+resource "awscc_apprunner_service" "example" {
+  service_name = "example-service-${formatdate("YYYYMMDD-HHmm", timestamp())}"
+  source_configuration = {
+    auto_deployments_enabled = false
+    image_repository = {
+      image_configuration = {
+        port = "80"
+      }
+      image_identifier      = "public.ecr.aws/docker/library/httpd:latest"
+      image_repository_type = "ECR_PUBLIC"
+    }
+  }
+  network_configuration = {
+    egress_configuration = {
+      egress_type = "DEFAULT"
+    }
+    ingress_configuration = {
+      is_publicly_accessible = false
+    }
+  }
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+
+# App Runner VPC Ingress Connection
+resource "awscc_apprunner_vpc_ingress_connection" "example" {
+  service_arn                 = awscc_apprunner_service.example.service_arn
+  vpc_ingress_connection_name = "example-vpc-ingress"
+  ingress_vpc_configuration = {
+    vpc_id          = aws_vpc.main.id
+    vpc_endpoint_id = awscc_ec2_vpc_endpoint.apprunner.id
+  }
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema

docs/resources/ce_anomaly_monitor.md

@@ -1,5 +1,5 @@
+
 ---
-# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "awscc_ce_anomaly_monitor Resource - terraform-provider-awscc"
 subcategory: ""
 description: |-
@@ -10,7 +10,31 @@ description: |-
 
 AWS Cost Anomaly Detection leverages advanced Machine Learning technologies to identify anomalous spend and root causes, so you can quickly take action. You can use Cost Anomaly Detection by creating monitor.
 
+## Example Usage
+
+### AWS Cost Anomaly Monitor by Service
+
+Creates a dimensional cost anomaly monitor that tracks AWS cost anomalies at the service level, helping to identify unusual spending patterns across AWS services.
 
+~> This example is generated by LLM using Amazon Bedrock and validated using terraform validate, apply and destroy. While we strive for accuracy and quality, please note that the information provided may not be entirely error-free or up-to-date. We recommend independently verifying the content.
+
+```terraform
+# Create cost anomaly monitor for AWS cost
+resource "awscc_ce_anomaly_monitor" "cost_monitor" {
+  monitor_name = "aws-cost-monitor"
+  monitor_type = "DIMENSIONAL"
+  monitor_specification = jsonencode({
+    dimensions = {
+      key = "SERVICE"
+    }
+  })
+
+  tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema

docs/resources/ce_anomaly_subscription.md

@@ -1,5 +1,5 @@
+
 ---
-# generated by https://github.com/hashicorp/terraform-plugin-docs
 page_title: "awscc_ce_anomaly_subscription Resource - terraform-provider-awscc"
 subcategory: ""
 description: |-
@@ -10,7 +10,48 @@ description: |-
 
 AWS Cost Anomaly Detection leverages advanced Machine Learning technologies to identify anomalous spend and root causes, so you can quickly take action. Create subscription to be notified
 
-
+## Example Usage
+
+### Cost Anomaly Detection and Notification
+
+Creates a daily Cost Explorer anomaly subscription that monitors service-level cost anomalies and notifies via email when the cost impact threshold exceeds $100.
+
+~> This example is generated by LLM using Amazon Bedrock and validated using terraform validate, apply and destroy. While we strive for accuracy and quality, please note that the information provided may not be entirely error-free or up-to-date. We recommend independently verifying the content.
+
+```terraform
+# Get AWS Account ID
+data "aws_caller_identity" "current" {}
+
+# Get current AWS Region
+data "aws_region" "current" {}
+
+# Create a Cost anomaly monitor first
+resource "awscc_ce_anomaly_monitor" "example" {
+  monitor_name      = "example-monitor"
+  monitor_type      = "DIMENSIONAL"
+  monitor_dimension = "SERVICE"
+  resource_tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+
+# Create the anomaly subscription
+resource "awscc_ce_anomaly_subscription" "example" {
+  subscription_name = "example-subscription"
+  frequency         = "DAILY"
+  monitor_arn_list  = [awscc_ce_anomaly_monitor.example.monitor_arn]
+  threshold         = 100
+  subscribers = [{
+    type    = "EMAIL"
+    address = "[email protected]"
+  }]
+  resource_tags = [{
+    key   = "Modified By"
+    value = "AWSCC"
+  }]
+}
+```
 
 <!-- schema generated by tfplugindocs -->
 ## Schema