Now you can see the replica that we created is displayed in the dashboard. Change the retention period as you prefer. Figure 29: Specifying the DB instance identifierĮnable the performance insights. Select the replica source as the previously created database instance and give a name for your DB instance replica. Figure 28: Encryption is automatically enabled Figure 27: Network and security configurations Let’s select an existing VPC security group. Select the no for the public accessibility. Select the availability zone as us-east-1b. Keep the default destination DB subnet group as it is. For this practical, we will select US East(N. The next section is network and security. Select General Purpose (SSD) as the storage type as shown in figure 26. Then select db.t2.micro as the DB instance class and select no for the Multi-AZ deployment. Figure 25: Creating read replicaįirst, we have to specify the instance. Click actions and select create read replica. Go to the database dashboard and select a database. But rather than high availability purposes, Read replicas are used read scalability. Real replicas also maintain a copy of the database instances same as Multi-AZ. Figure 24: The availability zone has changed This will ensure the reliability of the DB instances. They both are synched, but they are at different availability zones. Amazon creates a primary DB Instance that will replicate the data to a standby instance. This happened because we deployed multi-AZ. Now it has changed to us-east-1a from us-east-1f.
Then again go to the summary and check the Region and AZ. Figure 23: Rebooting the database instance Tick the Reboot with failover option and click Reboot. Then it will ask about Reboot DB instances. Figure 21: The summary of newly created database It will show you the region and the AZ as us-east-1f. Look at our newly created database summary. This process is shown in figure 20 Figure 20: The process of database creation Refresh it, and you can see how the status is shown as modifying, then it will be displayed as configuring-enhanced –monitoring, and, finally, it will become available. Then you can see from the dashboard, that the database is creating. Figure-18 Figure 19: Estimated monthly costs Select no preference as the maintenance window option.Īt the end of the configurations, the estimated monthly costs are displayed.
#Sqlectron screenshots upgrade
Then for the maintenance settings, enable the auto updating by ticking the Enable auto minor version upgrade option. Figure 17: Disabling the performance insights, monitoring and log exports facilities But if you prefer these, make sure to enable them by ticking the relevant options. Figure 16: Enable encryptionĭisable the performance insights, monitoring and log exports. Then for the master key, keep the default value. Figure-15Įnable encryption by ticking the option. Tick the copy tags to the snapshots option. Select no preference as the backup window option. Figure 14: The database optionsĮnable the automatic backup and set it for 7 days. Keep the default option for the DB parameter group. Give a name to the database in the initial database name. Then let’s configure the additional options.
#Sqlectron screenshots password
Set Password authentication as the Database authentication method Figure 13: Database authentication method selection Figure 11: Availability and durability settings Figure-12 Then create a new VPC security group as we discussed in the previous session. Then tick Yes for the public accessibility option. For the subnet, the group keeps the default subnet group. Next, let’s configure the additional connectivity settings. In order to deploy multi AZ, select the Create a standby instance option. Select General Purpose(SSD) as the Storage type. Let’s select Standard classes option and under this option select db.m4. Hence, we only had the Burstable classes option.
#Sqlectron screenshots free
Figure 8: Credential settingsĪs you may remember in the previous session, we selected the free tier. Figure 7: Giving a DB instance identifierįor the credential settings, give a password and then confirm the password by retyping it. Under settings you will be asked to give a DB instance identifier. Figure 6: Selecting the version and template type
Then for the template type select Dev/Test. For this session let’s select PostgreSQL. Since we selected MySQL as the engine type in the previous session. Figure 4: Selecting a database creation method Then select Create database Figure 3: Selecting Create databaseįor the database creation method, select Standard Create. Then we will be prompted into the RDS dashboard. In the previous session, we only used one AZ when creating a database instanceįirst, search for the RDS in aws console and select it. In this blog, we are going to apply multi AZs and read replicas.
0 kommentar(er)
