-
This is allowing changes in the route53 custom domain name and all the dns changes that go along with that.
Things to do:
- Create a custom domain name
- any necessary hosted zones or A or AAA rec…
-
### Terraform Version, Provider Version and Kubernetes Version
```
Terraform version:1.0.3
Kubernetes provider version:2.4.1
Kubernetes version:1.20
```
### Affected Resource(s)
###…
-
In Route53 it is possible to create private hosted zones with the same domain name but in different VPCs.
However, in such a case the parameter `name` in the API call [get_zone(name)](http://boto.rea…
-
### What problem are you facing?
Many cloud provider external resources are associated with a non-deterministic ID/external-name. To deal with that, Crossplane providers rely on the `crosspla…
-
### 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 Version
```
# go.mod
github.com/hashicorp/terraform v0.12.0-beta2
```
### Terraform Resource Files
In the Terraform AWS Provider:
```go
# aws/resource_aws_route53_zone.go…
bflad updated
2 years ago
-
## Context
With the recent update for custom SSL certificates support, route53 domains are not created when letsencrypt is used.
## Expected Behavior
route53 records should be created i…
-
### Description
I would like to be able to use `terraform destroy` to remove all resource that are dependent to my spot instance if the instance is preempted by AWS.
Take this as an example:
Usin…
-
## 1. Title
`AWS::Route53::HostedZone-DelegationSetId`
## 2. Scope of request
A new attribute, `DelegationSetId`, is desired on the `AWS::Route53::HostedZone` resource type.
* The attribute wo…
-
### What happened?
I tried the following example from the certificate docs:
It failed to run because the keys `name, record, type` are not quoted. The type wrapping is also incorrect because …