documentation/aws: More additions of Import documention to the AWS (#7729)

resources
This commit is contained in:
Paul Stack 2016-07-20 23:28:59 +01:00 committed by GitHub
parent d6d0c9087e
commit 5f6ea8b18e
60 changed files with 424 additions and 11 deletions

View File

@ -82,3 +82,12 @@ The following attribute is exported:
* `burst_limit` - The absolute maximum number of times API Gateway allows the API to be called per second (RPS).
* `rate_limit` - The number of times API Gateway allows the API to be called per second on average (RPS).
## Import
API Gateway Accounts can be imported using the word `api-gateway-account`, e.g.
```
$ terraform import aws_api_gateway_account.demo api-gateway-account
```

View File

@ -51,3 +51,12 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The ID of the API key
## Import
API Gateway Keys can be imported using the `id`, e.g.
```
$ terraform import aws_api_gateway_api_key.my_demo_key 8bklk8bl1k3sB38D9B3l0enyWT8c09B30lkq0blk
```

View File

@ -178,3 +178,12 @@ If ASG creation takes more than a few minutes, this could indicate one of a
number of configuration problems. See the [AWS Docs on Load Balancer
Troubleshooting](https://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-troubleshooting.html)
for more information.
## Import
AutoScaling Groups can be imported using the `name`, e.g.
```
$ terraform import aws_autoscaling_group.web web-asg
```

View File

@ -101,3 +101,12 @@ aws_s3_bucket "bucket" {
[2]: http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html
[3]: /docs/providers/aws/r/cloudfront_distribution.html
[4]: /docs/providers/aws/r/s3_bucket.html
## Import
Cloudfront Origin Access Identities can be imported using the `id`, e.g.
```
$ terraform import aws_cloudfront_origin_access_identity.origin_access E74FTE3AEXAMPLE
```

View File

@ -87,3 +87,12 @@ The following attributes are exported:
* `id` - The name of the trail.
* `home_region` - The region in which the trail was created.
* `arn` - The Amazon Resource Name of the trail.
## Import
Cloudtrails can be imported using the `name`, e.g.
```
$ terraform import aws_cloudtrail.sample my-sample-trail
```

View File

@ -55,3 +55,12 @@ The following arguments are supported:
The following attributes are exported:
* `arn` - The Amazon Resource Name (ARN) of the rule.
## Import
Cloudwatch Event Rules can be imported using the `name`, e.g.
```
$ terraform import aws_cloudwatch_event_rule.console capture-console-sign-in
```

View File

@ -31,3 +31,12 @@ The following arguments are supported:
The following attributes are exported:
* `arn` - The Amazon Resource Name (ARN) specifying the log group.
## Import
Cloudwatch Log Groups can be imported using the `name`, e.g.
```
$ terraform import aws_cloudwatch_log_group.test_group yada
```

View File

@ -84,3 +84,12 @@ The following attributes are exported:
* `id` - The ID of the health check
## Import
Cloud Metric Alarms can be imported using the `alarm_name`, e.g.
```
$ terraform import aws_cloudwatch_metric_alarm.test alarm-12345
```

View File

@ -44,3 +44,12 @@ The following attributes are exported:
* `ip_address` - The IP address of the gateway's Internet-routable external interface.
* `type` - The type of customer gateway.
* `tags` - Tags applied to the gateway.
## Import
Customer Gateways can be imported using the `id`, e.g.
```
$ terraform import aws_customer_gateway.main cgw-b4dc3961
```

View File

@ -141,3 +141,11 @@ On Oracle instances the following is exported additionally:
[1]: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Replication.html
[2]: https://docs.aws.amazon.com/fr_fr/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html
## Import
DB Instances can be imported using the `identifier`, e.g.
```
$ terraform import aws_db_instance.default mydb-rds-instance
```

View File

@ -62,3 +62,11 @@ Option Settings blocks support the following:
The following attributes are exported:
* `arn` - The ARN of the db option group.
## Import
DB Option groups can be imported using the `name`, e.g.
```
$ terraform import aws_db_option_group.bar mysql-option-group
```

View File

@ -51,3 +51,11 @@ The following attributes are exported:
* `id` - The db parameter group name.
* `arn` - The ARN of the db parameter group.
## Import
DB Parameter groups can be imported using the `name`, e.g.
```
$ terraform import aws_db_parameter_group.rds_pg rds-pg
```

View File

@ -38,3 +38,11 @@ The following attributes are exported:
* `id` - The db subnet group name.
* `arn` - The ARN of the db subnet group.
## Import
DB Subnet groups can be imported using the `name`, e.g.
```
$ terraform import aws_db_subnet_group.default production-subnet-group
```

View File

@ -44,3 +44,10 @@ The following attributes are exported:
* `id` - The volume ID (e.g. vol-59fcb34e).
## Import
EBS Volumes can be imported using the `id`, e.g.
```
$ terraform import aws_ebs_volume.data vol-049df61146c4d7901
```

View File

@ -36,3 +36,12 @@ The following attributes are exported:
* `name` - The name of the repository.
* `registry_id` - The registry ID where the repository was created.
* `repository_url` - The URL of the repository (in the form `https://aws_account_id.dkr.ecr.region.amazonaws.com/repositoryName`
## Import
ECR Repositories can be imported using the `name`, e.g.
```
$ terraform import aws_ecr_repository.service test-service
```

View File

@ -33,3 +33,12 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The ID that identifies the file system
## Import
EFS Filesystems can be imported using the `id`, e.g.
```
$ terraform import aws_efs_file_system.foo fs-6fa144c6
```

View File

@ -48,3 +48,12 @@ The following attributes are exported:
* `id` - The ID of the mount target
* `dns_name` - The DNS name for the given subnet/AZ per [documented convention](http://docs.aws.amazon.com/efs/latest/ug/mounting-fs-mount-cmd-dns-name.html)
* `network_interface_id` - The ID of the network interface that Amazon EFS created when it created the mount target.
## Import
EFS Mount Targets can be imported using the `id`, e.g.
```
$ terraform import aws_efs_mount_target.alpha fsmt-52a643fb
```

View File

@ -37,3 +37,12 @@ The following attributes are exported:
* `name`
* `description`
## Import
Elastic Beanstalk Applications can be imported using the `name`, e.g.
```
$ terraform import aws_elastic_beanstalk_application.tf_test tf-test-name
```

View File

@ -95,3 +95,12 @@ The following attributes are exported:
[1]: http://docs.aws.amazon.com/fr_fr/elasticbeanstalk/latest/dg/concepts.platforms.html
## Import
Elastic Beanstalk Environments can be imported using the `id`, e.g.
```
$ terraform import aws_elastic_beanstalk_environment.prodenv e-rpqsewtp2j
```

View File

@ -46,3 +46,12 @@ Parameter blocks support the following:
The following attributes are exported:
* `id` - The ElastiCache parameter group name.
## Import
ElastiCache Parameter Groups can be imported using the `name`, e.g.
```
$ terraform import aws_elasticache_parameter_group.default redis-params
```

View File

@ -55,3 +55,11 @@ The following attributes are exported:
* `name`
* `subnet_ids`
## Import
ElastiCache Subnet Groups can be imported using the `name`, e.g.
```
$ terraform import aws_elasticache_subnet_group.bar tf-test-cache-subnet
```

View File

@ -128,3 +128,11 @@ The following attributes are exported:
part of your inbound rules for your load balancer's back-end application
instances. Only available on ELBs launched in a VPC.
* `zone_id` - The canonical hosted zone ID of the ELB (to be used in a Route 53 Alias record)
## Import
ELBs can be imported using the `name`, e.g.
```
$ terraform import aws_elb.bar elb-production-12345
```

View File

@ -82,3 +82,11 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The Flow Log ID
## Import
Flow Logs can be imported using the `id`, e.g.
```
$ terraform import aws_flow_log.test_flow_log fl-1a2b3c4d
```

View File

@ -72,3 +72,11 @@ The following attributes are exported:
* `location` - The URI of the vault that was created.
* `arn` - The ARN of the vault.
## Import
Glacier Vaults can be imported using the `name`, e.g.
```
$ terraform import aws_glacier_vault.archive my_archive
```

View File

@ -49,3 +49,12 @@ The following attributes are exported:
* `expire_passwords` - Indicates whether passwords in the account expire.
Returns `true` if `max_password_age` contains a value greater than `0`.
Returns `false` if it is `0` or _not present_.
## Import
IAM Account Password Policy can be imported using the work `iam-account-password-policy`, e.g.
```
$ terraform import aws_iam_account_password_policy.strict iam-account-password-policy
```

View File

@ -37,3 +37,11 @@ The following attributes are exported:
* `unique_id` - The [unique ID][1] assigned by AWS.
[1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/Using_Identifiers.html#GUIDs
## Import
IAM Groups can be imported using the `name`, e.g.
```
$ terraform import aws_iam_group.developers developers
```

View File

@ -32,3 +32,11 @@ The following attributes are exported:
* `arn` - The ARN assigned by AWS for this provider.
* `valid_until` - The expiration date and time for the SAML provider in RFC1123 format, e.g. `Mon, 02 Jan 2006 15:04:05 MST`.
## Import
IAM SAML Providers can be imported using the `arn`, e.g.
```
$ terraform import aws_iam_saml_provider.default arn:aws:iam::123456789012:saml-provider/SAMLADFS
```

View File

@ -57,3 +57,12 @@ The following attributes are exported:
* `arn` - The ARN assigned by AWS for this user.
[1]: https://docs.aws.amazon.com/IAM/latest/UserGuide/Using_Identifiers.html#GUIDs
## Import
IAM Users can be imported using the `name`, e.g.
```
$ terraform import aws_iam_user.lb loadbalancer
```

View File

@ -159,3 +159,12 @@ The following attributes are exported:
* `security_groups` - The associated security groups.
* `vpc_security_group_ids` - The associated security groups in non-default VPC
* `subnet_id` - The VPC subnet ID.
## Import
Instances can be imported using the `id`, e.g.
```
$ terraform import aws_instance.web i-12345678
```

View File

@ -47,3 +47,11 @@ The following attributes are exported:
* `id` - The ID of the Internet Gateway.
## Import
Internet Gateways can be imported using the `id`, e.g.
```
$ terraform import aws_internet_gateway.gw igw-c0a643a9
```

View File

@ -40,3 +40,11 @@ The following attributes are exported:
* `key_name` - The key pair name.
* `fingerprint` - The MD5 public key fingerprint as specified in section 4 of RFC 4716.
## Import
Key Pairs can be imported using the `key_name`, e.g.
```
$ terraform import aws_key_pair.deployer deployer-key
```

View File

@ -39,3 +39,11 @@ The following attributes are exported:
* `arn` - The Amazon Resource Name (ARN) of the key.
* `key_id` - The globally unique identifier for the key.
## Import
KMS Keys can be imported using the `id`, e.g.
```
$ terraform import aws_kms_key.a arn:aws:kms:us-west-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
```

View File

@ -79,3 +79,11 @@ resource "aws_lambda_function" "test_lambda" {
[5]: https://docs.aws.amazon.com/lambda/latest/dg/limits.html
[6]: https://docs.aws.amazon.com/lambda/latest/dg/API_CreateFunction.html#SSS-CreateFunction-request-Runtime
[7]: http://docs.aws.amazon.com/lambda/latest/dg/vpc.html
## Import
Lambda Functions can be imported using the `function_name`, e.g.
```
$ terraform import aws_lambda_function.tesr_lambda my_test_lambda_function
```

View File

@ -214,3 +214,11 @@ The following attributes are exported:
[1]: /docs/providers/aws/r/autoscaling_group.html
[2]: /docs/configuration/resources.html#lifecycle
[3]: /docs/providers/aws/r/spot_instance_request.html
## Import
Launch configurations can be imported using the `name`, e.g.
```
$ terraform import aws_launch_configuration.as_conf terraform-lg-123456
```

View File

@ -49,3 +49,11 @@ The following attributes are exported:
* `network_interface_id` - The ENI ID of the network interface created by the NAT gateway.
* `private_ip` - The private IP address of the NAT Gateway.
* `public_ip` - The public IP address of the NAT Gateway.
## Import
NAT Gateways can be imported using the `id`, e.g.
```
$ terraform import aws_nat_gateway.private_gw nat-05dba92075d71c408
```

View File

@ -73,3 +73,11 @@ The following attributes are exported:
* `id` - The ID of the network ACL
## Import
Network ACLs can be imported using the `id`, e.g.
```
$ terraform import aws_network_acl.main acl-7aaabd18
```

View File

@ -53,3 +53,12 @@ The following attributes are exported:
* `source_dest_check` - Whether source destination checking is enabled
* `tags` - Tags assigned to the ENI.
## Import
Network Interfaces can be imported using the `id`, e.g.
```
$ terraform import aws_network_interface.test eni-e5aa89a3
```

View File

@ -32,3 +32,11 @@ The following arguments are supported:
The following attributes are exported:
* `id` - The name of the placement group.
## Import
Placement groups can be imported using the `name`, e.g.
```
$ terraform import aws_placement_group.prod_pg production-placement-group
```

View File

@ -109,3 +109,11 @@ The following attributes are exported:
[2]: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Aurora.html
[3]: /docs/providers/aws/r/rds_cluster_instance.html
[4]: http://docs.aws.amazon.com/fr_fr/AmazonRDS/latest/UserGuide/USER_UpgradeDBInstance.Maintenance.html
## Import
RDS Clusters can be imported using the `cluster_identifier`, e.g.
```
$ terraform import aws_rds_cluster.aurora_cluster aurora-prod-cluster
```

View File

@ -90,3 +90,11 @@ this instance is a read replica
[4]: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora.Managing.html
[5]: /docs/configuration/resources.html#count
[6]: https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html
## Import
Redshift Cluster Instances can be imported using the `identifier`, e.g.
```
$ terraform import aws_rds_cluster_instance.prod_instance_1 aurora-cluster-instance-1
```

View File

@ -53,3 +53,11 @@ The following attributes are exported:
* `id` - The db cluster parameter group name.
* `arn` - The ARN of the db cluster parameter group.
## Import
Redshift Clusters can be imported using the `name`, e.g.
```
$ terraform import aws_rds_cluster_parameter_group.cluster_pg production-pg-1
```

View File

@ -82,3 +82,11 @@ The following attributes are exported:
* `cluster_subnet_group_name` - The name of a cluster subnet group to be associated with this cluster
* `cluster_public_key` - The public key for the cluster
* `cluster_revision_number` - The specific revision number of the database in the cluster
## Import
Redshift Clusters can be imported using the `cluster_identifier`, e.g.
```
$ terraform import aws_redshift_cluster.myprodcluster tf-redshift-cluster-12345
```

View File

@ -50,3 +50,11 @@ You can read more about the parameters that Redshift supports in the [documentat
The following attributes are exported:
* `id` - The Redshift parameter group name.
## Import
Redshift Parameter Groups can be imported using the `name`, e.g.
```
$ terraform import aws_redshift_parameter_group.paramgroup1 parameter-group-test-terraform
```

View File

@ -56,3 +56,10 @@ The following attributes are exported:
* `id` - The Redshift Subnet group ID.
## Import
Redshift subnet groups can be imported using the `name`, e.g.
```
$ terraform import aws_redshift_subnet_group.testgroup1 test-cluster-subnet-group
```

View File

@ -42,3 +42,13 @@ The following attributes are exported:
* `id` - The delegation set ID
* `name_servers` - A list of authoritative name servers for the hosted zone
(effectively a list of NS records).
## Import
Route53 Delegation Sets can be imported using the `delegation set id`, e.g.
```
$ terraform import aws_route53_delegation_set.set1 N1PA6795SAMPLE
```

View File

@ -56,3 +56,11 @@ The following arguments are supported:
At least one of either `fqdn` or `ip_address` must be specified.
## Import
Route53 Health Checks can be imported using the `health check id`, e.g.
```
$ terraform import aws_route53_health_check.http_check abcdef11-2222-3333-4444-555555fedcba
```

View File

@ -69,3 +69,12 @@ The following attributes are exported:
* `zone_id` - The Hosted Zone ID. This can be referenced by zone records.
* `name_servers` - A list of name servers in associated (or default) delegation set.
Find more about delegation sets in [AWS docs](https://docs.aws.amazon.com/Route53/latest/APIReference/actions-on-reusable-delegation-sets.html).
## Import
Route53 Zones can be imported using the `zone id`, e.g.
```
$ terraform import aws_route53_zone.myzone Z1D633PJN98FT9
```

View File

@ -61,3 +61,11 @@ The following attributes are exported:
attribute once the route resource is created.
* `id` - The ID of the routing table
## Import
Route Tables can be imported using the `route table id`, e.g.
```
$ terraform import aws_route_table.public_rt rtb-22574640
```

View File

@ -152,3 +152,12 @@ The following attributes are exported:
* `description` - The description of the security group
* `ingress` - The ingress rules. See above for more.
* `egress` - The egress rules. See above for more.
## Import
Security Groups can be imported using the `security group id`, e.g.
```
$ terraform import aws_security_group.elb_sg sg-903004f8
```

View File

@ -35,5 +35,5 @@ The following attributes are exported:
SimpleDB Domains can be imported using the `name`, e.g.
```
terraform import aws_simpledb_domain.users users
$ terraform import aws_simpledb_domain.users users
```

View File

@ -39,5 +39,5 @@ The following attributes are exported:
SNS Topics can be imported using the `topic arn`, e.g.
```
terraform import aws_sns_topic.user_updates arn:aws:sns:us-west-2:0123456789012:my-topic
$ terraform import aws_sns_topic.user_updates arn:aws:sns:us-west-2:0123456789012:my-topic
```

View File

@ -102,5 +102,5 @@ The following attributes are exported:
SNS Topic Subscriptions can be imported using the `subscription arn`, e.g.
```
terraform import aws_sns_topic_subscription.user_updates_sqs_target arn:aws:sns:us-west-2:0123456789012:my-topic:8a21d249-4329-4871-acc6-7be709c6ea7f
$ terraform import aws_sns_topic_subscription.user_updates_sqs_target arn:aws:sns:us-west-2:0123456789012:my-topic:8a21d249-4329-4871-acc6-7be709c6ea7f
```

View File

@ -46,5 +46,5 @@ The following attributes are exported:
SQS Queues can be imported using the `queue url`, e.g.
```
terraform import aws_sqs_queue.public_queue https://queue.amazonaws.com/80398EXAMPLE/MyQueue
$ terraform import aws_sqs_queue.public_queue https://queue.amazonaws.com/80398EXAMPLE/MyQueue
```

View File

@ -51,5 +51,5 @@ The following attributes are exported:
Subnets can be imported using the `subnet id`, e.g.
```
terraform import aws_subnet.public_subnet subnet-9d4a7b6c
$ terraform import aws_subnet.public_subnet subnet-9d4a7b6c
```

View File

@ -70,5 +70,5 @@ The following attributes are exported:
VPNs can be imported using the `vpn id`, e.g.
```
terraform import aws_vpn.test_vpn vpc-a01106c2
$ terraform import aws_vpn.test_vpn vpc-a01106c2
```

View File

@ -68,5 +68,5 @@ official [AWS User Guide](https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide
VPC DHCP Options can be imported using the `dhcp options id`, e.g.
```
terraform import aws_vpc_dhcp_options.my_options dopt-d9070ebb
$ terraform import aws_vpc_dhcp_options.my_options dopt-d9070ebb
```

View File

@ -43,5 +43,5 @@ The following attributes are exported:
VPN Endpoints can be imported using the `vpc endpoint id`, e.g.
```
terraform import aws_vpc_endpoint.endpoint1 vpce-3ecf2a57
$ terraform import aws_vpc_endpoint.endpoint1 vpce-3ecf2a57
```

View File

@ -72,5 +72,5 @@ If you are not the owner of both VPCs, or do not enable auto_accept you will sti
VPC Peering resources can be imported using the `vpc peering id`, e.g.
```
terraform import aws_vpc_peering_connection.test_connection pcx-111aaa111
$ terraform import aws_vpc_peering_connection.test_connection pcx-111aaa111
```

View File

@ -68,5 +68,5 @@ The following attributes are exported:
VPN Connections can be imported using the `vpn connection id`, e.g.
```
terraform import aws_vpn_connection.testvpnconnection vpn-40f41529
$ terraform import aws_vpn_connection.testvpnconnection vpn-40f41529
```

View File

@ -42,5 +42,5 @@ The following attributes are exported:
VPN Gateways can be imported using the `vpn gateway id`, e.g.
```
terraform import aws_vpn_gateway.testvpngateway vgw-9a4cacf3
$ terraform import aws_vpn_gateway.testvpngateway vgw-9a4cacf3
```