1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
beantwortet vor 6 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr