...

After using the command the EFS should be attached into our instance and ready to be used right away.

In case the EFS does not mount probably we need to change the subnet ID of the instance.

Some additional commands:

...

Go through the file and make sure we didn’t forget to use the path anywhere else.

First Sign in

Inside config.php we need to include alternate url so that it won’t navigate into the previous website.

$CFG->alternateloginurl="https://dev.courses.unic.ac.cy/pages/login.php";

After signing in we comment out the $CFG->alternateurl and we go into the Manage authentication page in moodle. We search for Alternate login URL and we set there the URL we want the website to have. This is so the alternate url to be saved into the database.

Make sure Redis cache is correct in Moodle application

...

This is an important step as if it’s not configured then changes that are suppose to happen in cloned website will be done into the previous website because of redis caching.

Forbid Access to all users except

...

specific ones

We want to avoid random users to log into the cloned website that’s why we edit moodle/login/index.php

...

    $allowedUsers = [];
    if (FALSE == (in_array( $user->id, $allowedUsers ))){   
        die('Access Denied');
    }

Configure AWS EC2 services

All these changes will be implemented only to the instance that we will be working on until the clone is finished. After we finish we need to take an AMI of the instance we worked with. In load Balancers we need to update the target group and also in Auto Scaling we need to set a new version for Launch template in order to use the latest AMI.

Extra Steps (SMTP, CRONS, Alternate login URL)

...