[Bug]: aws_appmesh_virtual_node limits 50 backends even if quota is raised

[nwsparks]

Terraform Core Version

1.6.0

AWS Provider Version

5.26.0

Affected Resource(s)

aws_appmesh_virtual_node

Expected Behavior

We were able to get AWS to raise the quota on backends via a support case. I confirmed that via the gui and api I can add new backends above 50, but via Terraform I cannot. it seems that even though our quota is 100, the Terraform resource is limiting us to 50. I think this is the relevant code? Could be wrong.

terraform-provider-aws/internal/service/appmesh/virtual_node.go

Line 269 in 586606d

MaxItems: 50,

There isn't a good reason I can see to be doing this. Terraform still runs a full plan before throwing an error and if this restriction wasn't here the AWS Api still throws an error based on the quota

Actual Behavior

When planning we receive this error and are unable to add additional backends

│ Error: Too many backend blocks
│ 
│   on ../../modules/fargate_service/app-mesh.tf line 18, in resource "aws_appmesh_virtual_node" "node":
│   18:       content {
│ 
│ No more than 50 "backend" blocks are allowed

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

locals {
  backends = toset([
    for v in range(51) : "service${v}.local"
  ])
}

resource "aws_appmesh_mesh" "test" {
  name = "test"
}

resource "aws_appmesh_virtual_node" "test" {
  name      = "test"
  mesh_name = aws_appmesh_mesh.test.name

  spec {
    dynamic "backend" {
      for_each = local.backends
      iterator = service
      content {
        virtual_service {
          virtual_service_name = service.key
        }
      }
    }
  }
}

Steps to Reproduce

im not sure if someone else could reproduce this as you need to go through aws support to get the quota raised.

but you could run the code above and see by reducing the range to 50 it works and 51 it does not.

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No

[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.

[github-actions]

This functionality has been released in v5.31.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.