-
Since Hashicorp Vault started from 1.14 have ACME support I tried to configure it with dns-01 validation and found that if I'm using private hosted zone in Route53 for some reason plugin cannot find i…
-
/kind feature
**Describe the solution you'd like**
Alongside and for similar reasons to #4554.
- Add the ability to create or use a current Route53 zone.
- Add the ability for each ControlPlan…
-
**What happened**
We're using external-dns within EKS (v0.14.1). We have an environment with 5 different AWS Route 53 zones configured in it.
We recently noticed that some records were not being upd…
-
When rds_instances or clusters are used as a target for an route53 entry, applying the same yaml with no changes triggers an update when it should not.
-
### Terraform Core Version
1.3.6
### AWS Provider Version
4.47
### Affected Resource(s)
* aws_route53_zone
### Expected Behavior
The attribute name_servers order matches order in …
-
### Description
A new datasource to obtain a list of **aws route53 records** using different filters.
The main use case why this is requested is to create a Terraform logic that:
- Obtains a li…
luarx updated
3 months ago
-
### Documentation Link
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_user; https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/iam_access_k…
-
### Summary
Route53 allows enabling DNSSEC keys on registered domain, and also enable DNSSEC signing per hosted zone. It would be amazing if this was configurable through Ansible as well.
It would…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the com…
-
### Terraform Core Version
v1.8.5
### AWS Provider Version
v5.55.0
### Affected Resource(s)
* aws_route53_zone
### Expected Behavior
Consecutive run of `terraform plan -var vpn_se…