diff --git a/website/docs/r/route.html.markdown b/website/docs/r/route.html.markdown index 58d93da6fa9..f5679bf935b 100644 --- a/website/docs/r/route.html.markdown +++ b/website/docs/r/route.html.markdown @@ -10,11 +10,7 @@ description: |- Provides a resource to create a routing table entry (a route) in a VPC routing table. -~> **NOTE on Route Tables and Routes:** Terraform currently -provides both a standalone Route resource and a [Route Table](route_table.html) resource with routes -defined in-line. At this time you cannot use a Route Table with in-line routes -in conjunction with any Route resources. Doing so will cause -a conflict of rule settings and will overwrite rules. +~> **NOTE on Route Tables and Routes:** Terraform currently provides both a standalone Route resource and a [Route Table](route_table.html) resource with routes defined in-line. At this time you cannot use a Route Table with in-line routes in conjunction with any Route resources. Doing so will cause a conflict of rule settings and will overwrite rules. ~> **NOTE on `gateway_id` attribute:** The AWS API is very forgiving with the resource ID passed in the `gateway_id` attribute. For example an `aws_route` resource can be created with an [`aws_nat_gateway`](nat_gateway.html) or [`aws_egress_only_internet_gateway`](egress_only_internet_gateway.html) ID specified for the `gateway_id` attribute. Specifying anything other than an [`aws_internet_gateway`](internet_gateway.html) or [`aws_vpn_gateway`](vpn_gateway.html) ID will lead to Terraform reporting a permanent diff between your configuration and recorded state, as the AWS API returns the more-specific attribute. If you are experiencing constant diffs with an `aws_route` resource, the first thing to check is that the correct attribute is being specified. @@ -73,15 +69,13 @@ One of the following target arguments must be supplied: * `vpc_endpoint_id` - (Optional) Identifier of a VPC Endpoint. * `vpc_peering_connection_id` - (Optional) Identifier of a VPC peering connection. -Note that the default route, mapping the VPC's CIDR block to "local", is -created implicitly and cannot be specified. +Note that the default route, mapping the VPC's CIDR block to "local", is created implicitly and cannot be specified. ## Attributes Reference In addition to all arguments above, the following attributes are exported: -~> **NOTE:** Only the arguments that are configured (one of the above) -will be exported as an attribute once the resource is created. +~> **NOTE:** Only the arguments that are configured (one of the above) will be exported as an attribute once the resource is created. * `id` - Route identifier computed from the routing table identifier and route destination. * `instance_owner_id` - The AWS account ID of the owner of the EC2 instance. @@ -90,8 +84,7 @@ will be exported as an attribute once the resource is created. ## Timeouts -`aws_route` provides the following -[Timeouts](https://www.terraform.io/docs/configuration/blocks/resources/syntax.html#operation-timeouts) configuration options: +`aws_route` provides the following [Timeouts](https://www.terraform.io/docs/configuration/blocks/resources/syntax.html#operation-timeouts) configuration options: - `create` - (Default `2 minutes`) Used for route creation - `delete` - (Default `5 minutes`) Used for route deletion