[Bug]: aws_bedrockagent_agent "instruction" attribute validator max should be changed from 4000 to 8000

[jsermersheim-hv]

Terraform Core Version

1.6.6

AWS Provider Version

5.76.0

Affected Resource(s)

validation currently throws the following error for instruction lengths greater than 4000. "Attribute instruction string length must be between 40 and 4000, got: 4036"

Amazon increased the agent instruction limit to 8000 characters. The validator needs to be updated.

While the above screenshot shows the AWS Service Quota indicating 8000 characters, the AWS API reference documentation seems to lag behind at 4000 characters:

https://docs.aws.amazon.com/bedrock/latest/APIReference/API_agent_CreateAgent.html#bedrock-agent_CreateAgent-request-instruction

Here's the specific code block:

https://github.com/acwwat/terraform-provider-aws/blob/main/internal/service/bedrockagent/agent.go#L127-L135

Expected Behavior

The validator should allow up to 8000 characters

Actual Behavior

validation currently throws the following error for instruction lengths greater than 4000. "Attribute instruction string length must be between 40 and 4000, got: 4036"

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_bedrockagent_agent" "this" {
  agent_name = "agent"
  agent_resource_role_arn = "arn:aws:..."
  foundation_model = var.agent_foundation_model
  instruction = "instructions located here with more than 4000 characters"
}

Steps to Reproduce

You just need to check the validator settings in code and compare to AWS documentation https://docs.aws.amazon.com/bedrock/latest/userguide/quotas.html#quotas-agents

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[stefanfreitag]

Hi @jsermersheim-hv,

thanks for bringing this to our attention!
I checked the service quotas on my end and you are right.

{
    "Quota": {
        "ServiceCode": "bedrock",
        "ServiceName": "Amazon Bedrock",
        "QuotaArn": "arn:aws:servicequotas:eu-central-1:464678460130:bedrock/L-6E3CDA2D",
        "QuotaCode": "L-6E3CDA2D",
        "QuotaName": "Characters in Agent instructions",
        "Value": 8000.0,
        "Unit": "None",
        "Adjustable": true,
        "GlobalQuota": false,
        "QuotaAppliedAtLevel": "ACCOUNT"
    }
}

Let me try to update the code base.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.80.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.