...

In order to make an EFS backup right away we need to navigate into AWS Backup service.

...

We then must go directly into Site administration → plugins → caching → configuration

Alternatively we can go directly with /cache/admin.php

in Configured store instances table we edit redis_all and on the server input we put the one we have for our cloned website. eg dev-courses[…]amazonaws.com

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.

...

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

In allowedUsers array we put the user id’s we want to have access. This code is entered right after the authenticate_user_login function

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

Extra Steps (

...

SMTP, CRONS, Alternate login URL)

For safety reasons since this is a clone instance of another website ( MoodleIf we want to use it for test ), it’s better if we disable SMTP and Crons so that we don’t send any notifications in the public accidentally.

Alternate login URL

We must change the alternate URL and input the one of the cloned theme (if it was changed).

Go to Site administration → Plugins → Authentication → Manage authentication

Find Alternate login URL and change it eg. dev.courses…

SMTP

Go to Site administration → Server → Email → Outgoing mail configuration

change SMTP hosts, username, password.

CRONS

Go to Site administration → Server → Tasks → Task Processing

Uncheck Enable cron