This message was deleted.

This issue didn’t show up with 

pulumi preview

, but it did on a 

pulumi up

That’s surprising. Are you creating the record within an

apply

? The designation in the docs is correct, because

ttl

is not required by the AWS API, it is only required when there is a certain combination of inputs From the AWS docs:

TTL
The resource record cache time to live (TTL), in seconds. Note the following:

If you're creating or updating an alias resource record set, omit TTL. Amazon Route 53 uses the value of TTL for the alias target.

If you're associating this resource record set with a health check (if you're adding a HealthCheckId element), we recommend that you specify a TTL of 60 seconds or less so clients respond quickly to changes in health status.

All of the resource record sets in a group of weighted resource record sets must have the same value for TTL.

If a group of weighted resource record sets includes one or more weighted alias resource record sets for which the alias target is an ELB load balancer, we recommend that you specify a TTL of 60 seconds for all of the non-alias weighted resource record sets that have the same name and type. Values other than 60 seconds (the TTL for load balancers) will change the effect of the values that you specify for Weight.

Type: Long

Valid Range: Minimum value of 0. Maximum value of 2147483647.

Required: No

Source

Are you creating the record within an 

apply

?

Nope. Values are coming from cfg or hardcoded string. It's really simple example. This is the functioning version, with the Ttl added -- that was the only change.

hostedZoneId := cfg.Require("hostedZoneId")
	webflowProxyName := cfg.Require("webflowProxyName")

	_, err := route53.NewRecord(ctx, "landingPageDNSRecord", &route53.RecordArgs{
		ZoneId:  pulumi.String(hostedZoneId),
		Name:    pulumi.String("join"),
		Type:    pulumi.String("CNAME"),
		Records: pulumi.StringArray{pulumi.String(webflowProxyName)},
		Ttl:     <http://pulumi.Int|pulumi.Int>(86400), // 24 hours
	})

Yeah I think this is because of what I mentioned about the docs /

ttl

only being required under certain conditions. The error is returned by the aws api, which makes sense that you wouldn’t see it in

preview

but you do in

up

I suspected as much. Thank you!