Add aws_rdsdata_query action

[psantus]

Description

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

Simple usage:

action "aws_rdsdata_query" "example" {
  config {
    resource_arn = aws_rds_cluster.example.arn
    secret_arn   = aws_secretsmanager_secret_version.example.arn
    sql          = "SELECT COUNT(*) FROM users"
  }
}

Parameterized query

action "aws_rdsdata_query" "user_lookup" {
  config {
    resource_arn = aws_rds_cluster.example.arn
    secret_arn   = aws_secretsmanager_secret_version.example.arn
    database     = "example"
    sql          = "SELECT * FROM users WHERE status = :status AND created_date > :date"

    parameters {
      name  = "status"
      value = "active"
    }

    parameters {
      name  = "date"
      value = "2024-01-01"
    }
  }
}

Relations

On top of #44629 ( Add RDS Data Service) #44630 (aws_rdsdata_query datasource) #44643 (aws_rdsdata_query resource)

Closes #44472

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

% make testacc TESTS=TestAccRDSDataQueryAction_basic PKG=rdsdata

2025/10/16 16:26:40 Creating Terraform AWS Provider (SDKv2-style)...
2025/10/16 16:26:40 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN   TestAccRDSDataQueryAction_basic
=== PAUSE TestAccRDSDataQueryAction_basic
=== CONT  TestAccRDSDataQueryAction_basic
--- PASS: TestAccRDSDataQueryAction_basic (1218.59s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/rdsdata    1223.308s

[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

---

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

[psantus]

(rebased)