nixpkgs/nixos/modules/services/misc/amazon-ssm-agent.nix

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

77 lines
2.5 KiB
Nix
Raw Normal View History

2017-02-13 04:01:28 +00:00
{ config, pkgs, lib, ... }:
let
cfg = config.services.amazon-ssm-agent;
2017-02-13 04:01:28 +00:00
# The SSM agent doesn't pay attention to our /etc/os-release yet, and the lsb-release tool
# in nixpkgs doesn't seem to work properly on NixOS, so let's just fake the two fields SSM
# looks for. See https://github.com/aws/amazon-ssm-agent/issues/38 for upstream fix.
fake-lsb-release = pkgs.writeScriptBin "lsb_release" ''
#!${pkgs.runtimeShell}
2017-02-13 04:01:28 +00:00
case "$1" in
-i) echo "nixos";;
-r) echo "${config.system.nixos.version}";;
2017-02-13 04:01:28 +00:00
esac
'';
2023-10-22 19:55:05 +00:00
sudoRule = {
users = [ "ssm-user" ];
commands = [ { command = "ALL"; options = [ "NOPASSWD" ]; } ];
};
2017-02-13 04:01:28 +00:00
in {
imports = [
(lib.mkRenamedOptionModule [ "services" "ssm-agent" "enable" ] [ "services" "amazon-ssm-agent" "enable" ])
(lib.mkRenamedOptionModule [ "services" "ssm-agent" "package" ] [ "services" "amazon-ssm-agent" "package" ])
];
options.services.amazon-ssm-agent = {
enable = lib.mkEnableOption "Amazon SSM agent";
package = lib.mkPackageOption pkgs "amazon-ssm-agent" {};
2017-02-13 04:01:28 +00:00
};
config = lib.mkIf cfg.enable {
# See https://github.com/aws/amazon-ssm-agent/blob/mainline/packaging/linux/amazon-ssm-agent.service
systemd.services.amazon-ssm-agent = {
2017-02-13 04:01:28 +00:00
inherit (cfg.package.meta) description;
wants = [ "network-online.target" ];
after = [ "network-online.target" ];
2017-02-13 04:01:28 +00:00
wantedBy = [ "multi-user.target" ];
path = [
fake-lsb-release
pkgs.coreutils
"/run/wrappers"
"/run/current-system/sw"
];
2017-02-13 04:01:28 +00:00
serviceConfig = {
2020-06-26 10:15:08 +00:00
ExecStart = "${cfg.package}/bin/amazon-ssm-agent";
2017-02-13 04:01:28 +00:00
KillMode = "process";
# We want this restating pretty frequently. It could be our only means
# of accessing the instance.
Restart = "always";
RestartPreventExitStatus = 194;
RestartSec = "90";
2017-02-13 04:01:28 +00:00
};
};
2020-09-28 23:15:36 +00:00
# Add user that Session Manager needs, and give it sudo.
# This is consistent with Amazon Linux 2 images.
2023-10-22 19:55:05 +00:00
security.sudo.extraRules = [ sudoRule ];
security.sudo-rs.extraRules = [ sudoRule ];
2020-09-28 23:15:36 +00:00
# On Amazon Linux 2 images, the ssm-user user is pretty much a
# normal user with its own group. We do the same.
users.groups.ssm-user = {};
users.users.ssm-user = {
isNormalUser = true;
group = "ssm-user";
};
environment.etc."amazon/ssm/seelog.xml".source = "${cfg.package}/etc/amazon/ssm/seelog.xml.template";
environment.etc."amazon/ssm/amazon-ssm-agent.json".source = "${cfg.package}/etc/amazon/ssm/amazon-ssm-agent.json.template";
2017-02-13 04:01:28 +00:00
};
}