During these days, schools are closed due to the emergency for COVID-19, and staff quickly reorganized to work from home. Teachers began to carry out distance learning, so the pupils and parents also used our application Nuvola more assiduously, and…
In our daily work we often have the need to plan periodic or recurring activities. In the past this activity has always been managed using cron. This obliges us, always, to have a server on which to schedule activities. In…
In this article we will describe how we have automated a workflow thanks to the services managed by Amazon AWS. This has allowed us to have a unique and centralized service that can be managed by anyone. Let’s come to…
When we started developing Lambda functions to automate processes, or simply to delegate various jobs, compared to our infrastructure, we faced the problem of how to handle the deploy of functions and maintain the versions of this code. There are…
Negli ultimi anni, gli amministratori di sistema sempre più spesso sentono l’esigenza di trovare strumenti per difendersi da attacchi DoS o DDoS. La diffusione di questo tipo di attacchi in futuro sarà sempre maggiore al crescere della capacità di banda…
Il servizio AWS S3 (Simple Storage Service) è nato e si è diffuso per la sua caratteristica di essere uno storage ad oggetti, semplice da usare, sicuro e, in alcuni casi, anche economico. I nostri oggetti presenti su S3 possono essere…
In the previous articles we created our infrastructure on AWS and configured the services. All this using Ansible and creating an infrastructure as code. In this article we will describe the steps we have followed to migrate our infrastructure to AWS. Warm…
In the previous articles we created our infrastructure on AWS and configured the services. All using Ansible and creating an infrastructure as code. When the number of servers or services grows, keeping track of their names clearly can be complicated. This…
In the previous article we showed you how we created our infrastructure as code. This article describes how to configure services within our EC2 instances. Provision Backend Let’s start with a bash script to run the playbooks:
|
1 2 3 4 5 6 7 8 |
./provision_nuvola_backend.sh --limit "tag_nuvola_type_${ENV}_backend" ./provision_nuvola_dbserver.sh --limit "tag_nuvola_type_${ENV}_database" ./provision_nuvola_routine.sh --limit "tag_nuvola_type_${ENV}_routine" if [ "$ENV" != "prod" ]; then ./nuvola-init-not-prod-env.sh --env ${ENV} ./deploy_nuvola.sh --limit "tag_nuvola_type_${ENV}_backend" --env ${ENV} fi |
Here is the playbook…
In the previous article we described the reasons that made us change the provider. In this article we will describe how we built our infrastructure as code. As a first step let’s create a bash script to run the playbook:
|
1 2 3 4 5 6 7 8 9 10 11 |
:~$ ./infrastructure_nuvola_env_aws.sh --env prod #!/bin/bash . libs/extra_option_parser.sh … ansible-playbook --vault-password-file secrets/infrastructure_nuvola_env.secret \ ansible/infrastucture_nuvola_env.yml \ -e"$EXTRA_OPTIONS" |
With…
