You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
aws_route53_record created with a record pointing to aws_lightsail_static_ip.resourcename.ip_adddress
Checkov check fails with CKV2_AWS_23: "Route53 A Record has Attached Resource"
In AWS console, when creating an A record and selecting an alias, there is no option to select lightsail resources (only NLB/ALB, Cloudfront etc) so only option is to statically set IP address of lightsail instance (as per code example below).
Examples
For this purpose, assume a lightsail resource with name of example has already been created.
resource "aws_route53_record" "domain" {
zone_id = aws_route53_zone.primary.zone_id
name = "mydomian.com"
type = "A"
ttl = "30"
records = [aws_lightsail_static_ip.example.ip_address]
}
Version (please complete the following information):
[Checkov Version [e.g. 22]](version: 2.3.333)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the issue
aws_route53_record created with a record pointing to aws_lightsail_static_ip.resourcename.ip_adddress
Checkov check fails with CKV2_AWS_23: "Route53 A Record has Attached Resource"
In AWS console, when creating an A record and selecting an alias, there is no option to select lightsail resources (only NLB/ALB, Cloudfront etc) so only option is to statically set IP address of lightsail instance (as per code example below).
Examples
For this purpose, assume a lightsail resource with name of example has already been created.
resource "aws_route53_record" "domain" {
zone_id = aws_route53_zone.primary.zone_id
name = "mydomian.com"
type = "A"
ttl = "30"
records = [aws_lightsail_static_ip.example.ip_address]
}
Version (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: