Blog

Prev in AWSHow To Connect A Two EC2 Instances Data Transfer Using AWS CLI Without AWS EFS Next in AWSHow to Connect to AWS RDS MySQL Database to EC2 Instance With PHP By Using PDO

How To Connect A Two EC2 Instances Database and Files Transfer Using AWS CLI

Mohammad Abu MattarPublished: 13 Nov, 202213 Mins read22 Mins listen

Markdown for AI

Introduction

In this post, I will show you how to connect a two EC2 instances database and files transfer using AWS CLI. I will use AWS CLI to create a VPC, EC2 instances, EBS, EFS, and security groups. I will use the EC2 instances to connect to the database and files transfer.

Prerequisites

AWS CLI installed and configured
IAM user with the following permissions:
- AmazonVPCFullAccess
- AmazonEC2FullAccess
- AmazonElasticBlockStoreFullAccess
- AmazonElasticFileSystemFullAccess

Create VPC

Step 1: Create VPC

To create a VPC, run the following command:

1
# Create a VPC
2
AWS_VPC=$(aws ec2 create-vpc \
3
  --cidr-block 10.0.0.0/16 \
4
  --query 'Vpc.VpcId' \
5
  --output text)
6

7
# Add a name tag to the VPC
8
aws ec2 create-tags \
9
  --resources $AWS_VPC \
10
  --tags Key=Name,Value=aws-vpc

Explanation:

aws ec2 create-vpc - Create a VPC
--cidr-block - The IPv4 network range for the VPC, in CIDR notation.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.
--resources - The IDs of the resources.
--tags - The tags to apply to the resource.

Step 2: Modify your custom VPC and enable DNS hostname support, and DNS support

To modify your custom VPC and enable DNS hostname support, and DNS support, run the following command:

1
# Enable DNS hostnames
2
aws ec2 modify-vpc-attribute \
3
  --vpc-id $AWS_VPC \
4
  --enable-dns-hostnames "{\"Value\":true}"
5

6
# Enable DNS support
7
aws ec2 modify-vpc-attribute \
8
  --vpc-id $AWS_VPC \
9
  --enable-dns-support "{\"Value\":true}"

Explanation:

aws ec2 modify-vpc-attribute - Modifies the specified attribute of the specified VPC.
--vpc-id - The ID of the VPC.
--enable-dns-hostnames - Indicates whether the instances launched in the VPC get DNS hostnames.
--enable-dns-support - Indicates whether DNS resolution is supported for the VPC.

Step 3: Create a Public Subnet

To create a public subnet, run the following command:

1
# Create a public subnet
2
AWS_PUBLIC_SUBNET=$(aws ec2 create-subnet \
3
  --vpc-id $AWS_VPC \
4
  --cidr-block 10.0.1.0/24 \
5
  --query 'Subnet.SubnetId' \
6
  --output text)
7

8
# Add a name tag to the public subnet
9
aws ec2 create-tags \
10
  --resources $AWS_PUBLIC_SUBNET \
11
  --tags Key=Name,Value=aws-public-subnet

Explanation:

aws ec2 create-subnet - Creates a subnet in an existing VPC.
--vpc-id - The ID of the VPC.
--cidr-block - The IPv4 network range for the subnet, in CIDR notation.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.
--resources - The IDs of the resources.
--tags - The tags to apply to the resource.

Step 4: Enable Auto-assign Public IP on the subnet

To enable auto-assign public IP on the subnet, run the following command:

1
# Enable auto-assign public IP on the subnet
2
aws ec2 modify-subnet-attribute \
3
  --subnet-id $AWS_PUBLIC_SUBNET \
4
  --map-public-ip-on-launch

Explanation:

aws ec2 modify-subnet-attribute - Modifies a subnet attribute.
--subnet-id - The ID of the subnet.
--map-public-ip-on-launch - Specify true to indicate that network interfaces created in the specified subnet should be assigned a public IPv4 address.

Step 5: Create an Internet Gateway

To create an Internet Gateway, run the following command:

1
# Create an Internet Gateway
2
AWS_INTERNET_GATEWAY=$(aws ec2 create-internet-gateway \
3
  --query 'InternetGateway.InternetGatewayId' \
4
  --output text)
5

6
# Add a name tag to the Internet Gateway
7
aws ec2 create-tags \
8
  --resources $AWS_INTERNET_GATEWAY \
9
  --tags Key=Name,Value=aws-internet-gateway

Explanation:

aws ec2 create-internet-gateway - Creates an Internet gateway for use with a VPC.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.
--resources - The IDs of the resources.
--tags - The tags to apply to the resource.

Step 6: Attach the Internet Gateway to the VPC

To attach the Internet Gateway to the VPC, run the following command:

1
# Attach the Internet Gateway to the VPC
2
aws ec2 attach-internet-gateway \
3
  --internet-gateway-id $AWS_INTERNET_GATEWAY \
4
  --vpc-id $AWS_VPC

Explanation:

aws ec2 attach-internet-gateway - Attaches an Internet gateway to a VPC, enabling connectivity between the Internet and the VPC.
--internet-gateway-id - The ID of the Internet gateway.
--vpc-id - The ID of the VPC.

Step 7: Create a Route Table

To create a route table, run the following command:

1
# Create a route table
2
AWS_ROUTE_TABLE=$(aws ec2 create-route-table \
3
  --vpc-id $AWS_VPC \
4
  --query 'RouteTable.RouteTableId' \
5
  --output text)
6

7
# Add a name tag to the route table
8
aws ec2 create-tags \
9
  --resources $AWS_ROUTE_TABLE \
10
  --tags Key=Name,Value=aws-route-table

Explanation:

aws ec2 create-route-table - Creates a route table for the specified VPC.
--vpc-id - The ID of the VPC.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.
--resources - The IDs of the resources.
--tags - The tags to apply to the resource.

Step 8: Create a custom route table association

To create a custom route table association, run the following command:

1
# Create a custom route table association
2
aws ec2 associate-route-table \
3
  --subnet-id $AWS_PUBLIC_SUBNET \
4
  --route-table-id $AWS_ROUTE_TABLE

Explanation:

aws ec2 associate-route-table - Associates a subnet with a route table.
--subnet-id - The ID of the subnet.
--route-table-id - The ID of the route table.

Step 9: Associate the subnet with route table, making it a public subnet

To associate the subnet with route table, making it a public subnet, run the following command:

1
# Associate the subnet with route table, making it a public subnet
2
aws ec2 create-route \
3
  --route-table-id $AWS_ROUTE_TABLE \
4
  --destination-cidr-block 0.0.0.0/0 \
5
  --gateway-id $AWS_INTERNET_GATEWAY

Explanation:

aws ec2 create-route - Creates a route in a route table within a VPC.
--route-table-id - The ID of the route table for the route.
--destination-cidr-block - The IPv4 CIDR address block used for the destination match.
--gateway-id - The ID of an Internet gateway or virtual private gateway attached to your VPC.

Step 10: Create a Security Group

To create a security group, run the following command:

1
# Create a security group
2
AWS_SECURITY_GROUP=$(aws ec2 create-security-group \
3
  --group-name aws-security-group \
4
  --description "AWS Security Group" \
5
  --vpc-id $AWS_VPC \
6
  --query 'GroupId' \
7
  --output text)
8

9
# Add a name tag to the security group
10
aws ec2 create-tags \
11
  --resources $AWS_SECURITY_GROUP \
12
  --tags Key=Name,Value=aws-security-group

Explanation:

aws ec2 create-security-group - Creates a security group.
--group-name - The name of the security group.
--description - A description for the security group.
--vpc-id - The ID of the VPC.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.
--resources - The IDs of the resources.
--tags - The tags to apply to the resource.

Step 11: Add a rule to the security group

To add a rule to the security group, run the following command:

1
# Add a rule to the security group
2

3
# Add SSH rule
4
aws ec2 authorize-security-group-ingress \
5
--group-id $AWS_SECURITY_GROUP \
6
--protocol tcp \
7
--port 22 \
8
--cidr 0.0.0.0/0 \
9
--output text
10

11
# Add HTTP rule
12
aws ec2 authorize-security-group-ingress \
13
--group-id $AWS_SECURITY_GROUP \
14
--protocol tcp \
15
--port 80 \
16
--cidr 0.0.0.0/0 \
17
--output text
18

19
# Add HTTPS rule
20
aws ec2 authorize-security-group-ingress \
21
--group-id $AWS_SECURITY_GROUP \
22
--protocol tcp \
23
--port 443 \
24
--cidr 0.0.0.0/0 \
25
--output text
26

27
# Add NFS rule
28
aws ec2 authorize-security-group-ingress \
29
--group-id $AWS_SECURITY_GROUP \
30
--protocol tcp \
31
--port 2049 \
32
--cidr 0.0.0.0/0 \
33
--output text
34

35
# Add mysql/arura rule
36
aws ec2 authorize-security-group-ingress \
37
--group-id $AWS_SECURITY_GROUP \
38
--protocol tcp \
39
--port 3306 \
40
--cidr 0.0.0.0/0 \
41
--output text

Explanation:

aws ec2 authorize-security-group-ingress - Adds one or more ingress rules to a security group.
--group-id - The ID of the security group.
--protocol - The IP protocol name or number.
--port - The port number.
--cidr - The IPv4 CIDR range.
--output - The output format of the command.

Create a Two EC2 Instances

Step 1: Get the latest AMI ID

To get the latest AMI ID, run the following command:

1
# Get the latest AMI ID
2
AWS_AMI=$(aws ec2 describe-images \
3
  --owners 'amazon' \
4
  --filters 'Name=name,Values=amzn2-ami-hvm-2.0.*' \
5
  'Name=state,Values=available' \
6
  --query 'sort_by(Images, &CreationDate)[-1].[ImageId]' \
7
  --output 'text')

Explanation:

aws ec2 describe-images - Describes one or more of the images (AMIs, AKIs, and ARIs) available to you.
--owners - Filters the images by the owner.
--filters - The filters to apply to the images.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.

Step 2: Create a Key Pair

To create a key pair, run the following command:

1
# Create a key pair
2
aws ec2 create-key-pair \
3
--key-name aws-key-pair \
4
--query 'KeyMaterial' \
5
--output text > aws-key-pair.pem
6

7
# Change the permission of the key pair
8
chmod 400 aws-key-pair.pem

Explanation:

aws ec2 create-key-pair - Creates a 2048-bit RSA key pair with the specified name.
--key-name - The name for the key pair.
--query - The JMESPath query that is applied to the output.
--output - The output format of the command.
chmod 400 aws-key-pair.pem - Changes the permission of the key pair, making it read-only.

Step 3: Create a User Data Script

To create a user data script, run the following command:

1
# Create a user data script
2
cat <<EOF > user-data.sh
3
#!/bin/bash
4

5
# Variables
6
ROOT_DB_PASSWORD="121612"
7
DB_NAME="DB"
8
DB_USER="user"
9
DB_PASSWORD="121612"
10

11
# update the system
12
sudo yum update -y
13

14
# install efs-utils
15
sudo yum install git rpm-build make -y
16

17
# clone the efs-utils repository
18
git clone https://github.com/aws/efs-utils
19

20
# change directory to efs-utils
21
cd efs-utils
22

23
# build the efs-utils
24
make rpm
25

26
# install the efs-utils
27
sudo yum install build/amazon-efs-utils*rpm -y
28

29
# install httpd
30
sudo yum install httpd -y
31

32
# start httpd
33
sudo systemctl start httpd
34

35
# enable httpd
36
sudo systemctl enable httpd
37

38
# At first, we will enable amazon-linux-extras so that we can specify the PHP version that we want to install.
39
sudo amazon-linux-extras enable php7.4 -y
40

41
# Install PHP
42
sudo yum install php php-{pear,cgi,common,curl,mbstring,gd,mysqlnd,gettext,bcmath,json,xml,fpm,intl,zip,imap} -y
43

44
# Install MariaDB
45
sudo yum install mariadb-server -y
46

47
# Start MariaDB
48
sudo systemctl start mariadb
49

50
# Enable MariaDB
51
sudo systemctl enable mariadb
52

53
# Restart Apache
54
sudo systemctl restart httpd
55

56
# We will now secure MariaDB.
57
sudo mysql_secure_installation <<EOF2
58

59
y
60
$ROOT_DB_PASSWORD
61
$ROOT_DB_PASSWORD
62
y
63
y
64
y
65
y
66
EOF2
67

68
# Create a database
69
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CREATE DATABASE $DB_NAME;"
70

71
# Create a user
72
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CREATE USER '$DB_USER'@'localhost' IDENTIFIED BY '$DB_PASSWORD';"
73

74
# Grant privileges
75
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "GRANT ALL PRIVILEGES ON $DB_NAME.* TO '$DB_USER'@'localhost';"
76

77
# Flush privileges
78
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "FLUSH PRIVILEGES;"
79

80
# Create PHP page
81

82
cat <<EOF3 > /var/www/html/index.php
83
<?php
84
\$servername = "localhost";
85
\$username = "$DB_USER";
86
\$password = "$DB_PASSWORD";
87
\$dbname = "$DB_NAME";
88

89
// Create connection
90
try {
91
    \$conn = new PDO("mysql:host=\$servername;dbname=\$dbname", \$username, \$password);
92
    // set the PDO error mode to exception
93
    \$conn->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
94
    echo "Connected successfully";
95
} catch(PDOException \$e) {
96
    echo "Connection failed: " . \$e->getMessage();
97
}
98
?>
99
EOF3
100

101
# Restart Apache
102
sudo systemctl restart httpd
103

104
EOF

The user data script performs the following tasks:

Updates the system.
Installs the EFS utilities.
Installs Apache HTTP Server.
Installs PHP.
Installs MariaDB.
Secures MariaDB.
Creates a database.
Creates a user.
Grants privileges to the user.
Creates a PHP page.
Restarts Apache HTTP Server.

1
# Create a user data script
2
cat <<EOF > user-data2.sh
3
#!/bin/bash
4

5
# Variables
6
ROOT_DB_PASSWORD="121612"
7
DB_NAME="DB"
8
DB_USER="user"
9
DB_PASSWORD="121612"
10

11
# update the system
12
sudo yum update -y
13

14
# install efs-utils
15
sudo yum install git rpm-build make -y
16

17
# clone the efs-utils repository
18
git clone https://github.com/aws/efs-utils
19

20
# change directory to efs-utils
21
cd efs-utils
22

23
# build the efs-utils
24
make rpm
25

26
# install the efs-utils
27
sudo yum install build/amazon-efs-utils*rpm -y
28

29
# install httpd
30
sudo yum install httpd -y
31

32
# start httpd
33
sudo systemctl start httpd
34

35
# enable httpd
36
sudo systemctl enable httpd
37

38
# At first, we will enable amazon-linux-extras so that we can specify the PHP version that we want to install.
39
sudo amazon-linux-extras enable php7.4 -y
40

41
# Install PHP
42
sudo yum install php php-{pear,cgi,common,curl,mbstring,gd,mysqlnd,gettext,bcmath,json,xml,fpm,intl,zip,imap} -y
43

44
# Install MariaDB
45
sudo yum install mariadb-server -y
46

47
# Start MariaDB
48
sudo systemctl start mariadb
49

50
# Enable MariaDB
51
sudo systemctl enable mariadb
52

53
# Restart Apache
54
sudo systemctl restart httpd
55

56
# We will now secure MariaDB.
57
sudo mysql_secure_installation <<EOF2
58

59
y
60
$ROOT_DB_PASSWORD
61
$ROOT_DB_PASSWORD
62
y
63
y
64
y
65
y
66
EOF2
67

68
EOF

The user data script performs the following tasks:

Updates the system.
Installs the EFS utilities.
Installs Apache HTTP Server.
Installs PHP.
Installs MariaDB.
Restarts Apache HTTP Server.
Secures MariaDB.

Step 4: Create a Two EC2 Instances

To create two EC2 instances, run the following command:

1
# Create two EC2 instances
2
AWS_EC2_INSTANCE_1=$(aws ec2 run-instances \
3
--image-id $AWS_AMI \
4
--instance-type t2.micro \
5
--key-name aws-key-pair \
6
--monitoring "Enabled=false" \
7
--security-group-ids $AWS_SECURITY_GROUP \
8
--subnet-id $AWS_PUBLIC_SUBNET \
9
--user-data file://user-data.sh \
10
--query 'Instances[0].InstanceId' \
11
--output text)
12

13
AWS_EC2_INSTANCE_2=$(aws ec2 run-instances \
14
--image-id $AWS_AMI \
15
--instance-type t2.micro \
16
--key-name aws-key-pair \
17
--monitoring "Enabled=false" \
18
--security-group-ids $AWS_SECURITY_GROUP \
19
--subnet-id $AWS_PUBLIC_SUBNET \
20
--user-data file://user-data2.sh \
21
--query 'Instances[0].InstanceId' \
22
--output text)
23

24
# Add a tag to the instances
25
aws ec2 create-tags \
26
--resources $AWS_EC2_INSTANCE_1 \
27
--tags Key=Name,Value=ec2-instance-1
28

29
aws ec2 create-tags \
30
--resources $AWS_EC2_INSTANCE_2 \
31
--tags Key=Name,Value=ec2-instance-2

Explanation:

AWS_EC2_INSTANCE_1 and AWS_EC2_INSTANCE_2 are variables that store the instance IDs of the two EC2 instances.
The aws ec2 run-instances command creates two EC2 instances.
The --image-id option specifies the AMI ID.
The --instance-type option specifies the instance type.
The --key-name option specifies the key pair name.
The --monitoring option specifies whether detailed monitoring is enabled.
The --security-group-ids option specifies the security group ID.
The --subnet-id option specifies the subnet ID.
The --user-data option specifies the user data script.
The --query option specifies the query to retrieve the instance ID.
The --output option specifies the output format.
The aws ec2 create-tags command adds a tag to the instances.

Create an EBS Volume

Step 1: Create an EBS Volume With Multiple

To create an EBS volume with all availability zones, run the following command:

1
AWS_AVAILABILITY_ZONE=$(aws ec2 describe-availability-zones \
2
--query 'AvailabilityZones[*].ZoneName' \
3
--output text)
4

5
# Create an EBS volume with all availability zones
6
AWS_EBS_VOLUME=$(aws ec2 create-volume \
7
--availability-zone $AWS_AVAILABILITY_ZONE \
8
--size 1 \
9
--volume-type io1 \
10
--iops 100 \
11
--query 'VolumeId' \
12
--output text)
13

14
# Add a tag to the EBS volume
15
aws ec2 create-tags \
16
--resources $AWS_EBS_VOLUME \
17
--tags Key=Name,Value=ebs-volume

Explanation:

AWS_AVAILABILITY_ZONE is a variable that stores the availability zone.
The aws ec2 describe-availability-zones command retrieves the availability zone.
The --query option specifies the query to retrieve the availability zone.
The --output option specifies the output format.
The aws ec2 create-volume command creates an EBS volume.
The --availability-zone option specifies the availability zone.
The --size option specifies the size of the volume, in GiB.
The --volume-type option specifies the volume type.
The --iops option specifies the number of I/O operations per second (IOPS) that the volume supports.
The --query option specifies the query to retrieve the volume ID.
The --output option specifies the output format.
The aws ec2 create-tags command adds a tag to the EBS volume.

Step 2: Attach the EBS Volume to the First EC2 Instance

To attach the EBS volume to the first EC2 instance, run the following command:

1
# Attach the EBS volume to the first EC2 instance
2
aws ec2 attach-volume \
3
--device /dev/sdf \
4
--instance-id $AWS_EC2_INSTANCE_1 \
5
--volume-id $AWS_EBS_VOLUME

Explanation:

The aws ec2 attach-volume command attaches the EBS volume to the first EC2 instance.
The --device option specifies the device name.
The --instance-id option specifies the instance ID.
The --volume-id option specifies the volume ID.

Step 3: Create a File System and Mount the EBS Volume

To create a file system and mount the EBS volume, run the following command:

1
# connect to the first EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_1_PUBLIC_IP
3

4
# create a file system
5
sudo mkfs -t ext4 /dev/xvdf
6

7
# create a directory
8
sudo mkdir /data
9

10
# mount the EBS volume
11
sudo mount /dev/xvdf /data
12

13
# add the EBS volume to the fstab file
14
sudo echo "/dev/xvdf /data ext4 defaults 0 0" >> /etc/fstab
15

16
# exit the first EC2 instance
17
exit

Explanation:

The ssh command connects to the first EC2 instance.
The sudo mkfs -t ext4 /dev/xvdf command creates a file system.
The sudo mkdir /data command creates a directory.
The sudo mount /dev/xvdf /data command mounts the EBS volume.
The sudo echo "/dev/xvdf /data ext4 defaults 0 0" >> /etc/fstab command adds the EBS volume to the fstab file.
The exit command exits the first EC2 instance.

Step 4: Attach the EBS Volume to the Second EC2 Instance

To attach the EBS volume to the second EC2 instance, run the following command:

1
# Attach the EBS volume to the second EC2 instance
2
aws ec2 attach-volume \
3
--device /dev/sdf \
4
--instance-id $AWS_EC2_INSTANCE_2 \
5
--volume-id $AWS_EBS_VOLUME

Explanation:

The aws ec2 attach-volume command attaches the EBS volume to the second EC2 instance.
The --device option specifies the device name.
The --instance-id option specifies the instance ID.
The --volume-id option specifies the volume ID.

Step 5: Create a File System and Mount the EBS Volume

To create a file system and mount the EBS volume, run the following command:

1
# connect to the second EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_2_PUBLIC_IP
3

4
# create a file system
5
sudo mkfs -t ext4 /dev/xvdf
6

7
# create a directory
8
sudo mkdir /data
9

10
# mount the EBS volume
11
sudo mount /dev/xvdf /data
12

13
# add the EBS volume to the fstab file
14
sudo echo "/dev/xvdf /data ext4 defaults 0 0" >> /etc/fstab
15

16
# exit the second EC2 instance
17
exit

Explanation:

The ssh command connects to the second EC2 instance.
The sudo mkfs -t ext4 /dev/xvdf command creates a file system.
The sudo mkdir /data command creates a directory.
The sudo mount /dev/xvdf /data command mounts the EBS volume.
The sudo echo "/dev/xvdf /data ext4 defaults 0 0" >> /etc/fstab command adds the EBS volume to the fstab file.
The exit command exits the second EC2 instance.

Create an EFS File System

Step 1: Create an EFS File System

To create an EFS file system, run the following command:

1
# Create an EFS file system
2
AWS_EFS_FILE_SYSTEM=$(aws efs create-file-system \
3
--performance-mode generalPurpose \
4
--throughput-mode bursting \
5
--query 'FileSystemId' \
6
--output text)
7

8
# Add a tag to the EFS file system
9
aws efs create-tags \
10
--file-system-id $AWS_EFS_FILE_SYSTEM \
11
--tags Key=Name,Value=efs-file-system

