03-12-2025 Schema Updates

CHANGELOG.md

@@ -1,4 +1,14 @@
 ## 1.33.0 (Unreleased)
+
+FEATURES:
+
+* **New Data Source:** `awscc_applicationsignals_discoveries`
+* **New Data Source:** `awscc_applicationsignals_discovery`
+* **New Data Source:** `awscc_xray_transaction_search_config`
+* **New Data Source:** `awscc_xray_transaction_search_configs`
+* **New Resource:** `awscc_applicationsignals_discovery`
+* **New Resource:** `awscc_xray_transaction_search_config`
+
 ## 1.32.0 (March  6, 2025)
 
 FEATURES:

docs/data-sources/applicationsignals_discoveries.md

@@ -0,0 +1,21 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "awscc_applicationsignals_discoveries Data Source - terraform-provider-awscc"
+subcategory: ""
+description: |-
+  Plural Data Source schema for AWS::ApplicationSignals::Discovery
+---
+
+# awscc_applicationsignals_discoveries (Data Source)
+
+Plural Data Source schema for AWS::ApplicationSignals::Discovery
+
+
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Read-Only
+
+- `id` (String) Uniquely identifies the data source.
+- `ids` (Set of String) Set of Resource Identifiers.

docs/data-sources/applicationsignals_discovery.md

@@ -0,0 +1,24 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "awscc_applicationsignals_discovery Data Source - terraform-provider-awscc"
+subcategory: ""
+description: |-
+  Data Source schema for AWS::ApplicationSignals::Discovery
+---
+
+# awscc_applicationsignals_discovery (Data Source)
+
+Data Source schema for AWS::ApplicationSignals::Discovery
+
+
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `id` (String) Uniquely identifies the resource.
+
+### Read-Only
+
+- `account_id` (String) The identifier for the specified AWS account.

docs/data-sources/athena_data_catalog.md

@@ -21,11 +21,14 @@ Data Source schema for AWS::Athena::DataCatalog
 
 ### Read-Only
 
+- `connection_type` (String) The type of connection for a FEDERATED data catalog
 - `description` (String) A description of the data catalog to be created.
+- `error` (String) Text of the error that occurred during data catalog creation or deletion.
 - `name` (String) The name of the data catalog to create. The catalog name must be unique for the AWS account and can use a maximum of 128 alphanumeric, underscore, at sign, or hyphen characters.
 - `parameters` (Map of String) Specifies the Lambda function or functions to use for creating the data catalog. This is a mapping whose values depend on the catalog type.
