/░████\    /░█                        
           /░█░_  ░█  | ░█                        
 /░██████\| ░█ ░\ ░█ /░█████    /░█████\  /░█████\
| ░█__  ░█| ░█  ░ ░█|_  ░█_/   /░█__  ░█ /░█_____/
| ░█  \ ░█| ░█\  ░░█  | ░█    | ░██████|  ░█████  
| ░█  | ░█| ░█ \  ░█  | ░█ /░█| ░█_____/ \____  ░ 
| ░█  | ░█|  ░█████/  |  ░███/|  ░█████░ /░█████░/
|__/  |__/ \______/    \____/  \_______/|_______/ 

How I set up an automated backup system for Ansible Automation Platform (AAP) using the containerized installer. The script and the crontab setup run a daily backup, store it on a remote NFS location, and clean up older backups over time. The backup script must be launched using the dedicated non-root user (in this case, aap). This user also needs access to the AAP installation directory, since the backup command has to be run from there. PrerequisesPackagesYou have to install the following pack

Logging in with the dedicated non-root user account (here, aap) to perform a backup and access the automation platform’s installation directory is required. To control the compression of backup files before sending them to the host running the operation, you can use specific variables in the inventory file. Inventory file optionConnect to the aap user ang go to the installation directory then open the inventory-growth file: $ cd MyInstallDir$ vim inventory-growth Then add the following configu

How to install Ansible Automation Platform 2.6 (AAP) using the Containerized All-in-One Bundle in an offline environment.This installation focuses on the offline, containerized installation method, where all required components, including the Controller, Automation Hub, Automation Gateway, and Event-Driven are deployed via pre-packaged containers, without requiring direct internet access. Download the installation programGo to https://access.redhat.com/downloads/content/480/ver=2.6/rhel---9/2.6/

Il arrive parfois que les commandes Podman échouent pour un utilisateur rootless. Ce problème survient lorsque le répertoire runtime rootless de l’utilisateur n’est pas accessible ou possède de mauvaises permissions. Failed to obtain podman configuration: mkdir /run/user/XXXX/libpod: permission denied Origine du problèmePodman rootless utilise le répertoire $XDG_RUNTIME_DIR pour stocker ses données et sockets temporaires (libpod, run, etc.). Par défaut, ce répertoire se situe dans /run/user/&l

If you have a certificate problem with your AAP webGUI. Add a certificate1/ DL on your AAP server the certificates (probably a files named like the following: AAP-Server.your.company.org.key.pem and AAP-Server.your.company.org.cert.pem) 2/ In your /etc/tower folder you should have some old certificates, rename them and put your news certificates with the same name: # cp /etc/tower/tower.cert /etc/tower/tower.cert-$(date +%F)# cp /etc/tower/tower.key /etc/tower/tower.key-$(date +%F)# rm /etc/towe

A bash script for backup some configuration files on a distant volume. PrerequiesYou need at least this packages: # yum install nfs-utils# yum intall s-nail // for send mails You need to edit your /etc/fstab and add the following line: nfs-stockage.my.company.org:/backups/aap /mnt/aap-backups nfs defaults 0 0 You can add a cron like this (every monday at 8am): 0 8 * * 1 /root/AAP-scripts/backup-config.sh | mailx -v -s "[AAP] - Backup of $HOSTNAME" -S smtp=mail.m

The ability to backup and restore your system is integrated into the platform setup playbook. TL;DRSummary: # ./setup.sh -b // backup# ./setup.sh -r // restore# ./setup.sh -e 'backup_dest=/path/to/backup_dir/' -b // backup in a specific folder# ./setup.sh -e 'restore_backup_file=/path/to/nondefault/backup.tar.gz' -r // restore from a speficic file Make a backupSimple BackupYou make a backup using the same setup.sh script that you use to in