Start Maintenance
| opsworkscm_start_maintenance | R Documentation |
Manually starts server maintenance¶
Description¶
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.
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.
Usage¶
opsworkscm_start_maintenance(ServerName, EngineAttributes)
Arguments¶
ServerName |
[required] The name of the server on which to run maintenance. |
EngineAttributes |
Engine attributes that are specific to the server on which you want to run maintenance. Attributes accepted in a StartMaintenance request for Chef
|
Value¶
A list with the following syntax:
list(
Server = list(
AssociatePublicIpAddress = TRUE|FALSE,
BackupRetentionCount = 123,
ServerName = "string",
CreatedAt = as.POSIXct(
"2015-01-01"
),
CloudFormationStackArn = "string",
CustomDomain = "string",
DisableAutomatedBackup = TRUE|FALSE,
Endpoint = "string",
Engine = "string",
EngineModel = "string",
EngineAttributes = list(
list(
Name = "string",
Value = "string"
)
),
EngineVersion = "string",
InstanceProfileArn = "string",
InstanceType = "string",
KeyPair = "string",
MaintenanceStatus = "SUCCESS"|"FAILED",
PreferredMaintenanceWindow = "string",
PreferredBackupWindow = "string",
SecurityGroupIds = list(
"string"
),
ServiceRoleArn = "string",
Status = "BACKING_UP"|"CONNECTION_LOST"|"CREATING"|"DELETING"|"MODIFYING"|"FAILED"|"HEALTHY"|"RUNNING"|"RESTORING"|"SETUP"|"UNDER_MAINTENANCE"|"UNHEALTHY"|"TERMINATED",
StatusReason = "string",
SubnetIds = list(
"string"
),
ServerArn = "string"
)
)
Request syntax¶
svc$start_maintenance(
ServerName = "string",
EngineAttributes = list(
list(
Name = "string",
Value = "string"
)
)
)