- Home
- Skills
- DevOps & Cloud
- Cloud-init User-data Check
More screenshots
Works with the AI Agents you already use
Cloud-init User-data Check
And "# cloud-config" with one extra space makes cloud-init skip the whole file without an error, so none of your users, keys or security settings are applied.
$5
Cloud-init User-data Check
Example session with this skill installed
Check this project with cloud-init-userdata-check.
- Read your context and instructions
- Compiled the cloud-init user-data check
$ python3 scripts/check_cloud_init.py examples/risky
BLOCK cloud-init/web.yaml:9 C02 SSH_PASSWORD_LOGIN_ON
ssh_pwauth: true
Why: SSH password login is turned on (ssh_pwauth: true, or PasswordAuthentication yes in an sshd_config file or command) and an account gets a usable password (root counts only with PermitRootLogin yes: OpenSSH's default has been prohibit-password since 7.0, though some images set yes). Internet-facing SSH servers get password-guessing attempts within minutes, and a password or hash that sits in user-data can be read on the instance and cracked offline. Most cloud images ship with password login off for this reason.
Safer: Set ssh_pwauth: false (or leave it out) and log in with SSH keys. If someone needs a password for emergencies, use the provider's serial console and keep SSH password login off.
BLOCK cloud-init/web.yaml:25 C01 PLAIN_TEXT_PASSWORD
BLOCK cloud-init/web.yaml:41 C04 PRIVATE_KEY_OR_SECRET
BLOCK cloud-init/web.yaml:52 C04 PRIVATE_KEY_OR_SECRET
BLOCK cloud-init/web.yaml:57 C03 CODE_FETCHED_WITHOUT_TLS
REVIEW cloud-init/web.yaml:16 C14 PASSWORD_LOGIN_UNLOCKED
REVIEW cloud-init/web.yaml:18 C13 BROAD_PASSWORDLESS_SUDO
REVIEW cloud-init/web.yaml:25 C12 ROOT_LOGIN_ALLOWED
REVIEW cloud-init/web.yaml:30 C15 INTEGRITY_CHECK_OFF
REVIEW cloud-init/web.yaml:36 C13 BROAD_PASSWORDLESS_SUDO
REVIEW cloud-init/web.yaml:38 C16 WRITE_FILES_MODE_RISK
REVIEW cloud-init/web.yaml:43 C16 WRITE_FILES_MODE_RISK
REVIEW cloud-init/web.yaml:58 C15 INTEGRITY_CHECK_OFF
REVIEW infra/main.tf:17 C12 ROOT_LOGIN_ALLOWED
REVIEW infra/main.tf:20 C11 REMOTE_SCRIPT_RUN_UNVERIFIED
REVIEW seed/user-data:1 C17 CLOUD_CONFIG_NOT_RECOGNIZED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 3 files, 3 with cloud-config content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
chpasswd with ubuntu:changeme and ssh_pwauth: true gives every new server a login password that other users and processes on it can often read from the metadata service, and opens SSH to password guessing. And "# cloud-config" with one extra space makes cloud-init skip the whole file without an error, so none of your users, keys or security settings are applied. This skill finds those and the other cloud-init mistakes below before you launch, and tells you how to fix each one.
Your agent runs a scanner on #cloud-config files, cloud.cfg.d files, Ubuntu autoinstall files, files named like user-data, and cloud-config embedded in Terraform heredocs, CloudFormation UserData, KubeVirt, LXD profiles and Vagrantfiles. It knows cloud-init's defaults (passwords locked, root login off, chpasswd type hash), the hash formats the legacy chpasswd list accepts, the legacy hyphenated keys, and Terraform cloudinit_config parts that need no header; it decodes base64 and gzip write_files content and treats template placeholders as set but unknown. It never runs cloud-init or the commands. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- C01: passwords in clear text (plain_text_passwd, chpasswd text or legacy list, password, a plain value where a hash belongs, the autoinstall identity password, and commands such as echo or printf into chpasswd or passwd, chpasswd <<< and openssl passwd with a literal)
- C02: SSH password login turned on (ssh_pwauth, PasswordAuthentication yes) while an account gets a usable password (a root-only password counts only with PermitRootLogin yes, since OpenSSH defaults to prohibit-password)
- C03: code run as root that is fetched over plain HTTP or with certificate checks off: curl or wget piped into a shell (also through tee) or saved and then run, made executable or installed with dpkg, rpm or apt, rpm or dnf installs from http URLs, apt trusted=yes or yum/zypper gpgcheck off over http, executable write_files sources, Ansible, Puppet and Chef installer URLs
- C04: private keys and credentials in user-data: PEM keys (also in base64 or gzip content and ssh_keys), known token formats, passwords in URLs, Authorization headers, WireGuard keys, secret-named settings, and secrets on command lines (docker or az login -p, --token, htpasswd -b, rabbitmqctl add_user and others)
REVIEW
- C11: scripts or packages downloaded over https and run or installed with no checksum or signature check
- C12: root login allowed (disable_root: false, root users entry or password, PermitRootLogin yes)
- C13: NOPASSWD sudo for every user, a group, a system account or a user who also has a password, in users entries or sudoers files written by write_files or echo/tee (key-only admins are not reported)
- C14: lock_passwd: false for a user who gets a password
- C15: TLS or signature checks off over https (curl -k, apt trusted=yes, gpgcheck off, --allow-unauthenticated, snap --dangerous, pip --trusted-host and others)
- C16: write_files modes that everyone can write, or an unquoted mode like 644 that YAML reads as decimal
- C17: files cloud-init will not read as cloud-config (misspelled header, also inside a heredoc, a comment or --- before it, no header at all, a byte-order mark or UTF-16)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official documentation link for each rule
- A risky and a safe example project (cloud-config, Terraform and a NoCloud seed), and the real report the scanner produces on the risky one
Limits It reads each file as written. Values a template fills in (Terraform, Jinja, Helm) are unknown, MIME multi-part user-data, #include URLs, compressed user-data, user-data shell scripts and vendor-data are not read, and cloud-config stored as a JSON string is not found. Shell commands are matched by pattern, not parsed. Ubuntu Pro tokens and Red Hat activation keys are not reported. Some official cloud-init examples are reported on purpose because they show a plain password, an account password, a Basic auth header, a demonstration private key or a host private key in user-data. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Static check of user-data text. Settings that come from the cloud (metadata, vendor-data, image defaults) and values filled in by templates are not seen. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Accounts
0
Permissions
Allowed Hosts
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes a clearly fake, inert password, token and private key (not-a-real-..., NOT-A-REAL-KEY-EXAMPLE) for the scanner to find. Nothing in it is run.