Scaleway's standard kernel for Debian 8 (Jessie) has no AES-NI active.
If you try to load the module, you'll get an error message.
This is not due to a hardware limitation, the 2/4/8 core Atom systems support AES perfectly fine.
It's also not a Debian issue.
What's missing is the whole kernel module support, because Scaleway runs a modified kernel and they didn't enable the module.
To enable it, you just have to change the kernel you're running, like this:
In your server's properties there's a hidden menu to modify the boot environment:
Change the kernel
Select and safe the 4.5.7 kernel which is recent enough to include their bugfix.
Restart your server to load the newer kernel
After the reboot verify if the module is available
As you can see the module still wasn't loaded automatically, but I think this is default behavior of most distros.
Add it to your /etc/modules as you like - I just wanted to make sure you know how to get the module.
I've been working with various IT things for almost my whole life. It'll never stop entertaining me how people always make an "advanced settings" menu.
As a normal user you're not even really supposed to need it. Often enough it's even unsupported to modify anything in it.
Yet, it's always this place where you need to fiddle around to get things really right.
I suggest for the future we just rename "Advanced" to "Oops" or "Sorry!"
I had a problem with booting because an external disk would not attach, thanks to systemd that of course turned out fatal...
- there is a rescue bootscript, it'll bring up a base ubuntu accessible with your configured ssh key. you then mount your /dev/nbd0 and chroot to it.
- set a root password if you're messing with fstab, kernels, etc. to allow you to login via the console
- scw attach to get to the console
- (change laws so it is legal to beat up systemd advocates until they start ssh before mounting secondary filesystems)
- scw reboot to restart your server
- system once started with 4.5.7 kernel and 4.5.1 modules or vise versa. in either case, the xfs kernel module was missing, and thus no filesystems could be mounted
- system once hung when attaching nbd0 - I waited a few minutes just in case and then rebooted (hard reboot via panel), which sorted things.