Debian AMI boots into runlevel 5 by default

[Tim Sattarov <stimur@gmail.com>]

Hello Debian-Cloud !

I've noticed that Debian images in the AWS boot into runlevel 5 by default, which is incorrect (it
should be 3) and might potentially lead to issues with some services.

root@ip-172-19-1-122:~# ec2metadata --ami-id
ami-fa0bb29e

root@ip-172-19-1-122:~# runlevel
N 5
root@ip-172-19-1-122:~# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @13.747s
└─multi-user.target @13.739s
  └─ssh.service @13.295s +438ms
    └─basic.target @13.118s
      └─sockets.target @13.110s
        └─dbus.socket @13.106s
          └─sysinit.target @13.074s
            └─cloud-init.service @10.796s +2.264s
              └─networking.service @8.278s +2.513s
                └─network-pre.target @8.271s
                  └─cloud-init-local.service @2.338s +5.930s
                    └─systemd-remount-fs.service @2.055s +281ms
                      └─systemd-journald.socket @2.053s
                        └─-.slice @1.827s

Is it Debian(systemd) problem in general or specific to cloud images ?
Thanks !