Generate user-data and network-config for automated Linux cloud instance setup
Core identity and locale settings written to the instance on first boot.
Configure user accounts, SSH keys, and authentication settings.
openssl passwd -6 (prompts you to type the password, outputs the hash).Keys added here are injected into the default cloud user (e.g. ubuntu, ec2-user). One key per line.
Configure network interfaces. Generates a separate network-config file (cloud-init network v2 / Netplan format).
Install packages and configure repositories on first boot.
Configure additional disk mounts and swap space. The root filesystem is handled automatically.
/etc/fstab. Use nofail for non-critical mounts to prevent boot failures if the device is absent. NFS/CIFS mounts automatically get _netdev so they wait for the network before mounting.Create or overwrite files on the instance during cloud-init. Runs before runcmd.
Commands that run on every boot very early, before cloud-init modules. Must be idempotent.
Commands that run once on first boot after all cloud-init modules complete. Use for application setup.
/bin/sh -c so shell features like pipes and redirects work.Create custom systemd unit files (services, timers, sockets, etc). Cloud-init writes the unit file and runs daemon-reload plus enable/start via runcmd automatically. Service units can be built with a guided form or pasted as raw text â switching back to Guided regenerates the file from the form fields, discarding manual edits.
Configure Network Time Protocol servers.
Post-init message and power state action.
Review your configuration, then generate the cloud-init files.