forked from avizway1/june2024
-
Notifications
You must be signed in to change notification settings - Fork 0
/
RDS.txt
134 lines (81 loc) · 4.49 KB
/
RDS.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
RDS : Relational Database Service : 7 Relational db engines.
--> Amazon Aurora (Mysql Compatable / Postgresql Compatable)
--> MySQL
--> MS SQL
--> PostgreSQL
--> MariaDB
--> Oracle
--> IBM Db2
______
ec2 instance --> OS Level --> Install anything --> We have to take care below things.
Licensing..??
UPgradations..??
Backup..??
HA / FT..??
RDS --> Everything managed by AWS.
--> We won't get any choice to login to OS level.
GUI tools to manage the Databases :
--> Amazon Aurora : Mysql Workbench / pgadmin
--> MySQL : Mysql Workbench
--> MS SQL : ssms (Microsoft Sql Server Management Studio)
--> PostgreSQL : pgadmin
--> MariaDB : workbench
--> Oracle : oracle tool, Toad
--> DB2 : DB2 Client
DB Subnet Group : Choose the subnets that we have created to run DB workloads.
VPC , 4 Subnets..
Create a DB Subnet Group, Add 2 private subnets from Diff AZs (ap-south-1a & ap-south-1b private Subntes)..
Parameter group : When we launch a DB instance/cluster, we get access to db level only. We dont have any access to OS level. So, we cannot access configuration files/settings related to this DBs. If you want to define custom configurationm create a parameter group and use it.
--> Some time, we may need to reboot the db to take effect this parameter store entries.
Endpoint Name / Hostname : my-first-mysql-rdsdb.cfpgnjehw330.ap-south-1.rds.amazonaws.com
dbadmin
Avinash1234
nslookup my-first-mysql-rdsdb.cfpgnjehw330.ap-south-1.rds.amazonaws.com ==> to know IP of RDS.
Enable Public Access : Yes.. DB can be accesable over the internet, We can install tools in local device and connect.
NO : The DB instance will be available to the resources running in same VPC.
--> DB ENgine
--> Define Username and password (admin & custom/autogenerated)
--> Storage option
--> VPC
Version : -2 / -1 mechanism.. We don't go with latest version.
Free Tier : Choose this
Credentials : Define Username and password (admin & custom/autogenerated)
DB Instance class : db.t2.micro
Storage : Min 20gb, Max: 16TB : 20 GB (Free Tier)
Storage Autoscaling : AWS will add storage automatically when the existing size is 80%.
--> 10% of existing storage
--> 5 GB .. WHich ever is higher, AWS choose it.
COnnectivity :
VPC : CustomVPC
Public Access : No
Port : 3306
Automatic Backup : AWS creates backups automatically. : Disable
0 --> disable
1 --> Min
35 --> Max
7 --> Defualt Value
--> We will get DB Endpoint to connect to db instance. We won't get any IP address for this db instances.
mysql -h myprdrds.cfpgnjehw330.ap-south-1.rds.amazonaws.com -u dbadmin -P 3306 -p
===========================================
If you are using Linux as jump server :
1. install mysql :
If you are using Amazon Linux 2, use below command to install mysql client
==> yum install mysql -y
If you are using Amazon linux 2023, use below comamnds to install mysql client.
==> sudo dnf update -y
==> sudo dnf install mariadb105
2. connect to mysql using this command :
mysql -h rdsendpointname -u username -P portno -p
ask for password :
If you are using Windows as jump server :
1. Download and install "mysql workbench", then conenct to mysql rds db.
===========================================
Task 1 : Launch a Mysql RDS db instance in CUstomVPCs Private SUbnet. Launch a Windows ec2 instance in custom VPC Public Subnet and Install Mysql workbench then connect to the RDS db instance.
Task 2 : Launch a Linux ec2 instance in custom VPC Public Subnet and Install Mysql client then connect to the RDS db instance.
Task 3 : Restore the shared sample db to the rds instance. Run a SQL command to list all customer information. (SELECT * FROM db.table)
Task 4 : Launch a POSTGRE SQL RDS db instance in CUstomVPCs Private SUbnet. Launch an ec2 instance in custom VPC Public Subnet and Install "PGAdmin" then connect to the RDS db instance.
(OR/AND)
Task 5 : Launch a MS SQL RDS db (Express) instance in CUstomVPCs Private SUbnet. Launch an ec2 instance in custom VPC Public Subnet and Install "SSMS (SQL Server management Studio)" then connect to the RDS db instance.
================================================================================================
MultiAZ Deployment : Designed for Failover/FT purpose. : Creates a standby in a different Availability Zone (AZ) to provide data redundancy, eliminate I/O freezes, and minimize latency spikes during system backups.
myrdsdb.cfpgnjehw330.ap-south-1.rds.amazonaws.com