Difference between revisions of "User data"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| − | <code>user_data</code> (Optional) [[user data]] to provide when [[launching]] the instance. | + | <code>user_data</code> (Optional) [[user data]] to provide when [[launching]] the instance, [[such as shell scripts]]. |
* Notes: Do not pass gzip-compressed data via this argument; see <code>[[user_data_base64]]</code> instead. Updates to this field will trigger a stop/start of the EC2 instance by default. If the <code>[[user_data_replace_on_change]]</code> is set then updates to this field will trigger a destroy and recreate | * Notes: Do not pass gzip-compressed data via this argument; see <code>[[user_data_base64]]</code> instead. Updates to this field will trigger a stop/start of the EC2 instance by default. If the <code>[[user_data_replace_on_change]]</code> is set then updates to this field will trigger a destroy and recreate | ||
Revision as of 06:27, 2 February 2023
user_data (Optional) user data to provide when launching the instance, such as shell scripts.
- Notes: Do not pass gzip-compressed data via this argument; see
user_data_base64instead. Updates to this field will trigger a stop/start of the EC2 instance by default. If theuser_data_replace_on_changeis set then updates to this field will trigger a destroy and recreate
Related
aws_instancetemplatefile, *.tftplkey_namehttp://169.254.169.254/latest/user-data
See also
- Terraform AWS:
aws_instance:ami,availability_zone,instance_type,key_name,aws_key_pair,monitoring,associate_public_ip_address,tenancy,subnet_id, user_data, root_block_device, iam_instance_profile, vpc_security_group_ids, root_block_device - Terraform AWS resources: IAM, Net, EC2, ECS, ECR, S3, Route53, ACM, CloudWatch, CloudFront SES, RDS, DLM
Advertising:
