Is there an article to clearly define and explain the distinctions between the different available apis? And when to best use them? For example, I see there is a cloud api, an aws api, an awsx api, and the aws-serverless api.

We're just about to land an overhaul of a bunch of content to make clear the relationships between these (and other) packages. The short answer in the meantime: •

aws

is a raw projection of the AWS platform •

awsx

is convenient APIs for more easily working with many core areas of AWS at a slightly higher level - but still with the full flexibility of AWS •

cloud

is a multi-cloud compatible API, much more limited, but very high level - for most use cases that don't need multi-cloud, we will be recommending

awsx

instead of

cloud

•

aws-serverless

is deprecated - all of the functionality that was there is not in either

aws

or

awsx

Thanks Luke! Are the APIs interchangeable. For example, would this be a recommended approach for _future proofing_: Start with the cloud api, and then when required, use the more platform specific api for fine grain settings.

You can mix and match across layers of this, but the

cloud

stuff in general will be a bit less flexible because it generally is constrained to support configuration that can be expressed across all major cloud providers - so when that is not sufficient, the "step down" to

awsx

may be slightly more steep.

aws

and

awsx

generally mix together seamlessly.