<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Compute on Empowering European Innovation</title><link>https://beta.safespring.eu/tags/compute/</link><description>Recent content in Compute on Empowering European Innovation</description><generator>Hugo</generator><language>en-GB</language><copyright>2025 Safespring</copyright><lastBuildDate>Tue, 23 Jun 2026 18:40:00 +0200</lastBuildDate><atom:link href="https://beta.safespring.eu/tags/compute/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Windows Server Hardening on Safespring Compute: From Launch to Locked Down</title><link>https://beta.safespring.eu/deep-dive/automating-windows-server-hardening-on-safespring-compute-from-launch-to-locked-down/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://beta.safespring.eu/deep-dive/automating-windows-server-hardening-on-safespring-compute-from-launch-to-locked-down/</guid><description>&lt;p&gt;When you spin up a Windows Server instance in a cloud environment like Safespring Compute, you get a blank slate, no password, no SSH, no remote access at all.&lt;/p&gt;
&lt;p&gt;This post walks through the full automation chain: using cloudbase-init to bootstrap the instance at first boot, then running an Ansible playbook to apply a security baseline.&lt;/p&gt;
&lt;p&gt;The result is a fully hardened Windows Server you can provision in one shot, hands-off, from the OpenStack CLI.&lt;/p&gt;</description></item></channel></rss>