resource aws_cloudfront_distribution restrictions with restriction_type equal to "none" gives an invalid request parameter

[helioascorreia]

I'm trying to configure the terraform to create a cloudfront. After a few tries, following the examples I successfully created one cloudfront, than I started to make a few tweaks to implement my desire configuration.
In my config I want to disable the geo restrictions so I follow the configuration and got an error.

with this it's working

restrictions {
    geo_restriction {
      restriction_type = "blacklist"
      locations        = ["BW"]
    }
  }

and with this not

restrictions {
    geo_restriction {
      restriction_type = "none"
    }
  }

error

Error: error updating CloudFront Distribution (E2BUECT05PC943): InvalidGeoRestrictionParameter: Your request contains invalid Restriction parameters.
        status code: 400, request id: XXXX-XXX-XXX-XXXX

The terraform plan works go and only gives the error after starting to making the apply on the api

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

terraform 0.13.5
aws 3.38.0

Affected Resource(s)

• aws_cloudfront_distribution

References

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_distribution#restrictions-arguments

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[tyree731]

I ran into this as well today. Has anyone taken a look at this?

[tyree731]

Looks like this is a duplicate of #20807 , with that issue having a workaround.