1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a 6 mois
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans