Restart the AWS Replication Agent automatically without disabling SELinux after rebooting a RHEL source server

Create an Application Migration Service user with an access key and a secret access key.

To install the AWS Replication Agent, you must create an Application Migration Service user with the required AWS credentials. For instructions, see the Application Migration Service documentation.

Install the AWS Replication Agent.

Restart or reboot the RHEL source server.

Restart or reboot your RHEL source server when its Data replication status displays Stalled on the Migration dashboard.

Check data replication status.

Wait for one hour and then check the Data replication status again on the Migration dashboard. It should be in the Healthy state.

Identify the system version.

Open the command line interface for your RHEL source server and run the following command to identify the system version:

#systemctl –version

List all active services.

To list all active services available on the RHEL server, run the command:

#systemctl list-units --type=service

List all running services.

To list all services that are currently running on the RHEL server, use the command:

#systemctl list-units --type=service | grep running

List all services that failed to load.

To list all services that failed to load after the RHEL server rebooted or restarted, run the command:

#systemctl list-units --type=service | grep failed

Change the security context.

In the command line interface for your RHEL source server, run the following command to change the security context to the AWS replication service:

restorecon -Rv /etc/rc.d/init.d/aws-replication-service

Install core utilities.

To install the core utilities required for the operation of the SELinux system and its policies, run the command:

yum install policycoreutils*

Search the audit log and create a module for policies.

Run the command:

ausearch -c "insmod" --raw | audit2allow -M my-modprobe

Display the contents of the my-modprobe-te file.

The my-modprobe.te file is generated by the audit2allow command. It includes the SELinux domains, policy source directory, and subdirectories, and specifies the access vector rules and transitions associated with the domains. To display the contents of the file, run the command:

cat my modprobe.te

Activate the policy.

To insert the module and make the policy package active, run the command:

semodule -i my-modprobe.pp

Check whether the module has been loaded.

Run the command:

semodule -l | grep my-modprobe

After the SELinux module is loaded, you will no longer have to set SELinux to disabled or permissive mode during your migration.

Reboot or restart the RHEL source server and verify the data replication status.

Open the AWS Migration Service console, navigate to Data replication progress, and then reboot or restart your RHEL source server. Data replication should now resume automatically after the RHEL source server reboots.