aws

http://status.aws.amazon.com/ https://www.expeditedssl.com/aws-in-plain-english
kenny 2020-03-20T16:26:52.158100Z

The information in the endpoints.edn file is extremely useful. We've been depending on it in many of our specs for aws resources. Is the format in this file something we should be depending on?

2020-03-20T16:29:51.158200Z

@kenny we won't guarantee it's format at this point, as it's sourced from aws

kenny 2020-03-20T16:30:52.158700Z

Ah. That seems unlikely to change.

2020-03-20T16:31:17.158900Z

Agreed, but there is nobody committing to that (not aws, not cognitect).

2020-03-20T16:32:08.159100Z

That said, if you think there's a good case to be made for an endpoints API, please feel free to submit an issue. We'd be happy to discuss it, at the very least.

kenny 2020-03-20T16:34:29.159300Z

Depending on it seems better than having to manually write & update these specs. To be clear, I'm not necessarily after an endpoints API, per se. We are using the data in that file to create specs for AWS partitions, services, services in a region, regions in a partition, etc.

kenny 2020-03-20T16:36:09.159500Z

Having these sort of specs built into aws-api could be useful but potentially a non-goal for the project.

2020-03-20T16:48:52.159700Z

Understood.

2020-03-20T16:49:28.159900Z

But if you're using it for something broadly applicable, it's worth some thought.

1
2020-03-20T16:49:44.160100Z

Even if not for aws-api, but for a separate project.