Explanation:

The aws efs create-file-system command creates an EFS file system.
The --performance-mode option specifies the performance mode.
The --throughput-mode option specifies the throughput mode.
The --query option specifies the query to retrieve the file system ID.
The --output option specifies the output format.
The aws efs create-tags command adds a tag to the EFS file system.

Step 2: Create an EFS Mount Target

To create an EFS mount target, run the following command:

1
# Create an EFS mount target
2
AWS_EFS_MOUNT_TARGET=$(aws efs create-mount-target \
3
--file-system-id $AWS_EFS_FILE_SYSTEM \
4
--subnet-id $AWS_PUBLIC_SUBNET \
5
--security-groups $AWS_SECURITY_GROUP \
6
--query 'MountTargetId' \
7
--output text)

Explanation:

The aws efs create-mount-target command creates an EFS mount target.
The --file-system-id option specifies the file system ID.
The --subnet-id option specifies the subnet ID.
The --security-groups option specifies the security group ID.
The --query option specifies the query to retrieve the mount target ID.
The --output option specifies the output format.

Step 3: Mount the EFS File System to Two EC2 Instances

To mount the EFS file system to two EC2 instances, run the following command:

1
# connect to the first EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_1_PUBLIC_IP
3

4
# mount the EFS file system
5
sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 $AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html
6

7
# add the EFS file system to the fstab file
8
sudo echo "$AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html nfs4 nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 0 0" >> /etc/fstab
9

10
# exit the first EC2 instance
11
exit
12

13
# connect to the second EC2 instance
14
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_2_PUBLIC_IP
15

16
# mount the EFS file system
17
sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 $AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html
18

19
# add the EFS file system to the fstab file
20
sudo echo "$AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html nfs4 nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 0 0" >> /etc/fstab
21

22
# exit the second EC2 instance
23
exit

Explanation:

The ssh command connects to the first EC2 instance.
The sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 $AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html command mounts the EFS file system.
The sudo echo "$AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html nfs4 nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 0 0" >> /etc/fstab command adds the EFS file system to the fstab file.
The exit command exits the first EC2 instance.
The ssh command connects to the second EC2 instance.
The sudo mount -t nfs4 -o nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 $AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html command mounts the EFS file system.
The sudo echo "$AWS_EFS_FILE_SYSTEM.efs.$AVAILABILITY_ZONE.amazonaws.com:/ /var/www/html nfs4 nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 0 0" >> /etc/fstab command adds the EFS file system to the fstab file.
The exit command exits the second EC2 instance.

Create a Database Replication on EBS

Step 1: Create a Database Replication on EBS

To create a database replication on EBS, run the following command:

Connect to the first EC2 instance.

1
# Connect to the first EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_1_PUBLIC_IP

Create a database Replication

1
# Variables
2
ROOT_DB_PASSWORD="121612"
3

4
# Create a database Replication
5
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CREATE USER 'replication'@'%' IDENTIFIED BY '121612';"
6
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "GRANT REPLICATION SLAVE ON *.* TO 'replication'@'%';"
7
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "FLUSH PRIVILEGES;"
8
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "SHOW MASTER STATUS;"

Explanation:

The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CREATE USER 'replication'@'%' IDENTIFIED BY '121612';" command creates a database replication.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "GRANT REPLICATION SLAVE ON *.* TO 'replication'@'%';" command grants replication slave on all databases to the replication user.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "FLUSH PRIVILEGES;" command flushes the privileges.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "SHOW MASTER STATUS;" command shows the master status.
Connect to the second EC2 instance.

1
# Connect to the second EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_2_PUBLIC_IP

Create a database Replication

1
# Variables
2
ROOT_DB_PASSWORD="121612"
3
AWS_EC2_INSTANCE_1_PRIVATE_IP=''
4

