Provisioning Fedora CoreOS on Amazon Web Services

This guide shows how to provision new Fedora CoreOS (FCOS) instances on the Amazon Web Services (AWS) cloud platform.


Before provisioning an FCOS machine, you must have an Ignition configuration file containing your customizations. If you do not have one, see Producing an Ignition File.

If you do not want to use Ignition to get started, you can make use of the Afterburn support and provide an SSH key via the cloud provider and continue from there.

You also need to have access to an AWS account. The examples below use the aws command-line tool, which must be separately installed and configured beforehand.

Launching a VM instance

Las nuevas instancias AWS pueden ser creadas y arrancadas directamente desde imágenes FCOS públicas. Puede encontrar la última AMI para cada región de Update Streams, que tambien se puede ver en la download page.

Si está interesado en explorar FCOS sin más personalización, puede usar directamente un par de claves registradas SSHpara el usuario core predeterminado.

Para probar FCOS de esta manera, sseleccione simplemente el par de claves SSH pertinente por medio de --key-name cuando lanza la nueva instancia:

Lanzando una nueva instancia
aws ec2 run-instances <other options> --image-id <ami> --key-name "${SSH_KEY_NAME}"

In order to launch a customized FCOS instance, a valid Ignition configuration must be passed as its user data at creation time:

Launching and customizing a new instance
aws ec2 run-instances <other options> --image-id <ami> --user-data file://example.ign
By design, cloud-init configuration and startup scripts are not supported on FCOS. Instead, it is recommended to encode any startup logic as systemd service units in the Ignition configuration.