fedora-docs-l10n/fedora-coreos/master/pages/provisioning-aws — Spanish @ Fedora Weblate: NAME='instance1' SSHKEY='my-key' # the name of your SSH key: `aws …

Translation

English type: delimited block -

NAME='instance1'
SSHKEY='my-key' # the name of your SSH key: `aws ec2 describe-key-pairs`
IMAGE='ami-xxx' # the AMI ID found on the download page
DISK='20' # the size of the hard disk
REGION='us-east-1' # the target region
TYPE='m5.large' # the instance type
SUBNET='subnet-xxx' # the subnet: `aws ec2 describe-subnets`
SECURITY_GROUPS='sg-xx' # the security group `aws ec2 describe-security-groups`
USERDATA='/path/to/config.ign' # path to your Ignition config
aws ec2 run-instances \
--region $REGION \
--image-id $IMAGE \
--instance-type $TYPE \
--key-name $SSHKEY \
--subnet-id $SUBNET \
--security-group-ids $SECURITY_GROUPS \
--user-data "file://${USERDATA}" \
--tag-specifications "ResourceType=instance,Tags=[{Key=Name,Value=${NAME}}]" \
--block-device-mappings "VirtualName=/dev/xvda,DeviceName=/dev/xvda,Ebs={VolumeSize=${DISK}}"

Spanish

NAME='instance1'
SSHKEY='my-key'     # the name of your SSH key: `aws ec2 describe-key-pairs`
IMAGE='ami-xxx'     # the AMI ID found on the download page
DISK='20'           # the size of the hard disk
REGION='us-east-1'  # the target region
TYPE='m5.large'     # the instance type
SUBNET='subnet-xxx' # the subnet: `aws ec2 describe-subnets`
SECURITY_GROUPS='sg-xx' # the security group `aws ec2 describe-security-groups`
USERDATA='/path/to/config.ign' # path to your Ignition config
aws ec2 run-instances                     \
    --region $REGION                      \
    --image-id $IMAGE                     \
    --instance-type $TYPE                 \
    --key-name $SSHKEY                    \
    --subnet-id $SUBNET                   \
    --security-group-ids $SECURITY_GROUPS \
    --user-data "file://${USERDATA}"      \
    --tag-specifications "ResourceType=instance,Tags=[{Key=Name,Value=${NAME}}]" \
    --block-device-mappings "VirtualName=/dev/xvda,DeviceName=/dev/xvda,Ebs={VolumeSize=${DISK}}"

Needs editing

