Customizing your RDS Custom environment (original) (raw)
To pause or resume RDS Custom automation, use the modify-db-instance
AWS CLI command. Identify the DB instance using the required parameter --db-instance-identifier
. Control the automation mode with the following parameters:
--automation-mode
specifies the pause state of the DB instance. Valid values areall-paused
, which pauses automation, andfull
, which resumes it.--resume-full-automation-mode-minutes
specifies the duration of the pause. The default value is 60 minutes.
Note
Regardless of whether you specify --no-apply-immediately
or --apply-immediately
, RDS Custom applies modifications asynchronously as soon as possible.
In the command response, ResumeFullAutomationModeTime
indicates the resume time as a UTC timestamp. When the automation mode is all-paused
, you can use modify-db-instance
to resume automation mode or extend the pause period. No other modify-db-instance
options are supported.
The following example pauses automation for my-custom-instance
for 90 minutes.
For Linux, macOS, or Unix:
aws rds modify-db-instance \
--db-instance-identifier my-custom-instance \
--automation-mode all-paused \
--resume-full-automation-mode-minutes 90
For Windows:
aws rds modify-db-instance ^
--db-instance-identifier my-custom-instance ^
--automation-mode all-paused ^
--resume-full-automation-mode-minutes 90
The following example extends the pause duration for an extra 30 minutes. The 30 minutes is added to the original time shown in ResumeFullAutomationModeTime
.
For Linux, macOS, or Unix:
aws rds modify-db-instance \
--db-instance-identifier my-custom-instance \
--automation-mode all-paused \
--resume-full-automation-mode-minutes 30
For Windows:
aws rds modify-db-instance ^
--db-instance-identifier my-custom-instance ^
--automation-mode all-paused ^
--resume-full-automation-mode-minutes 30
The following example resumes full automation for my-custom-instance
.
For Linux, macOS, or Unix:
aws rds modify-db-instance \
--db-instance-identifier my-custom-instance \
--automation-mode full \
For Windows:
aws rds modify-db-instance ^
--db-instance-identifier my-custom-instance ^
--automation-mode full
In the following partial sample output, the pending AutomationMode
value isfull
.
{
"DBInstance": {
"PubliclyAccessible": true,
"MasterUsername": "admin",
"MonitoringInterval": 0,
"LicenseModel": "bring-your-own-license",
"VpcSecurityGroups": [
{
"Status": "active",
"VpcSecurityGroupId": "0123456789abcdefg"
}
],
"InstanceCreateTime": "2020-11-07T19:50:06.193Z",
"CopyTagsToSnapshot": false,
"OptionGroupMemberships": [
{
"Status": "in-sync",
"OptionGroupName": "default:custom-oracle-ee-19"
}
],
"PendingModifiedValues": {
"AutomationMode": "full"
},
"Engine": "custom-oracle-ee",
"MultiAZ": false,
"DBSecurityGroups": [],
"DBParameterGroups": [
{
"DBParameterGroupName": "default.custom-oracle-ee-19",
"ParameterApplyStatus": "in-sync"
}
],
...
"ReadReplicaDBInstanceIdentifiers": [],
"AllocatedStorage": 250,
"DBInstanceArn": "arn:aws:rds:us-west-2:012345678912:db:my-custom-instance",
"BackupRetentionPeriod": 3,
"DBName": "ORCL",
"PreferredMaintenanceWindow": "fri:10:56-fri:11:26",
"Endpoint": {
"HostedZoneId": "ABCDEFGHIJKLMNO",
"Port": 8200,
"Address": "my-custom-instance.abcdefghijk.us-west-2.rds.amazonaws.com"
},
"DBInstanceStatus": "automation-paused",
"IAMDatabaseAuthenticationEnabled": false,
"AutomationMode": "all-paused",
"EngineVersion": "19.my_cev1",
"DeletionProtection": false,
"AvailabilityZone": "us-west-2a",
"DomainMemberships": [],
"StorageType": "gp2",
"DbiResourceId": "db-ABCDEFGHIJKLMNOPQRSTUVW",
"ResumeFullAutomationModeTime": "2020-11-07T20:56:50.565Z",
"KmsKeyId": "arn:aws:kms:us-west-2:012345678912:key/aa111a11-111a-11a1-1a11-1111a11a1a1a",
"StorageEncrypted": false,
"AssociatedRoles": [],
"DBInstanceClass": "db.m5.xlarge",
"DbInstancePort": 0,
"DBInstanceIdentifier": "my-custom-instance",
"TagList": []
}