Difference between revisions of "Terraform apply: ec2 instance example (aws instance module)"
Jump to navigation
Jump to search
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
https://github.com/terraform-aws-modules/terraform-aws-ec2-instance/tree/master/examples/basic | https://github.com/terraform-aws-modules/terraform-aws-ec2-instance/tree/master/examples/basic | ||
| Line 6: | Line 5: | ||
* Resource: <code>[[aws_instance]]</code> | * Resource: <code>[[aws_instance]]</code> | ||
| − | * [[aws instance example: main.tf]] | + | * [[aws instance example]]: <code>[[main.tf]]</code> |
== Apply complete! == | == Apply complete! == | ||
| Line 137: | Line 136: | ||
</pre> | </pre> | ||
| − | == Related | + | == Related == |
* [[Terraform apply examples with errors]] | * [[Terraform apply examples with errors]] | ||
* <code>[[terraform show]]</code> | * <code>[[terraform show]]</code> | ||
| − | * <code>[[ec2-instance]]</code> | + | * Terraform module: <code>[[ec2-instance]]</code> |
| + | * [[Terraform resource: aws_volume_attachment]] | ||
| + | [[ebs_block_device]] | ||
== See also == | == See also == | ||
| + | * {{tf ec2}} | ||
* {{terraform apply}} | * {{terraform apply}} | ||
| − | + | ||
[[Category:Terraform]] | [[Category:Terraform]] | ||
Latest revision as of 08:08, 15 February 2023
https://github.com/terraform-aws-modules/terraform-aws-ec2-instance/tree/master/examples/basic
- Resource:
aws_instance - aws instance example:
main.tf
Apply complete![edit]
terraform apply
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with
the following symbols:
+ create
Terraform will perform the following actions:
# aws_instance.example will be created
+ resource "aws_instance" "example" {
+ ami = "ami-08d70e59c07c61a3a"
+ arn = (known after apply)
+ associate_public_ip_address = (known after apply)
+ availability_zone = (known after apply)
+ cpu_core_count = (known after apply)
+ cpu_threads_per_core = (known after apply)
+ disable_api_termination = (known after apply)
+ ebs_optimized = (known after apply)
+ get_password_data = false
+ host_id = (known after apply)
+ id = (known after apply)
+ instance_initiated_shutdown_behavior = (known after apply)
+ instance_state = (known after apply)
+ instance_type = "t2.micro"
+ ipv6_address_count = (known after apply)
+ ipv6_addresses = (known after apply)
+ key_name = (known after apply)
+ monitoring = (known after apply)
+ outpost_arn = (known after apply)
+ password_data = (known after apply)
+ placement_group = (known after apply)
+ primary_network_interface_id = (known after apply)
+ private_dns = (known after apply)
+ private_ip = (known after apply)
+ public_dns = (known after apply)
+ public_ip = (known after apply)
+ secondary_private_ips = (known after apply)
+ security_groups = (known after apply)
+ source_dest_check = true
+ subnet_id = (known after apply)
+ tags = {
+ "Name" = "ExampleAppServerInstance"
}
+ tags_all = {
+ "Name" = "ExampleAppServerInstance"
}
+ tenancy = (known after apply)
+ user_data = (known after apply)
+ user_data_base64 = (known after apply)
+ vpc_security_group_ids = (known after apply)
+ capacity_reservation_specification {
+ capacity_reservation_preference = (known after apply)
+ capacity_reservation_target {
+ capacity_reservation_id = (known after apply)
}
}
+ ebs_block_device {
+ delete_on_termination = (known after apply)
+ device_name = (known after apply)
+ encrypted = (known after apply)
+ iops = (known after apply)
+ kms_key_id = (known after apply)
+ snapshot_id = (known after apply)
+ tags = (known after apply)
+ throughput = (known after apply)
+ volume_id = (known after apply)
+ volume_size = (known after apply)
+ volume_type = (known after apply)
}
+ enclave_options {
+ enabled = (known after apply)
}
+ ephemeral_block_device {
+ device_name = (known after apply)
+ no_device = (known after apply)
+ virtual_name = (known after apply)
}
+ metadata_options {
+ http_endpoint = (known after apply)
+ http_put_response_hop_limit = (known after apply)
+ http_tokens = (known after apply)
}
+ network_interface {
+ delete_on_termination = (known after apply)
+ device_index = (known after apply)
+ network_interface_id = (known after apply)
}
+ root_block_device {
+ delete_on_termination = (known after apply)
+ device_name = (known after apply)
+ encrypted = (known after apply)
+ iops = (known after apply)
+ kms_key_id = (known after apply)
+ tags = (known after apply)
+ throughput = (known after apply)
+ volume_id = (known after apply)
+ volume_size = (known after apply)
+ volume_type = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
aws_instance.example: Creating...
aws_instance.example: Still creating... [10s elapsed]
aws_instance.example: Still creating... [20s elapsed]
aws_instance.example: Still creating... [30s elapsed]
aws_instance.example: Still creating... [40s elapsed]
aws_instance.example: Creation complete after 43s [id=i-079b8300c42bea5c3]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Related[edit]
- Terraform apply examples with errors
terraform show- Terraform module:
ec2-instance - Terraform resource: aws_volume_attachment
ebs_block_device
See also[edit]
- Terraform EC2 resources:
aws_instance, aws_ebs_volume, aws_volume_attachment, aws_ec2_tag, Terraform module:ec2-instance,ebs_block_device,argument/input terraform apply[-auto-approve|-refresh-only, -destroy | --help ], Terraform examples,Still creating..., Terraform apply examples with errors
Advertising:
