Manually starts server maintenance. This command can be useful if an
earlier maintenance attempt failed, and the underlying cause of
maintenance failure has been resolved. The server is in an
UNDER_MAINTENANCE
state while maintenance is in progress.
opsworkscm_start_maintenance(ServerName, EngineAttributes)
[required] The name of the server on which to run maintenance.
Engine attributes that are specific to the server on which you want to run maintenance.
Attributes accepted in a StartMaintenance request for Chef
CHEF_MAJOR_UPGRADE
: If a Chef Automate server is eligible for
upgrade to Chef Automate 2, add this engine attribute to a
StartMaintenance
request and set the value to true
to upgrade
the server to Chef Automate 2. For more information, see Upgrade an AWS OpsWorks for Chef Automate Server to Chef Automate 2.
svc$start_maintenance( ServerName = "string", EngineAttributes = list( list( Name = "string", Value = "string" ) ) )
Maintenance can only be started on servers in HEALTHY
and UNHEALTHY
states. Otherwise, an InvalidStateException
is thrown. A
ResourceNotFoundException
is thrown when the server does not exist. A
ValidationException
is raised when parameters of the request are not
valid.