OVHcloud best practices: organization, security, networking, backup and costs

1. Organization and access #

The foundations.

Rules #

• One Public Cloud project per environment.
• 2FA on the account; IAM and dedicated OpenStack users per tool.
• API keys limited in rights and duration.

2. Network, security, backup #

Protecting and holding up.

Rules #

• Instances without public addresses, behind a Load Balancer and a Gateway.
• Security groups kept tight; administration through a bastion or VPN.
• Backups and images replicated in another region; tested restore.
• Automatic security updates on instances.

3. Operations and costs #

Lasting without drifting.

Rules #

• Everything in Terraform, state in Object Storage, deployment through a pipeline.
• Logs in Logs Data Platform or a Grafana stack.
• Monthly billing for permanent resources, deletion of orphaned resources.

openstack server list --long -c Name -c Status -c Networks
openstack volume list --status available            # volumes non attachés (coût inutile)
openstack floating ip list --status DOWN              # IP non utilisées
openstack security group rule list --ingress | grep 0.0.0.0/0
openstack image list --private --sort-column Created_At