You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Debezium connector needs a user account to connect to MySQL. This
4
+
user must have appropriate permissions on all databases where you want Debezium
5
+
to capture changes.
6
+
7
+
1. Connect to your database as an admin user and create a new user for the connector:
8
+
9
+
```sql
10
+
CREATE USER '<username>'@'%' IDENTIFIED BY '<password>';
11
+
```
12
+
13
+
Replace `<username>`and`<password>` with a username and password for the new user.
14
+
15
+
The `%` means that the user can connect from any client. If you want to restrict the user to connect only from the RDI host, replace `%` with the IP address of the RDI host.
16
+
17
+
1. Grant the user the necessary permissions:
18
+
19
+
```sql
20
+
GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, LOCK TABLES ON *.* TO '<username>'@'%';
21
+
```
22
+
23
+
Replace `<username>` with the username of the Debezium user.
24
+
25
+
You can also grantSELECT permissions for specific tables only. The other permissions are global and cannot be restricted to specific tables.
26
+
27
+
```sql
28
+
GRANT RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, LOCK TABLES ON *.* TO '<username>'@'%';
29
+
GRANT SELECT ON <database>.<table> TO '<username>'@'%';
Copy file name to clipboardExpand all lines: content/integrate/redis-data-integration/data-pipelines/prepare-dbs/aws-aurora-rds/aws-aur-mysql.md
+39-38Lines changed: 39 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,18 +19,52 @@ weight: 2
19
19
Follow the steps in the sections below to prepare an [AWS Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_GettingStartedAurora.CreatingConnecting.Aurora.html) or [AWS RDS MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_GettingStarted.CreatingConnecting.MySQL.html) database.
20
20
database to work with RDI.
21
21
22
+
Select the steps for your database type.
23
+
24
+
{{< multitabs id="rds-aur-mysql"
25
+
tab1="AWS Aurora MySQL"
26
+
tab2="AWS RDS MySQL" >}}
27
+
28
+
## Add an Aurora reader node
29
+
30
+
RDI requires that your Aurora MySQL database has at least one replica or reader node.
31
+
32
+
To add a reader node to an existing database, select **Add reader** from the **Actions** menu of the database and [add a reader node](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-replicas-adding.html).
33
+
34
+
You can also create one during database creation by selecting **Create an Aurora Replica or Reader node in a different AZ (recommended for scaled availability)** under **Availability & durability > Multi-AZ deployment**.
35
+
22
36
## Create and apply parameter group
23
37
24
-
RDI requires some changes to database parameters. On AWS RDS and AWS Aurora, you change these parameters via a parameter group.
38
+
RDI requires some changes to database parameters. On AWS Aurora, you change these parameters via a parameter group.
25
39
26
40
1. In the [Relational Database Service (RDS) console](https://console.aws.amazon.com/rds/),navigate to **Parameter groups > Create parameter group**. [Create a parameter group](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.CreatingCluster.html) with the following settings:
27
41
28
42
| Name | Value |
29
43
| :-- | :-- |
30
44
|**Parameter group name**| Enter a suitable parameter group name, like `rdi-mysql`|
31
45
|**Description**| (Optional) Enter a description for the parameter group |
32
-
|**Engine Type**| Choose **Aurora MySQL** for Aurora MySQL or **MySQL Community** for AWS RDS MySQL. |
33
-
|**Parameter group family**| Choose **aurora-mysql8.0** for Aurora MySQL or **mysql8.0** for AWS RDS MySQL. |
46
+
|**Engine Type**| Choose **Aurora MySQL**. |
47
+
|**Parameter group family**| Choose **aurora-mysql8.0**. |
RDI requires some changes to database parameters. On AWS RDS, you change these parameters via a parameter group.
59
+
60
+
1. In the [Relational Database Service (RDS) console](https://console.aws.amazon.com/rds/),navigate to **Parameter groups > Create parameter group**. [Create a parameter group](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithParamGroups.CreatingCluster.html) with the following settings:
61
+
62
+
| Name | Value |
63
+
| :-- | :-- |
64
+
|**Parameter group name**| Enter a suitable parameter group name, like `rdi-mysql`|
65
+
|**Description**| (Optional) Enter a description for the parameter group |
66
+
|**Engine Type**| Choose **MySQL Community**. |
67
+
|**Parameter group family**| Choose **mysql8.0**. |
34
68
35
69
Select **Create** to create the parameter group.
36
70
@@ -47,39 +81,6 @@ RDI requires some changes to database parameters. On AWS RDS and AWS Aurora, you
47
81
48
82
Select **Save changes** to apply the parameter group to the new database.
49
83
50
-
## Create Debezium user
51
-
52
-
The Debezium connector needs a user account to connect to MySQL. This
53
-
user must have appropriate permissions on all databases where you want Debezium
54
-
to capture changes.
55
-
56
-
1. Connect to your database as an admin user and create a new user for the connector:
57
-
58
-
```sql
59
-
CREATE USER '<username>'@'%' IDENTIFIED BY '<password>';
60
-
```
61
-
62
-
Replace `<username>`and`<password>` with a username and password for the new user.
63
-
64
-
The `%` means that the user can connect from any client. If you want to restrict the user to connect only from the RDI host, replace `%` with the IP address of the RDI host.
65
-
66
-
1. Grant the user the necessary permissions:
67
-
68
-
```sql
69
-
GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, LOCK TABLES ON *.* TO '<username>'@'%';
70
-
```
71
-
72
-
Replace `<username>` with the username of the Debezium user.
73
-
74
-
You can also grantSELECT permissions for specific tables only. The other permissions are global and cannot be restricted to specific tables.
75
-
76
-
```sql
77
-
GRANT RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT, LOCK TABLES ON *.* TO '<username>'@'%';
78
-
GRANT SELECT ON <database>.<table> TO '<username>'@'%';
0 commit comments