Add aws_rdsdata_query resource

[psantus]

Description

Adds support for RDS Data Query, with the Terraform resource workflow.

resource "aws_rdsdata_query" "test" {
  resource_arn = aws_rds_cluster.test.arn
  secret_arn   = aws_secretsmanager_secret_version.test.arn
  sql          = "SELECT * FROM information_schema.tables WHERE table_name = ?"
  database     = aws_rds_cluster.test.database_name

  parameters {
    name  = "table_name"
    value = "test_table"
  }
}

Relations

On top of #44629 ( Add RDS Data Service) and #44630 (aws_rdsdata_query datasource)
TO REVIEWER only the last commit is specific to this PR.

References

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html
https://docs.aws.amazon.com/rdsdataservice/latest/APIReference/API_ExecuteStatement.html

Output from Acceptance Testing

2025/10/14 01:12:30 Creating Terraform AWS Provider (SDKv2-style)...
2025/10/14 01:12:30 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN   TestAccRDSDataQueryResource_basic
=== PAUSE TestAccRDSDataQueryResource_basic
=== RUN   TestAccRDSDataQueryResource_withParameters
=== PAUSE TestAccRDSDataQueryResource_withParameters
=== CONT  TestAccRDSDataQueryResource_basic
=== CONT  TestAccRDSDataQueryResource_withParameters
--- PASS: TestAccRDSDataQueryResource_basic (1170.36s)
--- PASS: TestAccRDSDataQueryResource_withParameters (1233.06s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/rdsdata    1238.091s
...

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

⚠️ Our automation has detected the following potential issues with your pull request

---

❌ Dependency Changes (Click to expand)

Typically Go dependency changes are handled in this repository by dependabot or the maintainers. This is to prevent pull request merge conflicts and further delay reviews of contributions. For more information, see the Dependency Updates section of the contributing guide.

Remove any changes to the go.mod or go.sum files and commit them into this pull request to prevent delays with reviewing and potentially merging it.

Additional details:

• Check open pull requests with the dependencies label to view other dependency updates.
• If this pull request includes an update the AWS Go SDK (or any other dependency) version, only updates submitted via dependabot will be merged. This pull request will need to remove these changes and will need to be rebased after the existing dependency update via dependabot has been merged for this pull request to be reviewed.
• If this pull request is for supporting a new AWS service:
• Ensure the new AWS service changes are following the Adding a New AWS Service section of the contributing guide, in particular that the dependency addition and initial provider support are in a separate pull request from other changes (e.g. new resources). Contributions not following this item will not be reviewed until the changes are split.
• If this pull request is already a separate pull request from the above item, you can ignore this message.

❌ Changelog Entry Required (Click to expand)

The proposed change requires a changelog entry. Please see the Changelog Process section of the contributing guide for information on the changelog generation process.

Tip: This check is not triggered for draft pull requests, since the pull request number is not known until the pull request is opened and is required to create a changelog entry. Opening a pull request first as a draft, adding the requisite changelog entry file, and then marking the pull request as ready for review will prevent future warnings.