Document single value limitations for launch_instances function

[beardedsamwise]

Describe the issue

The documentation for the launch_instances function should make it clear that even though the following three parameters are plural, they only accept a list with a single value. The parameters are by their nature misleading (though apparently named that way for potential future expansion according to AWS Support) so documentation would help end users understand correct usage.

• AvailabilityZones
• AvailabilityZoneIds
• SubnetIds

I should note that the actual API does note this limitation, as does the general documentation.

If we look at the enter_standby function we can see a similar limitation is well documented for the InstanceIds parameter where a maximum of 20 instances can be specified, so there is a precedent for the launch_instance function to be of a similar standard.

Links

https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/autoscaling/client/launch_instances.html

[RyanFitzSimmonsAK]

Hi @beardedsamwise, thanks for reaching out. The issue you've noticed is not unique to this operation; Boto3 does not document constraints such as this one for any operation, unlike the AWS CLI documentation. The best advice I can offer is to use the API reference in conjunction with the Boto3 reference to get the entirety of the information about an operation. Please let me know if you have any follow-up questions.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.