RDS custom stop temporarily

Dear AWS Customer,

Hope you are in good health.

After going through the post, I understand that you are using a Lambda function to stop the DB instances based on tags. When it ran on a RDS custom for oracle DB instance, It just stopped underlying EC2 host and updated as 'unsupported configuration' on the RDS side/console. further you want to know whether the RDS custom shutdown or not .

Please correct me if I misunderstood your query.

Please allow me to answer your query :

I would like to inform you that it is the expected behaviour of RDS custom DB instance to set the state as " Unsupported configuration" in RDS console when the underlying EC2 host is stopped or restarted.

RDS Custom provides monitoring capability called the support perimeter. The support perimeter ensures that your RDS Custom instance uses a supported Amazon infrastructure, operating system, and database. To know more on this please refer below link :

[+] https://docs.amazonaws.cn/en_us/AmazonRDS/latest/UserGuide/custom-troubleshooting.html#custom-troubleshooting.fix-unsupported

Now moving on to the billing related question , I would like to inform you that you are correct in the approach behind the shutdown lambda, as it is to save money at the end of each day and shut down development machines and it works for All other DBs except RDS custom.

---> My question is the Custom Oracle RDS instance shut down or not ?

Ans : It does not shutdown. Unfortunately it is not possible to Stop the RDS custom temporarily at the moment as it is not a supported feature.

I would like to apologise for the inconvenience this feature limitation is causing you .When you use the Lambda function to shutdown based on tags , Only the underlying EC2 host gets stopped but not the RDS Custom instance. If you stop underlying EC2 instance, RDS custom Oracle server is put in 'Out of Perimeter/unsupported configuration' state and you will be charged.

Instance will be still billed in the "unsupported-configuration" state. It means that customer will be charged for the custom Oracle instance per hour even if they stop the underlying EC2 instance.

So you will get billed for all services launched with RDS Oracle Custom even if you stop oracle service and underlying EC2 instance.

You may consider purchasing Reserved instance for RDS Custom oracle instance to minimize cost. Amazon RDS Custom is available in two DB instance purchase models: On-Demand and Reserved.

[+] https://aws.amazon.com/rds/custom/pricing/

---> If not then how does one shut one down ?

Ans : As mentioned above, You cannot stop the RDS custom temporarily. If you are not using RDS custom oracle database and don't want to get billed for same, you may delete custom oracle database. Please take a snapshot before deleting and use it later for restore, if needed.

However, I would like to let you know that there is already a feature request existing in the Internal Product Team's queue on this requirement to enable RDS Custom Oracle start/stop. Unfortunately, we can not provide you with an ETA or confirmation at the moment on when or how this feature will be available in the future for RDS Custom.

The new features release updates are available regularly on the official AWS Updates sources, Please be on the lookout using the links attached below for your reference. [1] RDS What's New - https://aws.amazon.com/new/
[2] AWS Database Blog - https://aws.amazon.com/blogs/database/
[3] AWS Blog - https://aws.amazon.com/blogs/aws/

I hope that above information is useful.