Infrastructure and cloud analyst
I build the platforms developers deploy on.
I work on the cloud team at Beneva, where we give developers a flexible, secure infrastructure for deploying applications on Kubernetes.
apiVersion: v1
kind: Analyst
metadata:
name: christopher-remillard
location: Montreal, QC
spec:
team: cloud
employer: Beneva
since: 2022-05
platform: [kubernetes, eks, aws]
automation: [ansible, terraform]
status:
phase: RunningExperience
-
May 2025 – Present
Infrastructure and cloud analyst
Beneva
Member of the cloud team. We give developers a flexible, secure infrastructure for deploying applications in a Kubernetes environment.
-
Aug. 2023 – May 2025
Technology analyst
Beneva
Member of the automation platform team. We maintained and evolved Ansible Automation Platform, and onboarded client teams into Ansible development.
-
Aug. 2022 – Aug. 2023
Programmer
Beneva
Part-time while continuing my university studies, I developed integrations for developers to make it easier to deploy their applications in the on-premise environment.
-
May 2022 – Aug. 2022
Intern
Beneva
Intern in on-premise infrastructure. Our mandate was to build automated virtual machine lifecycle management with Ansible.
Stack
- Cloud
- AWS
- GCP
- Platform
- EKS
- VMware
- Vault
- Ansible Automation Platform
- Automation
- Ansible
- Terraform
- Languages
- TypeScript
- Nix
Education
-
2020 – 2023
Bachelor’s in computer science and software engineering
Université du Québec à Montréal
-
2018 – 2020
Certificate in administration
Université du Québec à Montréal
Selected projects
-
Full virtual machine lifecycle with Ansible
My internship project at Beneva. Getting a virtual machine meant waiting for system administrators to build it by hand with scripts. Now a Jira form triggers an Ansible workflow that delivers a ready-to-use Linux or Windows machine in VMware, and a second form deletes it when it is no longer needed.
- Before
- About 2 weeks
- After
- 20 minutes
-
Signed SSH certificates with HashiCorp Vault
On the team running Ansible Automation Platform, the automation service accounts reached virtual machines with static SSH keys: highly privileged, hard to track, and hard to rotate. I automated SSH key signing with HashiCorp Vault. No static key is deployed any more, only certificates issued by the internal Vault.
- Before
- Static SSH keys
- After
- Vault-signed certificates
-
Ephemeral namespaces on EKS
I worked on the project that built ephemeral namespaces for EKS. A GitHub Actions workflow creates a namespace and deploys developers’ Helm charts straight into it. After 48 hours at most it is gone, so nothing lingers in the clusters. We also automated the AWS access entries that connect each team’s repositories to the clusters it deploys to.
- Namespace lifetime
- 48 hours max
- Deployed from
- GitHub Actions
2025 · Réseau Action TI
Octas winner, Digital transformation — Large enterprise.
Awarded to Beneva for the project « L’usine d’automatisation des fondations TI : là où l’innovation crée de la valeur ».
In the video, a member of our team explains the project.