# systemd-analyze verify nm-cloud-setup.service
/usr/lib/systemd/system/nm-cloud-setup.service:19: Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.
# systemctl status nm-cloud-setup
○ nm-cloud-setup.service - Automatically configure NetworkManager in cloud
     Loaded: loaded (/usr/lib/systemd/system/nm-cloud-setup.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/nm-cloud-setup.service.d
             └─10-rh-enable-for-ec2.conf
     Active: inactive (dead) since Mon 2024-09-02 05:59:39 UTC; 14s ago
TriggeredBy: ● nm-cloud-setup.timer
       Docs: man:nm-cloud-setup(8)
    Process: 905 ExecStart=/usr/libexec/nm-cloud-setup (code=exited, status=0/SUCCESS)
   Main PID: 905 (code=exited, status=0/SUCCESS)
        CPU: 59ms

Sep 02 05:59:39 ip-10-116-2-252.us-west-2.compute.internal systemd[1]: Starting Automatically configure NetworkManager in cloud...
Sep 02 05:59:39 ip-10-116-2-252.us-west-2.compute.internal systemd[1]: nm-cloud-setup.service: Deactivated successfully.
Sep 02 05:59:39 ip-10-116-2-252.us-west-2.compute.internal systemd[1]: Finished Automatically configure NetworkManager in cloud.
#  systemctl cat  nm-cloud-setup
# /usr/lib/systemd/system/nm-cloud-setup.service
[Unit]
Description=Automatically configure NetworkManager in cloud
Documentation=man:nm-cloud-setup(8)
Before=network-online.target
After=NetworkManager.service

[Service]
Type=oneshot
ExecStart=/usr/libexec/nm-cloud-setup

# The service restart gets triggered from dispatcher script
# (pre-up and dhcp4-change actions), possibly ending up with many
# restart requests at the same time (e.g. on initial daemon startup
# on a machine with multiple NICs). The systemd handles multiple
# concurrent restart requests gracefully (the newer requests supersede
# older, which wait for them to finish), but the default limits are way
# too low: 5 restarts in 10 seconds. Raise that high enough for us to
# be on the safe side.
StartLimitIntervalSec=1
StartLimitBurst=100

#Environment=NM_CLOUD_SETUP_LOG=TRACE

# Cloud providers are disabled by default. You need to
# Opt-in by setting the right environment variable for
# the provider.
#
# Create a drop-in file to overwrite these variables or
# use systemctl edit.
#Environment=NM_CLOUD_SETUP_EC2=yes
#Environment=NM_CLOUD_SETUP_GCP=yes
#Environment=NM_CLOUD_SETUP_AZURE=yes
#Environment=NM_CLOUD_SETUP_ALIYUN=yes

CapabilityBoundingSet=
KeyringMode=private
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
PrivateDevices=yes
PrivateTmp=yes
PrivateUsers=yes
ProtectClock=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectHostname=yes
ProtectKernelLogs=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
ProtectProc=invisible
ProtectSystem=strict
RestrictNamespaces=yes
RestrictRealtime=yes
RestrictSUIDSGID=yes
SystemCallArchitectures=native

DevicePolicy=closed
PrivateNetwork=no
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallFilter=@system-service

[Install]
WantedBy=NetworkManager.service

# /usr/lib/systemd/system/nm-cloud-setup.service.d/10-rh-enable-for-ec2.conf
[Service]
Environment=NM_CLOUD_SETUP_EC2=yes