hashicorp/terraform-provider-aws

aws_bedrockagentcore_harness is missing additionalAttributes in bedrockModelConfig

Open

#48,363 opened on Jun 11, 2026

View on GitHub
 (1 comment) (3 reactions) (0 assignees)Go (10,310 forks)github user discovery
enhancementgood first issueservice/bedrockagentcore

Repository metrics

Stars
 (11,045 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

The AWS API allows for a JSON-valued field named additionalParams in the model.bedrock_model_config block, which is passed directly through to the underlying model.

Currently, we're working around this with a null_resource and a local provisioner that directly invokes aws aws bedrock-agentcore-control update-harness and passing in the additionalParams value there, but this is obviously suboptimal

Affected Resource(s) or Data Source(s)

aws_bedrockagentcore_harness

Potential Terraform Configuration

resource "aws_bedrockagentcore_harness" "main" {
  model {
    bedrock_model_config {
      model_id    = "global.anthropic.claude-sonnet-4-6"
      max_tokens  = 16384
      temperature = 1.0
      additionalParams = jsonencode({
         additionalModelRequestFields = {
            thinking = { type = "enabled", budget_tokens = 2048 }
         }
      })
    }
  }
}

References

https://github.com/aws/aws-sdk-go-v2/blob/service/bedrockagentcorecontrol/v1.43.0/service/bedrockagentcorecontrol/api_op_UpdateHarness.go

Would you like to implement the enhancement?

No

Contributor guide

Research direction
Examine the implementation of aws bedrockagentcore harness in the provider. Locate the schema for bedrock model config and its corresponding API request construction. Identify how additionalParams is represented in the AWS SDK and plan how to add it to the Terraform schema, including all CRUD operations and tests.
Tech stack
go
Domain
backendinfrastructurecloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75