Skip

	English	Spanish	Actions
	Provisioning Fedora CoreOS on Amazon Web Services	Aprovisionando Fedora CoreOS en Servicios Amazon Web
	This guide shows how to provision new Fedora CoreOS (FCOS) instances on the Amazon Web Services (AWS) cloud platform.	Esta guía le muestra como aprovisionar nuevas instancias Fedora CoreOS (FCOS) sobre la plataforma en la nube Servicios Amazon Web (AWS).
	Prerequisites	Requisitos previos
	Before provisioning an FCOS machine, you must have an Ignition configuration file containing your customizations. If you do not have one, see xref:producing-ign.adoc[Producing an Ignition File].	Antes de aprovisionar una máquina FCOS, usted debe tener un archivo de configuración Ignition que contenga sus personalizaciones. Si no tiene uno vea xref:producing-ign.adoc[Produciendo un Archivo Ignition].
	Fedora CoreOS has a default `core` user that can be used to explore the OS. If you want to use it, finalize its xref:authentication.adoc[configuration] by providing e.g. an SSH key.	Fedora CoreOS tiene un usuario `core` predeterminado que puede ser usado para explorar el SO. Si usted desea utilizarlo finalice su xref:authentication.adoc[configuración] proporcionando una clave SSH.
	If you do not want to use Ignition to get started, you can make use of the https://coreos.github.io/afterburn/platforms/[Afterburn support].	Si no desea usar Ignition para empezar, puede usar https://coreos.github.io/afterburn/platforms/[Soporte Afterburn].
	You also need to have access to an AWS account. The examples below use the https://aws.amazon.com/cli/[aws] command-line tool, which must be separately installed and configured beforehand.	También necesita tener acceso a una cuenta AWS. Los ejemplos de abajo usan las herramienta de línea de comandos https://aws.amazon.com/cli/[aws], que debe instalarse y configurarse separadamente de antemano.
	Launching a VM instance	Lanzar una instancia de Máquina Virtual
	Minimal Example	Ejemplo Mínimo
	Customized Example	Ejemplo Personalizado
	In order to launch a customized FCOS instance, a valid Ignition configuration must be passed as its https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-add-user-data[user data] at creation time. You can use the same command from the xref:#_minimal_example[] but add `--user-data file://path/to/config.ign` argument:	Con el objetivo de lanzar una instancia FCOS personalizada, se debe pasar una configuración Ignition válida como sus https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html#instancedata-add-user-data[datos de usuario] en el momento de la creación. Usted puede utilizar el mismo comando del ejemplo mínimo pero añadiendo el argumento `--user-data file://path/to/config.ign`:
	The SSH key for the `core` user is supplied via Afterburn in this example as well.	La clave SSH para el usuario `core` también se proporciona a través de Afterburn en este ejemplo.
	Launching and customizing a new instance	Lanzar y personalizar una nueva instancia
	NAME='instance1' SSHKEY='my-key' # the name of your SSH key: `aws ec2 describe-key-pairs` IMAGE='ami-xxx' # the AMI ID found on the download page DISK='20' # the size of the hard disk REGION='us-east-1' # the target region TYPE='m5.large' # the instance type SUBNET='subnet-xxx' # the subnet: `aws ec2 describe-subnets` SECURITY_GROUPS='sg-xx' # the security group `aws ec2 describe-security-groups` USERDATA='/path/to/config.ign' # path to your Ignition config aws ec2 run-instances \ --region $REGION \ --image-id $IMAGE \ --instance-type $TYPE \ --key-name $SSHKEY \ --subnet-id $SUBNET \ --security-group-ids $SECURITY_GROUPS \ --user-data "file://${USERDATA}" \ --tag-specifications "ResourceType=instance,Tags=[{Key=Name,Value=${NAME}}]" \ --block-device-mappings "VirtualName=/dev/xvda,DeviceName=/dev/xvda,Ebs={VolumeSize=${DISK}}"	NAME='instance1' SSHKEY='my-key' # the name of your SSH key: `aws ec2 describe-key-pairs` IMAGE='ami-xxx' # the AMI ID found on the download page DISK='20' # the size of the hard disk REGION='us-east-1' # the target region TYPE='m5.large' # the instance type SUBNET='subnet-xxx' # the subnet: `aws ec2 describe-subnets` SECURITY_GROUPS='sg-xx' # the security group `aws ec2 describe-security-groups` USERDATA='/path/to/config.ign' # path to your Ignition config aws ec2 run-instances \ --region $REGION \ --image-id $IMAGE \ --instance-type $TYPE \ --key-name $SSHKEY \ --subnet-id $SUBNET \ --security-group-ids $SECURITY_GROUPS \ --user-data "file://${USERDATA}" \ --tag-specifications "ResourceType=instance,Tags=[{Key=Name,Value=${NAME}}]" \ --block-device-mappings "VirtualName=/dev/xvda,DeviceName=/dev/xvda,Ebs={VolumeSize=${DISK}}"
	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.	Por diseño, la configuración cloud-init y los scripts de arranque no se admiten en FCOS. En su lugar, se recomienda codificar cualquier lógica de inicio como unidades de servicio systemd en la configuración Ignition.
	You can find out the instance's assigned IP by running `aws ec2 describe-instances`	Usted puede encontrar la IP asignada de la instancia ejecutando`aws ec2 describe-instances`
	You now should be able to SSH into the instance using the associated IP address.	Ahora debería poder acceder mediante SSH a la instancia usando la dirección IP asociada.
	Example connecting	Ejemplo de conexión
	ssh core@<ip address>	ssh core@<ip address>
	Remote Ignition configuration	Configuración Ignition remota
	As user-data is limited to 16 KB, you may need to use an external source for your Ignition configuration. A common solution is to upload the config to a S3 bucket, as the following steps show:	Como los datos de usuario están limitados a 16 KB, usted puede necesitar una fuente externa para su configuración Ignition. Una solución común es cargar la configuración en un depósito S3, como muestran los siguientes pasos:
	Create a new s3 bucket	Crear un nuevo depósito s3
	NAME='instance1' aws s3 mb s3://$NAME-infra
	Upload the Ignition file	Cargar el archivo Ignition
	NAME='instance1' CONFIG='/path/to/config.ign' # path to your Ignition config aws s3 cp $CONFIG s3://$NAME-infra/bootstrap.ign	NAME='instance1' CONFIG='/path/to/config.ign' # path to your Ignition config aws s3 cp CONFIG s3://$NAME-infra/bootstrap.ign
	You can verify the file have been correctly uploaded:	Usted puede verificar que el archivo ha sido cargado correctamente:
	List files in the bucket	Listar archivos en el depósito
	NAME='instance1' aws s3 ls s3://$NAME-infra/	NAME='instance1' aws s3 ls s3://$NAME-infra/
	Then create a minimal Ignition config as follows:	Después cree la configuración Ignition mínima como sigue:

Loading…

vareli

Translation added

English

Spanish 1018 characters edited Current translation Translated

3 months ago

None

String updated in the repository

English

Spanish 0 characters edited Empty

2 years ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string description

type: delimited block -

Flags

no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"

Source string location

pages/provisioning-aws.adoc:49

String age

2 years ago

Last updated

3 months ago

Source string age

2 years ago

Translation file

po/es/master/pages/provisioning-aws.po, string 14

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.