Skip to main content

How to stop an instance in AWS; How to delete an AWS cluster

Hi guys!

 Today's post is on how to delete an AWS cluster.

If you are brand new to Amazon Web Services, here is some quick vocabulary for you:

instance (database)
cluster
snapshot

 Let's jump right in.

Part 1 - How to Stop an Instance or Cluster in AWS:

  1. Sign on to the AWS console.
    aws console login
  2. Enter your MFA (multi-factor authentication code)aws multi-factor authentication
  3. Under "RDS Services", choose databases.
    Amazon RDS
  4. Search for your database or cluster nameAmazon RDS databases

  5. Select the radial button to the left of the instance or cluster name you would like to stop.Stop AWS RDS database

    Note: In this example, stopping the instance is the same as stopping the entire cluster because there is only 1 instance in this cluster. If this cluster had more than 1 instance, you would need to stop all of the instances for the entire cluster to be stopped. Otherwise, the cluster would still be operational.

Part 2 - How to Delete an Instance or Cluster in AWS:

If we are picking up from the last step of Part 1 where we would like to now delete the same instance or cluster we just stopped, this is what would happen.
  1. Select the radial button to the left of the instance or cluster name you would like to delete.delete AWS RDS database
  2. You will receive a prompt stating that your cluster must be started before you are able to delete the database (instance). Hit Cancel.
    delete Amazon cluster
    Note: Remember in step 5 of Part 1 that this cluster only has 1 instance and stopping the instance also stopped the entire cluster.
  3. Just like in step 5 of part 1, select the radial button to the left of instance or cluster name. Then under the 'Actions' arrow option choose to 'Start' the instance or cluster.

    Note: The cluster can't be deleted while it is stopped because the database (instance) must be online to take a final snapshot which will be your last backup of the cluster. A final snapshot is needed in the event that a developer needs the database (instance) restored in the future.
  4. Select the radial button to the left of instance or cluster name. Then under the 'Actions' arrow option choose to 'Delete' the instance or cluster. You will then be prompted to take a final snapshot of your database (instance). Then hit 'Delete'.create final aws snapshot
  5. When you hit delete, you may have to type 'delete me' as a confirmation that you want the instance or cluster deleted.

    Finally, you will be able to see the instance and/or cluster being deleted.

    Amazon AWS RDS snapshot

    Note: In this image, you can see instances and clusters being backed up prior to deletion.
If you have any questions related to this post, please put them below.

Thank you and Happy reading,

-marshé hutchinson
#learnSQLwithme
Labels:

Comments

Post a Comment

Popular posts from this blog

Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Hi guys! Here's another quick and easy post. Scenario I was trying to copy a SQL agent job from one server to another by just copying the script of that SQL job. You can copy any script by right clicking a job > Script job as > create to > new query window. I pasted the job on a different server and tried to execute it and received this error: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 199 The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]). This error message is simply saying for the variable '@owner_login_name', the user account associated with the variable is incorrect because it does not exist. Fix Simply update the variable for '@owner_login_name' to a valid user account for the current SQL instance. Now when you execute the script again to create the SQL agent job your results will be: Command(s) completed successfully. If you have any furt...
2 comments
Read more

ERROR: must be owner of database databaseName - postgres error

Hi everyone! Today's post is about Postgres SQL. In my environment we are using Postgres SQL as one option for the backend of AWS (Amazon Web Services). That's right. We also have another option - MySQL. This post however will focus on the Postgres SQL error: "ERROR: must be owner of database databaseName" Scenario : I encountered this error when I was trying to drop a database from an AWS cluster. Amazon allows you to group databases inside of containers. These containers still have the same logic as SQL schemas which hold our database in SQL server. You can read more about AWS clusters here . Solution : This is very easy. It's in the error. All I have to do is make myself the owner of the database so I can delete the database. I. If your user account does not already have read/write privileges, then you will need to sign in to the Postgres cluster with an admin account so you can grant read/write access to your user account. II. If your ...
Post a Comment
Read more

How to export SQL agent jobs from your SQL Server instance

Hi everyone! As a database administrator, you always need a copy of your data and data processes for: migrating servers disaster recovery backup procedures/best practices This post covers a simple Powershell script. The script is to take a backup of all the SQL agent jobs on your SQL server instance. If you ever needed to recreate all the jobs on another server, all you would have to do is execute the SQL script. I. In SSMS (SQL Server Management Studio), create an empty .SQL file and save it with this naming convention: I.e. SqlAgentJobs_PROD01.sql } This file will represent all the SQL agent jobs on the primary production SQL server. II. Copy the "SqlAgentJobs_PROD01.sql" file from above to a network share. III. Run the Powershell script below in  Powershell ISE as administrator: ##migrating jobs from one server to another with the replace command $SqlConnection = New-Object System.Data.SqlClient.SqlConnection $SqlConnection.ConnectionStrin...
Post a Comment
Read more