Use Cloud-Init to Write to a File
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Cloud-init is an industry-standard tool that automates server initialization and has cross-distribution, cross-platform support. While the cloud platform provides cloud-init with metadata for server deployment, custom user data lets you script almost every aspect of server initialization.
Akamai’s Metadata service allows you to leverage cloud-init to deploy Compute Instances. Using a cloud-config script, you can define everything you need, from security and user set up to software installation and shell script execution.
In this guide, learn how to use a cloud-config script to write files to your server during initialization. Automate the process of creating and editing files so that your software and system configurations are precisely as you need them from the start.
Before getting started, review our guide on how to Use Cloud-Init to Automatically Configure and Secure Your Servers. There, you can see how to create a cloud-config file, which you need to follow along with this guide. When you are ready to deploy your cloud-config, the guide linked above details how.
Write to a File
Cloud-init includes a module for writing files, using the write_files option within your cloud-config script. This module provides the simplest setup when you want to create a new file or overwrite an existing file during initialization.
By default, the write_files option takes a file path, creating a new file or overwriting an existing one at the given destination. Cloud-init also creates any parent directories that do not already exist.
Here is an example that creates an HTML file:
- File: cloud-config.yaml
1 2 3 4 5 6 7 8 9 10 11write_files: - path: /var/www/html/example.com/index.html content: | <html> <body> <h1>Hello, World!</h1> <p>Welcome to the example web page!</p> </body> </html> owner: 'root:root' permissions: '0644'
The example defines a set of file contents as well as details like ownership and permissions. Here is a deeper breakdown of what this example write_files configuration does:
pathpoints to the location for the created file. Any existing file at the location is overwritten, and parent directories are created as necessary. This is the one required option forwrite_files.contentdefines the content for the file. This can be a single line, or, as above, you can use appropriate YAML formatting for multi-line file content. Leaving out thecontentoption creates an empty file.owneroptionally lets you define a user and/or group to assign ownership of the file to. The default isroot:root. To specify a user and/or group created within the cloud-config script, you should use thedefer: trueoption, as described further below, to ensure the user/group is created before the file.permissionsoptionally specifies the file’s permissions. Use the format0###where###is an octal notation as used withchmod. You can learn more about permissions and octal notation in our guide on how to Modify File Permissions with chmod.Here,
permissionsgives the owner user read-write permission (6--), read permission for the user’s group (-4-), and read permission for all other users (--4).
An additional defer option can be useful when you want to delay creation of the file until the final stage of cloud-init’s initialization. That way, you can ensure that a file is only created after all user creation and software installation.
Here is a further example showing that feature off by creating an Apache Web Server configuration. Using the defer option ensures that Apache is installed and the Apache user (typically www-data on Debian and Ubuntu) is created before the file.
- File: cloud-config.yaml
1 2 3 4 5 6 7 8 9 10 11 12 13 14write_files: - path: /etc/apache2/sites-available/example.com.conf content: | <VirtualHost *:80> ServerAdmin webmaster@example.com ServerName example.com ServerAlias www.example.com DocumentRoot /var/www/example.com/html/ ErrorLog /var/www/example.com/logs/error.log CustomLog /var/www/example.com/logs/access.log combined </VirtualHost> owner: 'www-data:www-data' permissions: '0640' defer: true
Omitting the defer: true option above would result in an error since the www-data user would not yet exist at the time cloud-init attempts to create the file.
Modify a File
When you need to modify a file, cloud-init has a couple of approaches to use:
The
write_filesoption can achieve basic file modifications with itsappend: trueoption. For instance, the example below modifies the SSH service configuration by adding aPermitRootLogin norule:- File: cloud-config.yaml
1 2 3 4write_files: - path: /etc/ssh/sshd_config content: PermitRootLogin no append: true
Otherwise,
write_filescan only provide modifications by recreating the files. In that case, you would need to copy the whole configuration with your desired modifications into your cloud-config script.The more approachable and maintainable solution is to use cloud-init’s
runcmdoption to runsedcommands on the server.sedprovides text editing via shell commands, andruncmdlets you run shell commands from a cloud-init script. Learn more about usingruncmdin our guide Use Cloud-Init to Run Commands and Bash Scripts on First Boot and more aboutsedin our guide Manipulate Text from the Command Line with sed.The
runcmdoption takes a list of shell commands. In the example that follows, two shell commands run to change the SSH service configuration, similar to the example above. However,sedlets you replace existing settings, rather than just appending a new setting.- File: cloud-config.yaml
1 2 3runcmd: - sed -i -e 's/PermitRootLogin\s*yes/PermitRootLogin no/g' /etc/ssh/sshd_config - sed -i -e 's/#*\s*PermitRootLogin/PermitRootLogin/g' /etc/ssh/sshd_config
Each command in the
runcmdlist above makes an edit to the/etc/ssh/sshd_configfile. Together, these two command effectively switchPermitRootLogintonoand ensure that the setting is not commented out. The firstsedcommand replacesPermitRootLogin[any number of spaces]yeswithPermitRootLogin no, while the second removes the comment marker (#) from the beginning of any occurrences ofPermitRootLogin.
Verify File Contents
Once your instance is up and running, use the cat command to verify that files are written as expected. Using cat on a file’s location, you should see the contents of the file as dictated in the cloud-config.
cat /var/www/html/example.com/index.html<html>
<body>
<h1>Hello, World!</h1>
<p>Welcome to the example web page!</p>
</body>
</html>You can do the same for file modifications. However, you can make that check more efficient by limiting the output to matching terms. Here, the sshd_config contents are filtered to just the lines where cloud-init made changes (the ones containing PermitRootLogin).
cat /etc/ssh/sshd_config | grep PermitRootLoginPermitRootLogin noTo verify file permissions, use the stat command. In the case of the example.com.conf file from further above, look for the file to be owned by www-data and for the 0640 permission.
sudo stat /etc/apache2/sites-available/example.com.conf File: /etc/apache2/sites-available/example.com.conf
Size: 284 Blocks: 8 IO Block: 4096 regular file
Device: 800h/2048d Inode: 261541 Links: 1
Access: (0640/-rw-r-----) Uid: ( 33/www-data) Gid: ( 33/www-data)
...More Information
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on