AWS outposts documentation change
Summary
Updated multiple documentation links from relative paths to full URLs and improved formatting with line breaks
Security assessment
The changes primarily involve updating hyperlinks to use absolute paths and improving document structure. There is no mention of security vulnerabilities, patches, or security feature enhancements. The modifications relate to general documentation maintenance and readability improvements.
Diff
diff --git a/outposts/latest/userguide/launch-instance.md b/outposts/latest/userguide/launch-instance.md index d0fa07fdd..fefe30372 100644 --- a//outposts/latest/userguide/launch-instance.md +++ b//outposts/latest/userguide/launch-instance.md @@ -13 +13 @@ After your Outpost is installed and the compute and storage capacity is availabl -You must have an Outpost installed at your site. For more information, see [Create an order for an Outposts rack](./order-outpost-capacity.html). +You must have an Outpost installed at your site. For more information, see [Create an order for an Outposts rack](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html). @@ -67 +67 @@ If you want to use Direct VPC routing, specify a CIDR range that does not overla -You can create and add an Outpost subnet to any VPC in the AWS Region that the Outpost is homed to. When you do so, the VPC includes the Outpost. For more information, see [Network components](./how-outposts-works.html#outposts-networking-components). +You can create and add an Outpost subnet to any VPC in the AWS Region that the Outpost is homed to. When you do so, the VPC includes the Outpost. For more information, see [Network components](https://docs.aws.amazon.com/outposts/latest/userguide/how-outposts-works.html#outposts-networking-components). @@ -71 +71 @@ You can create and add an Outpost subnet to any VPC in the AWS Region that the O -If you are launching an instance in an Outpost subnet that has been shared with you by another AWS account, skip to Step 5: Launch an instance on the Outpost. +If you are launching an instance in an Outpost subnet that has been shared with you by another AWS account, skip to [Step 5: Launch an instance on the Outpost](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html#launch-instances). @@ -137 +137,3 @@ To apply route table routes to a particular subnet, you must associate the route -The local gateway (LGW) enables connectivity between your Outpost subnets and your on-premises network. For more information about the LGW, see [Local gateway](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-local-gateways.html). +The local gateway (LGW) enables connectivity between your Outpost subnets and your on-premises network. + +For more information about the LGW, see [Local gateways](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-local-gateways.html). @@ -166 +168 @@ Use the following procedure to create a custom route table for your local gatewa - * Choose **CoIP** to use addresses from your customer-owned IP address pools. You can specify up to 10 CoIP pools and 100 CIDR blocks. For more information, see [CoIP pools](./coip-pools.html). + * Choose **CoIP** to use addresses from your customer-owned IP address pools. You can specify up to 10 CoIP pools and 100 CIDR blocks. For more information, see [Create a CoIP pool](https://docs.aws.amazon.com/outposts/latest/userguide/coip-pools.html). @@ -269 +271 @@ Destination | Target -If you configured your Outposts in the 3a. Create a custom local gateway route table to use a customer-owned IP (CoIP) address pool, you must allocate an Elastic IP address from the CoIP address pool and associate the Elastic IP address with the instance. For more information, see [Customer-owned IP addresses](./routing.html#ip-addressing). +If you configured your Outposts in the 3a. Create a custom local gateway route table to use a customer-owned IP (CoIP) address pool, you must allocate an Elastic IP address from the CoIP address pool and associate the Elastic IP address with the instance. For more information, see [Customer-owned IP addresses](https://docs.aws.amazon.com/outposts/latest/userguide/routing.html#ip-addressing). @@ -279 +281,3 @@ If you want to use a shared customer-owned IP address pool, the pool must be sha -The Outpost establishes an external BGP peering from each Outpost Networking Device (OND) to a Customer Local Network Device (CND) to send and receive traffic from your on-premise network to the Outposts. For more information, see [Local gateway BGP connectivity](https://docs.aws.amazon.com/outposts/latest/userguide/local-rack.html#local-gateway-bgp-connectivity). +The Outpost establishes an external BGP peering from each Outpost Networking Device (OND) to a Customer Local Network Device (CND) to send and receive traffic from your on-premise network to the Outposts. + +For more information, see [Local gateway BGP connectivity](https://docs.aws.amazon.com/outposts/latest/userguide/local-rack.html#local-gateway-bgp-connectivity). @@ -316 +320,3 @@ As a result, the local gateway will send outbound traffic with destination netwo -For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor. For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/userguide/network-troubleshoot.html). +For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor. + +For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/userguide/network-troubleshoot.html). @@ -346 +352,5 @@ As a result the local gateway will send outbound traffic with destination networ -For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor. For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/userguide/network-troubleshoot.html). +For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor. + +For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/userguide/network-troubleshoot.html). + +For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/network-userguide/network-troubleshoot.html). @@ -356 +366 @@ You can launch EC2 instances in the Outpost subnet that you created, or in an Ou - * You can create a [placement group](./outposts-optimizations.html#placement-groups-outpost) to influence how Amazon EC2 should attempt to place groups of interdependent instances on the Outposts hardware. You can choose the placement group strategy that meets the needs of your workload. + * You can create a [placement group](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-optimizations.html) to influence how Amazon EC2 should attempt to place groups of interdependent instances on the Outposts hardware. You can choose the placement group strategy that meets the needs of your workload.