Stop AWS RDS instance using the CLI

-
The easiest method to start/stop AWS RDS instance based on schedule is by using AWS CLI inside a bash/bat script.

Download and configure the AWS CLI.

Install AWS CLI – https://docs.aws.amazon.com/cli/latest/userguide/install-windows.html
Configure AWS CLI for the VPC – https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html

CLI Commands.

Use “rds stop-db-instance” and “rds start-db-instance” commands in a simple bat file as below,
 set userprofile=C:\Users\07766  
 aws rds stop-db-instance --db-instance-identifier qa-rds-ban
 aws rds stop-db-instance --db-instance-identifier dev-rds-ban
 aws rds stop-db-instance --db-instance-identifier uat-rds-ban
It is required to set the userprofile of the user who configured the AWS CLI in the bat script
set userprofile=C:\Users\<username>
If you have not configured the AWS CLI using the security parameters, it is required to add below configuration to the script,
        aws configure set AWS_ACCESS_KEY_ID <access_key>
        aws configure set AWS_SECRET_ACCESS_KEY <secret_key>
        aws configure set default.region <region>
Once the bat file is ready simple windows task scheduler would do the trick.

Limitations

This is just a simple script to start/stop rds instance on a particular time. There is no verification mechanism included in the script, which can be added by using the rds describe-db-instances command.
e.g - aws rds describe-db-instances --db-instance-identifier qa-rds-mob-ban --no-verify-ssl | findstr "DBInstanceStatus"



Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 after
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view
Read more

ORA-14126 - While splitting max value partition

-
Oracle version -- Oracle 9i to 11g While splitting partitions, SQL> alter TABLE ARBOR.CDR_BILLED split PARTITION CDR_BILLED_MAXVALUE at (TO_DATE('2014-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')) into (partition CDR_BILLED_01SEP14,partition CDR_BILLED_MAXVALUE) TABLESPACE "C01_CDR_BILL" update global indexes; 2 into (partition CDR_BILLED_01SEP14,partition CDR_BILLED_MAXVALUE) TABLESPACE "C01_CDR_BILL" update global indexes * ERROR at line 2: ORA-14126: only a <parallel clause> may follow description(s) of resulting partitions 4:58:56 PM The reason for above error is while splitting max value partition, it is not allowed to explicitly provide a tablespace. The splitted partition will be reside on the same tablespace as the max value partitions. Below can be used without the tablespace clause to split the max value partition, alter TABLE ARBOR.CDR_BILLED split PARTITION CDR_BILLED_
Read more