+- `status` (String) The status of the creation or deletion of the data catalog. LAMBDA, GLUE, and HIVE data catalog types are created synchronously. Their status is either CREATE_COMPLETE or CREATE_FAILED. The FEDERATED data catalog type is created asynchronously.
 - `tags` (Attributes List) A list of comma separated tags to add to the data catalog that is created. (see [below for nested schema](#nestedatt--tags))
-- `type` (String) The type of data catalog to create: LAMBDA for a federated catalog, GLUE for AWS Glue Catalog, or HIVE for an external hive metastore.
+- `type` (String) The type of data catalog to create: LAMBDA for a federated catalog, GLUE for AWS Glue Catalog, or HIVE for an external hive metastore. FEDERATED is a federated catalog for which Athena creates the connection and the Lambda function for you based on the parameters that you pass.
 
 <a id="nestedatt--tags"></a>
 ### Nested Schema for `tags`

docs/data-sources/batch_job_definition.md

@@ -25,6 +25,7 @@ Data Source schema for AWS::Batch::JobDefinition
 - `container_properties` (Attributes) (see [below for nested schema](#nestedatt--container_properties))
 - `ecs_properties` (Attributes) (see [below for nested schema](#nestedatt--ecs_properties))
 - `eks_properties` (Attributes) (see [below for nested schema](#nestedatt--eks_properties))
+- `job_definition_arn` (String)
 - `job_definition_name` (String)
 - `node_properties` (Attributes) (see [below for nested schema](#nestedatt--node_properties))
 - `parameters` (Map of String)

docs/data-sources/bedrock_agent.md

@@ -207,6 +207,7 @@ Read-Only:
 
 Read-Only:
 
+- `additional_model_request_fields` (String) Additional Model Request Fields for Prompt Configuration
 - `base_prompt_template` (String) Base Prompt Template.
 - `foundation_model` (String) ARN or name of a Bedrock model.
 - `inference_configuration` (Attributes) Configuration for inference in prompt configuration (see [below for nested schema](#nestedatt--prompt_override_configuration--prompt_configurations--inference_configuration))

docs/data-sources/chatbot_microsoft_teams_channel_configuration.md

@@ -31,6 +31,7 @@ Data Source schema for AWS::Chatbot::MicrosoftTeamsChannelConfiguration
 - `tags` (Attributes List) The tags to add to the configuration (see [below for nested schema](#nestedatt--tags))
 - `team_id` (String) The id of the Microsoft Teams team
 - `teams_channel_id` (String) The id of the Microsoft Teams channel
+- `teams_channel_name` (String) The name of the Microsoft Teams channel
 - `teams_tenant_id` (String) The id of the Microsoft Teams tenant
 - `user_role_required` (Boolean) Enables use of a user role requirement in your chat configuration
 

docs/data-sources/dynamodb_table.md

@@ -27,8 +27,8 @@ Data Source schema for AWS::DynamoDB::Table
  Update requires: [Some interruptions](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-some-interrupt). Replacement if you edit an existing AttributeDefinition. (see [below for nested schema](#nestedatt--attribute_definitions))
 - `billing_mode` (String) Specify how you are charged for read and write throughput and how you manage capacity.
  Valid values include:
-  +   ``PROVISIONED`` - We recommend using ``PROVISIONED`` for predictable workloads. ``PROVISIONED`` sets the billing mode to [Provisioned Mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html#HowItWorks.ProvisionedThroughput.Manual).
-  +   ``PAY_PER_REQUEST`` - We recommend using ``PAY_PER_REQUEST`` for unpredictable workloads. ``PAY_PER_REQUEST`` sets the billing mode to [On-Demand Mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html#HowItWorks.OnDemand).
+  +   ``PAY_PER_REQUEST`` - We recommend using ``PAY_PER_REQUEST`` for most DynamoDB workloads. ``PAY_PER_REQUEST`` sets the billing mode to [On-demand capacity mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html). 
+  +   ``PROVISIONED`` - We recommend using ``PROVISIONED`` for steady workloads with predictable growth where capacity requirements can be reliably forecasted. ``PROVISIONED`` sets the billing mode to [Provisioned capacity mode](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html).
 
  If not specified, the default is ``PROVISIONED``.
 - `contributor_insights_specification` (Attributes) The settings used to enable or disable CloudWatch Contributor Insights for the specified table. (see [below for nested schema](#nestedatt--contributor_insights_specification))

docs/data-sources/ec2_vpc_endpoint_service.md

@@ -27,6 +27,7 @@ Data Source schema for AWS::EC2::VPCEndpointService
 - `network_load_balancer_arns` (List of String)
 - `payer_responsibility` (String)
 - `service_id` (String)
+- `supported_ip_address_types` (List of String) Specify which Ip Address types are supported for VPC endpoint service.
 - `tags` (Attributes List) The tags to add to the VPC endpoint service. (see [below for nested schema](#nestedatt--tags))
 
 <a id="nestedatt--tags"></a>

docs/data-sources/ecr_pull_through_cache_rule.md

@@ -22,6 +22,8 @@ Data Source schema for AWS::ECR::PullThroughCacheRule
 ### Read-Only
 
 - `credential_arn` (String) The ARN of the Secrets Manager secret associated with the pull through cache rule.
+- `custom_role_arn` (String) The ARN of the IAM role to be assumed by Amazon ECR to authenticate to ECR upstream registry. This role must be in the same account as the registry that you are configuring.
 - `ecr_repository_prefix` (String) The Amazon ECR repository prefix associated with the pull through cache rule.
 - `upstream_registry` (String) The name of the upstream source registry associated with the pull through cache rule.
 - `upstream_registry_url` (String) The upstream registry URL associated with the pull through cache rule.
+- `upstream_repository_prefix` (String) The repository name prefix of upstream registry to match with the upstream repository name. When this field isn't specified, Amazon ECR will use the `ROOT`.

docs/data-sources/ecs_service.md

@@ -25,7 +25,7 @@ Data Source schema for AWS::ECS::Service
  For more information, see [Balancing an Amazon ECS service across Availability Zones](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-rebalancing.html) in the *Amazon Elastic Container Service Developer Guide*.
 - `capacity_provider_strategy` (Attributes List) The capacity provider strategy to use for the service.
  If a ``capacityProviderStrategy`` is specified, the ``launchType`` parameter must be omitted. If no ``capacityProviderStrategy`` or ``launchType`` is specified, the ``defaultCapacityProviderStrategy`` for the cluster is used.
- A capacity provider strategy may contain a maximum of 6 capacity providers.
+ A capacity provider strategy can contain a maximum of 20 capacity providers.
   To remove this property from your service resource, specify an empty ``CapacityProviderStrategyItem`` array. (see [below for nested schema](#nestedatt--capacity_provider_strategy))
 - `cluster` (String) The short name or full Amazon Resource Name (ARN) of the cluster that you run your service on. If you do not specify a cluster, the default cluster is assumed.
 - `deployment_configuration` (Attributes) Optional deployment parameters that control how many tasks run during the deployment and the ordering of stopping and starting tasks. (see [below for nested schema](#nestedatt--deployment_configuration))
@@ -184,7 +184,11 @@ Read-Only:
 
 Read-Only:
 
-- `assign_public_ip` (String) Whether the task's elastic network interface receives a public IP address. The default value is ``ENABLED``.
+- `assign_public_ip` (String) Whether the task's elastic network interface receives a public IP address. 
+ Consider the following when you set this value:
+  +  When you use ``create-service`` or ``update-service``, the default is ``DISABLED``. 
+  +  When the service ``deploymentController`` is ``ECS``, the value must be ``DISABLED``. 
+  +  When you use ``create-service`` or ``update-service``, the default is ``ENABLED``.
 - `security_groups` (List of String) The IDs of the security groups associated with the task or service. If you don't specify a security group, the default security group for the VPC is used. There's a limit of 5 security groups that can be specified.
   All specified security groups must be from the same VPC.
 - `subnets` (List of String) The IDs of the subnets associated with the task or service. There's a limit of 16 subnets that can be specified.

docs/data-sources/ecs_task_definition.md

@@ -23,8 +23,7 @@ Data Source schema for AWS::ECS::TaskDefinition
 
 - `container_definitions` (Attributes Set) A list of container definitions in JSON format that describe the different containers that make up your task. For more information about container definition parameters and defaults, see [Amazon ECS Task Definitions](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_defintions.html) in the *Amazon Elastic Container Service Developer Guide*. (see [below for nested schema](#nestedatt--container_definitions))
 - `cpu` (String) The number of ``cpu`` units used by the task. If you use the EC2 launch type, this field is optional. Any value can be used. If you use the Fargate launch type, this field is required. You must use one of the following values. The value that you choose determines your range of valid values for the ``memory`` parameter.
- If you use the EC2 launch type, this field is optional. Supported values are between ``128`` CPU units (``0.125`` vCPUs) and ``10240`` CPU units (``10`` vCPUs).
- The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.
+ If you're using the EC2 launch type or the external launch type, this field is optional. Supported values are between ``128`` CPU units (``0.125`` vCPUs) and ``196608`` CPU units (``192`` vCPUs). The CPU units cannot be less than 1 vCPU when you use Windows containers on Fargate.
   +  256 (.25 vCPU) - Available ``memory`` values: 512 (0.5 GB), 1024 (1 GB), 2048 (2 GB)
   +  512 (.5 vCPU) - Available ``memory`` values: 1024 (1 GB), 2048 (2 GB), 3072 (3 GB), 4096 (4 GB)
   +  1024 (1 vCPU) - Available ``memory`` values: 2048 (2 GB), 3072 (3 GB), 4096 (4 GB), 5120 (5 GB), 6144 (6 GB), 7168 (7 GB), 8192 (8 GB)
@@ -294,11 +293,11 @@ Read-Only:
  You don't include the double quotes and brackets when you use the AWS Management Console.
   ``CMD-SHELL, curl -f http://localhost/ || exit 1`` 
  An exit code of 0 indicates success, and non-zero exit code indicates failure. For more information, see ``HealthCheck`` in the docker container create command.
-- `interval` (Number) The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds.
-- `retries` (Number) The number of times to retry a failed health check before the container is considered unhealthy. You may specify between 1 and 10 retries. The default value is 3.
-- `start_period` (Number) The optional grace period to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You can specify between 0 and 300 seconds. By default, the ``startPeriod`` is off.
+- `interval` (Number) The time period in seconds between each health check execution. You may specify between 5 and 300 seconds. The default value is 30 seconds. This value applies only when you specify a ``command``.
+- `retries` (Number) The number of times to retry a failed health check before the container is considered unhealthy. You may specify between 1 and 10 retries. The default value is 3. This value applies only when you specify a ``command``.
+- `start_period` (Number) The optional grace period to provide containers time to bootstrap before failed health checks count towards the maximum number of retries. You can specify between 0 and 300 seconds. By default, the ``startPeriod`` is off. This value applies only when you specify a ``command``. 
   If a health check succeeds within the ``startPeriod``, then the container is considered healthy and any subsequent failures count toward the maximum number of retries.
-- `timeout` (Number) The time period in seconds to wait for a health check to succeed before it is considered a failure. You may specify between 2 and 60 seconds. The default value is 5.
+- `timeout` (Number) The time period in seconds to wait for a health check to succeed before it is considered a failure. You may specify between 2 and 60 seconds. The default value is 5. This value applies only when you specify a ``command``.
 
 
 <a id="nestedatt--container_definitions--linux_parameters"></a>

docs/data-sources/elasticloadbalancingv2_load_balancer.md

@@ -24,11 +24,12 @@ Data Source schema for AWS::ElasticLoadBalancingV2::LoadBalancer
 - `canonical_hosted_zone_id` (String)
 - `dns_name` (String)
 - `enable_prefix_for_ipv_6_source_nat` (String) [Network Load Balancers with UDP listeners] Indicates whether to use an IPv6 prefix from each subnet for source NAT. The IP address type must be ``dualstack``. The default value is ``off``.
-- `enforce_security_group_inbound_rules_on_private_link_traffic` (String) Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through privatelink.
+- `enforce_security_group_inbound_rules_on_private_link_traffic` (String) Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through privatelink. The default is ``on``.
 - `ip_address_type` (String) The IP address type. Internal load balancers must use ``ipv4``.
  [Application Load Balancers] The possible values are ``ipv4`` (IPv4 addresses), ``dualstack`` (IPv4 and IPv6 addresses), and ``dualstack-without-public-ipv4`` (public IPv6 addresses and private IPv4 and IPv6 addresses).
  Application Load Balancer authentication supports IPv4 addresses only when connecting to an Identity Provider (IdP) or Amazon Cognito endpoint. Without a public IPv4 address the load balancer can't complete the authentication process, resulting in HTTP 500 errors.
  [Network Load Balancers and Gateway Load Balancers] The possible values are ``ipv4`` (IPv4 addresses) and ``dualstack`` (IPv4 and IPv6 addresses).
+- `ipv_4_ipam_pool_id` (String)
 - `load_balancer_arn` (String)
 - `load_balancer_attributes` (Attributes Set) The load balancer attributes. (see [below for nested schema](#nestedatt--load_balancer_attributes))
 - `load_balancer_full_name` (String)

docs/data-sources/iot_software_package_version.md

@@ -21,15 +21,55 @@ Data Source schema for AWS::IoT::SoftwarePackageVersion
 
 ### Read-Only
 
+- `artifact` (Attributes) The artifact location of the package version (see [below for nested schema](#nestedatt--artifact))
 - `attributes` (Map of String)
 - `description` (String)
 - `error_reason` (String)
 - `package_name` (String)
 - `package_version_arn` (String)
+- `recipe` (String) The inline json job document associated with a software package version
+- `sbom` (Attributes) The sbom zip archive location of the package version (see [below for nested schema](#nestedatt--sbom))
+- `sbom_validation_status` (String) The validation status of the Sbom file
 - `status` (String)
 - `tags` (Attributes Set) An array of key-value pairs to apply to this resource. (see [below for nested schema](#nestedatt--tags))
 - `version_name` (String)
 
+<a id="nestedatt--artifact"></a>
+### Nested Schema for `artifact`
+
+Read-Only:
+
+- `s3_location` (Attributes) The Amazon S3 location (see [below for nested schema](#nestedatt--artifact--s3_location))
+
+<a id="nestedatt--artifact--s3_location"></a>
+### Nested Schema for `artifact.s3_location`
+
+Read-Only:
+
+- `bucket` (String) The S3 bucket
+- `key` (String) The S3 key
+- `version` (String) The S3 version
+
+
+
+<a id="nestedatt--sbom"></a>
+### Nested Schema for `sbom`
+
+Read-Only:
+
+- `s3_location` (Attributes) The Amazon S3 location (see [below for nested schema](#nestedatt--sbom--s3_location))
+
+<a id="nestedatt--sbom--s3_location"></a>
+### Nested Schema for `sbom.s3_location`
+
+Read-Only:
+
+- `bucket` (String) The S3 bucket
+- `key` (String) The S3 key
+- `version` (String) The S3 version
+
+
+
 <a id="nestedatt--tags"></a>
 ### Nested Schema for `tags`
 

docs/data-sources/rds_db_cluster.md

@@ -46,7 +46,7 @@ Data Source schema for AWS::RDS::DBCluster
  Valid for: Aurora DB clusters and Multi-AZ DB clusters
 - `database_insights_mode` (String) The mode of Database Insights to enable for the DB cluster.
  If you set this value to ``advanced``, you must also set the ``PerformanceInsightsEnabled`` parameter to ``true`` and the ``PerformanceInsightsRetentionPeriod`` parameter to 465.
- Valid for Cluster Type: Aurora DB clusters only
+ Valid for Cluster Type: Aurora DB clusters and Multi-AZ DB clusters
 - `database_name` (String) The name of your database. If you don't provide a name, then Amazon RDS won't create a database in this DB cluster. For naming constraints, see [Naming Constraints](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Limits.html#RDS_Limits.Constraints) in the *Amazon Aurora User Guide*. 
  Valid for: Aurora DB clusters and Multi-AZ DB clusters
 - `db_cluster_arn` (String)