Possible documentation issue: TTL required for ChangeResourceRecordSet

[beetree]

This request (awsutilStringValue-printed) fails:

{
  ChangeBatch: {
    Changes: [{
        Action: "UPSERT",
        ResourceRecordSet: {
          Name: "test.eleet.io",
          ResourceRecords: [{
              Value: "1.2.3.4"
            }],
          Type: "A"
        }
      }]
  },
  HostedZoneID: "Z1D7XUUU1KCTJJ"
}

InvalidInput: Invalid request
        status code: 400, request id: [704348a5-30a6-11e5-bf66-03665cd893ce]

Whereas this request works:

{
  ChangeBatch: {
    Changes: [{
        Action: "UPSERT",
        ResourceRecordSet: {
          Name: "test.eleet.io",
          ResourceRecords: [{
              Value: "1.2.3.4"
            }],
          TTL: 60,
          Type: "A"
        }
      }]
  },
  HostedZoneID: "Z1D7XUUU1KCTJJ"
}

{
  ChangeInfo: {
    ID: "/change/C11AIRX96SV181",
    Status: "PENDING",
    SubmittedAt: 2015-07-22 19:19:07.117 +0000 UTC
  }
}

But the documentation states that TTL is not required.

I hope this saves someone else some debugging time...

/b3

[lsegal]

The issue here is that TTL is conditionally required depending on what other parameters are provided in the operation, see the Route53 API Reference documentation for more information. Specifically, TTL is not required for alias resource record sets, which is why it is not marked as required. It seems like we should potentially sync some of that extra API documentation down to our SDKs, though.