5
# Create a database Replication
6
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CHANGE MASTER TO MASTER_HOST='$AWS_EC2_INSTANCE_1_PRIVATE_IP', MASTER_USER='replication', MASTER_PASSWORD='password', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=0;"
7
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "START SLAVE;"
8
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "SHOW SLAVE STATUS\G;"

Explanation:

The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CHANGE MASTER TO MASTER_HOST='$AWS_EC2_INSTANCE_1_PRIVATE_IP', MASTER_USER='replication', MASTER_PASSWORD='password', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=0;" command changes the master to the first EC2 instance.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "START SLAVE;" command starts the slave.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "SHOW SLAVE STATUS\G;" command shows the slave status.

Test the Replication

Step 1: Test the Replication

To test the replication, run the following command:

Connect to the first EC2 instance.

1
# Connect to the first EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_1_PUBLIC_IP
3

4
# Variables
5
ROOT_DB_PASSWORD="121612"
6

7
# Create a database MK LLC
8
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CREATE DATABASE MKLLC;"
9

10
# Create a table users
11
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; CREATE TABLE users (id INT NOT NULL AUTO_INCREMENT, FIRST_NAME VARCHAR(255) NOT NULL, LAST_NAME VARCHAR(255) NOT NULL, PRIMARY KEY (id));"
12

13
# Insert a record to the table users
14
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; INSERT INTO users (FIRST_NAME, LAST_NAME) VALUES ('John', 'Doe');"
15
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; INSERT INTO users (FIRST_NAME, LAST_NAME) VALUES ('Jane', 'Doe');"
16
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; INSERT INTO users (FIRST_NAME, LAST_NAME) VALUES ('Jack', 'Doe');"
17
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; INSERT INTO users (FIRST_NAME, LAST_NAME) VALUES ('Jill', 'Doe');"
18
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; INSERT INTO users (FIRST_NAME, LAST_NAME) VALUES ('Joe', 'Doe');"
19

20
# Select all records from the table users
21
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; SELECT * FROM users;"

Explanation:

The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "CREATE DATABASE MKLLC;" command creates a database MK LLC.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; CREATE TABLE users (id INT NOT NULL AUTO_INCREMENT, FIRST_NAME VARCHAR(255) NOT NULL, LAST_NAME VARCHAR(255) NOT NULL, PRIMARY KEY (id));" command creates a table users.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; INSERT INTO users (FIRST_NAME, LAST_NAME) VALUES ('FIRST_NAME', 'FIRST_NAME');" command inserts a record to the table users.
The sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; SELECT * FROM users;" command selects all records from the table users.
Connect to the second EC2 instance.

1
# Connect to the second EC2 instance
2
ssh -i aws-key-pair.pem ec2-user@$AWS_EC2_INSTANCE_2_PUBLIC_IP
3

4
# Variables
5
ROOT_DB_PASSWORD="121612"
6

7
# Select all records from the table users
8
sudo mysql -u root -p$ROOT_DB_PASSWORD -e "USE MKLLC; SELECT * FROM users;"

If the replication is successful, the command returns the following output:

1
+----+------------+-----------+
2
| id | FIRST_NAME | LAST_NAME |
3
+----+------------+-----------+
4
|  1 | John       | Doe       |
5
|  2 | Jane       | Doe       |
6
|  3 | Jack       | Doe       |
7
|  4 | Jill       | Doe       |
8
|  5 | Joe        | Doe       |
9
+----+------------+-----------+

The command tests the replication.

Why the Replication Matters

Replication gives you high availability, disaster recovery, data redundancy, and stronger data security.

Conclusion

In this article, you learned how to create a database replication on EBS and EFS. You also learned why the replication is important.

Resources

Was this useful?

Continue on this topic

AWS CLI

AWS Advanced: EC2, RDS, Lambda, CloudFormation

AWS EC2 Instance Management with Boto3: Start, Stop, and Query Instances

Migrating a Monolith to Kubernetes Without a Big-Bang Cutover

You might also enjoy