RDS.pptx

AWS RDS What is AWS RDS Relational Database Service AWS RDS makes it easy to set up, operate, and scale a relational database in the AWS Cloud It provides cost-efficient, resizable capacity for an industry- standard relational database and manages common database administration tasks...

AWS RDS What is AWS RDS Relational Database Service AWS RDS makes it easy to set up, operate, and scale a relational database in the AWS Cloud It provides cost-efficient, resizable capacity for an industry- standard relational database and manages common database administration tasks Common administration tasks such as scaling, high availability, database backups, power, network and cooling are all taken care of by AWS only There are different ways we can run a database in AWS Amazon EC2 and on-premises Amazon EC2 provides scalable computing capacity in the AWS cloud. In an on-premise server we get the CPU, memory, IOPS all bundled together, but using EC2 we can allocate them as we need. For a database on Amazon EC2 instance, AWS manages all the layers below the OS Comparison of On premises and Amazon EC2 managed Databases Amazon RDS and Amazon EC2 This is a managed database service. Responsible for most management tasks This allows us to more on our application and the users than the management aspects of the database With RDS, we can use database products which we are already familiar with such as MySQL, PostgreSQL, Oracle etc. RDS manages backups, automatic failure detection and recovery. RDS backups work efficiently and reliably to restore the Database We can use read replicas for read scaling. Primary and synchronous secondary instance for fail over We can use IAM to restrict access to the RDS database  Amazon RDS also provides Custom service for Oracle and Microsoft SQL server This combines the flexibility of EC2 and the automation of RDS Amazon RDS on AWS Outposts. This extends RDS for SQL, PostgreSQL etc to AWS outpost environment AWS outposts are the same hardware as in public AWS regions which bring AWS services, infrastructure and operation models on- premises With this we can provision managed DB instances close to the business applications DB Instances This is an isolated database environment in the AWS cloud. This is the basic building block of RDS It can contain one or more databases created by the user. We can create and modify this DB instance by using the CLI or console The application servers interact with the RDS DB instances. These reside in different AZs, within the same VPC They can be in the same AZ but it can cause total failure if the DB is down in the AZ, application will be down DB Engines DB Engine is the specific relational database software that runs on our DB instance. Following softwares are supported now by AWS: Db2 MariaDB Microsoft SQL server MySQL Oracle PostgreSQL Each DB Engine has its own supported features based in version also. DB Instance Classes A DB Instance Class determines the computation and memory capacity of a DB instance It consists of both DB instance type and size. Each instance type provides different compute, memory and storage capabilities. Instance types are as follows: General purpose - balanced compute, memory and networking (db.m6g.large) Memory optimised - high compute capacity, high memory footprint Compute optimised - compute intensive workloads (only for multi AZs) Burstable performance - allows to burst performance for short time Optimitzed reads - There are specifications about which instance class supports which DB engine which includes the database software and the versions. DB Instance Storage DB Instances use DB Instance storage (Basically AWS EBS volumes) for database and logs storage Three types: Provisioned IOPS SSD (io1 and io2 Block express): Designed to meet the need of I/O intensive workloads. Low I/O latency, consistent I/O throughput. Production best General Purpose SSD (gp2 and gp3): Cost effective storage ideal for medium sized DB Instances. Development and Testing best (gp2) Magnetic (also known as standard): (legacy, not recommended) Maximum allowed is 3 TiB of storage. We can create any type of DB Instance (MySQL, PostgreSQL) up to 64 TiB of storage. Volumes added based on Engines Backups Amazon RDS creates and saves automatic backups of our DB Instance during the backup window of our DB instance (Backup window can be specified by the user. Default is random 30 min in 8 hour block per region). RDS creates a storage volume snapshot of the DB instance and backs up the entire instance, not just individual databases. For automated backup to take place, the DB must be in “available” state. It also does not take place if a DB snapshot is running in the same AWS region for the same database. Manual snapshots can also be taken for the DB instance, by giving a name, so that we can later restore from it. Time depends on the size. In single AZ DB instance, this can lead to brief suspension of I/O lasting a few sec to few min. Manual snapshots don’t expire. If we need long term backups, AWS recommends snapshots be exported to S3 bucket and saved. The first snapshot of a DB instance contains data of the full database. All subsequent snapshots are incremental. When we delete a DB, the automated backups are deleted, unless we specify a retention period. Manual snapshots are not deleted (100).