1 Answer
- Newest
- Most votes
- Most comments
1
Whenever you see an error about a parameter not existing, it usually means the version of the CLI/SDK being used isn't up to date. Since MaxHealthyPercentage is a very new feature, I'd guess that's what's happening here
Since you mentioned an Automation Document, I assume this is running via CLI on an instance using SSM? If so, make sure to update the CLI on that instance to the latest version
answered 5 months ago
Relevant content
- asked 2 years ago
- asked 5 months ago
- asked 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago