Issue with Route53 and DNSSEC while the cluster is being undeployed in China

[yaremchuk3]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Affected Resource(s)

• AWS accounts in China region
• Route53 and DNSSEC

Debug Output

https://gist.github.com/yaremchuk3/a514fe67dc406a7e405643ba9f7e188a

Panic Output

Error: error while force deleting Route53 Hosted Zone (Z02456591M16DHVMZ3XXX), disabling DNSSEC: could not get DNS SEC status for hosted zone (Z02456591M16DHVMZ3XXX): AccessDenied: The operation GetDNSSEC is not available for the current AWS account 897775818260. status code: 403, request id: 893b9ef3-0049-4e06-93d2-a858dbafd17e

Expected Behavior

Hosted zones in AWS should be deleted successfully.

Actual Behavior

We use AWS for placing our kubernetes clusters. Every night our test clusters are built and undeployed. About December 10th our jobs for undeploying clusters in China AWS started crashed with error related to DNSSec.
Error: error while force deleting Route53 Hosted Zone (Z02456591M16DHVMZ3XXX), disabling DNSSEC: could not get DNS SEC status for hosted zone (Z02456591M16DHVMZ3XXX): AccessDenied: The operation GetDNSSEC is not available for the current AWS account 897775818260. status code: 403, request id: 893b9ef3-0049-4e06-93d2-a858dbafd17e

It looks like China hasn't implemented this API yet, but our terraform aws module version expects it.

Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform
- Finding hashicorp/aws versions matching ">= 2.33.*"...
- Finding hashicorp/template versions matching ">= 2.1.2"...
- Installing hashicorp/aws v3.67.0...
- Installed hashicorp/aws v3.67.0 (unauthenticated)
- Installing hashicorp/template v2.1.2...
- Installed hashicorp/template v2.1.2 (unauthenticated)

Steps to Reproduce

In Chinese AWS:

1. aws route53 get-dnssec --hosted-zone-id hosted_zone_id_here

References

• #0000

[gilesvessey]

We are running into the same issue in AWS Govcloud regions (Terraform 1.1.7, AWS provider 3.74). Deleting the zone out of the console works, but this same error message appears when Terraform tries to delete hosted zones.

[kjenney]

We are running into the same issue in AWS Govcloud regions (Terraform 1.1.7, AWS provider 3.74). Deleting the zone out of the console works, but this same error message appears when Terraform tries to delete hosted zones.

I am also experiencing the same issue in GovCloud. It would be very helpful to prioritize this.

[kjenney]

Still having this issue in GovCloud. It would be nice to prioritize this.

[kjenney]

Still having this issue in GovCloud. It would be nice to prioritize this. Following up with AWS TAM as this has been open for entirely too long.

[kjenney]

I just ran terraform destroy and now it's working in GovCloud. I'm running AWS provider 5.7.0. Hopefully this means this is resolved now.

[cs-fiscal]

This issue is still occurring with 5.7.0 through 5.11.0 (latest). What is the necessary IAM policy update in order to grant the permission to delete? route53.* does not work but going into the web UI with "administrator" policy permissions works.

UPDATE: This work is being performed in GovCloud specifically in case that helps.

[github-actions]

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