Doc-only updates for Amazon EC2

Author: aws-sdk-dotnet-automation

generator/ServiceModels/ec2/ec2-2016-11-15.docs.json

@@ -36,12 +36,11 @@ namespace Amazon.EC2.Model
     ///  
     /// <para>
     /// A route server association is the connection established between a route server and
-    /// a VPC. This is a fundamental configuration step that enables the route server to work
-    /// with appliances in your VPC.
+    /// a VPC.
     /// </para>
     ///  
     /// <para>
-    /// For more information see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html">Dynamic
+    /// For more information see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html">Dynamic
     /// routing in your VPC with VPC Route Server</a> in the <i>Amazon VPC User Guide</i>.
     /// </para>
     /// </summary>

generator/ServiceModels/ec2/ec2-2016-11-15.normal.json

@@ -36,8 +36,13 @@ namespace Amazon.EC2.Model
     ///  
     /// <para>
     /// A route server endpoint is an Amazon Web Services-managed component inside a subnet
-    /// that facilitates BGP (Border Gateway Protocol) connections between your route server
-    /// and your BGP peers. Create two endpoints per subnet for redundancy.
+    /// that facilitates <a href="https://en.wikipedia.org/wiki/Border_Gateway_Protocol">BGP
+    /// (Border Gateway Protocol)</a> connections between your route server and your BGP peers.
+    /// </para>
+    ///  
+    /// <para>
+    /// For more information see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html">Dynamic
+    /// routing in your VPC with VPC Route Server</a> in the <i>Amazon VPC User Guide</i>.
     /// </para>
     /// </summary>
     public partial class CreateRouteServerEndpointRequest : AmazonEC2Request

sdk/src/Services/EC2/Generated/Model/AssociateRouteServerRequest.cs

@@ -35,9 +35,9 @@ namespace Amazon.EC2.Model
     /// 
     ///  
     /// <para>
-    /// A route server peer is a network appliance or function deployed in Amazon Web Services,
-    /// such as firewall appliances and other network security functions, that meet these
-    /// requirements:
+    /// A route server peer is a session between a route server endpoint and the device deployed
+    /// in Amazon Web Services (such as a firewall appliance or other network security function
+    /// running on an EC2 instance). The device must meet these requirements:
     /// </para>
     ///  <ul> <li> 
     /// <para>
@@ -51,7 +51,11 @@ namespace Amazon.EC2.Model
     /// <para>
     /// Can initiate BGP sessions
     /// </para>
-    ///  </li> </ul>
+    ///  </li> </ul> 
+    /// <para>
+    /// For more information see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html">Dynamic
+    /// routing in your VPC with VPC Route Server</a> in the <i>Amazon VPC User Guide</i>.
+    /// </para>
     /// </summary>
     public partial class CreateRouteServerPeerRequest : AmazonEC2Request
     {
@@ -83,7 +87,7 @@ internal bool IsSetBgpOptions()
         /// <summary>
         /// Gets and sets the property PeerAddress. 
         /// <para>
-        /// The IPv4 address of the peer.
+        /// The IPv4 address of the peer device.
         /// </para>
         /// </summary>
         [AWSProperty(Required=true)]

sdk/src/Services/EC2/Generated/Model/CreateRouteServerEndpointRequest.cs

@@ -37,18 +37,18 @@ namespace Amazon.EC2.Model
     /// <para>
     /// Amazon VPC Route Server simplifies routing for traffic between workloads that are
     /// deployed within a VPC and its internet gateways. With this feature, VPC Route Server
-    /// dynamically updates VPC and gateway route tables with your preferred IPv4 or IPv6
-    /// routes to achieve routing fault tolerance for those workloads. This enables you to
-    /// automatically reroute traffic within a VPC, which increases the manageability of VPC
-    /// routing and interoperability with third-party workloads.
+    /// dynamically updates VPC and internet gateway route tables with your preferred IPv4
+    /// or IPv6 routes to achieve routing fault tolerance for those workloads. This enables
+    /// you to automatically reroute traffic within a VPC, which increases the manageability
+    /// of VPC routing and interoperability with third-party workloads.
     /// </para>
     ///  
     /// <para>
     /// Route server supports the follow route table types:
     /// </para>
     ///  <ul> <li> 
     /// <para>
-    /// VPC route tables
+    /// VPC route tables not associated with subnets
     /// </para>
     ///  </li> <li> 
     /// <para>
@@ -66,7 +66,7 @@ namespace Amazon.EC2.Model
     /// </para>
     ///  
     /// <para>
-    /// For more information see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html">Dynamic
+    /// For more information see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html">Dynamic
     /// routing in your VPC with VPC Route Server</a> in the <i>Amazon VPC User Guide</i>.
     /// </para>
     /// </summary>

sdk/src/Services/EC2/Generated/Model/CreateRouteServerPeerRequest.cs

@@ -36,8 +36,8 @@ namespace Amazon.EC2.Model
     ///  
     /// <para>
     /// A route server endpoint is an Amazon Web Services-managed component inside a subnet
-    /// that facilitates BGP (Border Gateway Protocol) connections between your route server
-    /// and your BGP peers. Create two endpoints per subnet for redundancy.
+    /// that facilitates <a href="https://en.wikipedia.org/wiki/Border_Gateway_Protocol">BGP
+    /// (Border Gateway Protocol)</a> connections between your route server and your BGP peers.
     /// </para>
     /// </summary>
     public partial class DeleteRouteServerEndpointRequest : AmazonEC2Request

sdk/src/Services/EC2/Generated/Model/CreateRouteServerRequest.cs

@@ -35,9 +35,9 @@ namespace Amazon.EC2.Model
     /// 
     ///  
     /// <para>
-    /// A route server peer is a network appliance or function deployed in Amazon Web Services,
-    /// such as firewall appliances and other network security functions, that meet these
-    /// requirements:
+    /// A route server peer is a session between a route server endpoint and the device deployed
+    /// in Amazon Web Services (such as a firewall appliance or other network security function
+    /// running on an EC2 instance). The device must meet these requirements:
     /// </para>
     ///  <ul> <li> 
     /// <para>

sdk/src/Services/EC2/Generated/Model/DeleteRouteServerEndpointRequest.cs

@@ -37,18 +37,18 @@ namespace Amazon.EC2.Model
     /// <para>
     /// Amazon VPC Route Server simplifies routing for traffic between workloads that are
     /// deployed within a VPC and its internet gateways. With this feature, VPC Route Server
-    /// dynamically updates VPC and gateway route tables with your preferred IPv4 or IPv6
-    /// routes to achieve routing fault tolerance for those workloads. This enables you to
-    /// automatically reroute traffic within a VPC, which increases the manageability of VPC
-    /// routing and interoperability with third-party workloads.
+    /// dynamically updates VPC and internet gateway route tables with your preferred IPv4
+    /// or IPv6 routes to achieve routing fault tolerance for those workloads. This enables
+    /// you to automatically reroute traffic within a VPC, which increases the manageability
+    /// of VPC routing and interoperability with third-party workloads.
     /// </para>
     ///  
     /// <para>
     /// Route server supports the follow route table types:
     /// </para>
     ///  <ul> <li> 
     /// <para>
-    /// VPC route tables
+    /// VPC route tables not associated with subnets
     /// </para>
     ///  </li> <li> 
     /// <para>
@@ -66,7 +66,7 @@ namespace Amazon.EC2.Model
     /// </para>
     ///  
     /// <para>
-    /// For more information see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html">Dynamic
+    /// For more information see <a href="https://docs.aws.amazon.com/vpc/latest/userguide/dynamic-routing-route-server.html">Dynamic
     /// routing in your VPC with VPC Route Server</a> in the <i>Amazon VPC User Guide</i>.
     /// </para>
     /// </summary>

sdk/src/Services/EC2/Generated/Model/DeleteRouteServerPeerRequest.cs

@@ -31,28 +31,40 @@ namespace Amazon.EC2.Model
 {
     /// <summary>
     /// Container for the parameters to the DeregisterImage operation.
-    /// Deregisters the specified AMI. After you deregister an AMI, it can't be used to launch
-    /// new instances.
+    /// Deregisters the specified AMI. A deregistered AMI can't be used to launch new instances.
     /// 
     ///  
     /// <para>
-    /// If you deregister an AMI that matches a Recycle Bin retention rule, the AMI is retained
-    /// in the Recycle Bin for the specified retention period. For more information, see <a
-    /// href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recycle-bin.html">Recycle
-    /// Bin</a> in the <i>Amazon EC2 User Guide</i>.
+    /// If a deregistered EBS-backed AMI matches a Recycle Bin retention rule, it moves to
+    /// the Recycle Bin for the specified retention period. It can be restored before its
+    /// retention period expires, after which it is permanently deleted. If the deregistered
+    /// AMI doesn't match a retention rule, it is permanently deleted immediately. For more
+    /// information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/recycle-bin.html">Recycle
+    /// Bin</a> in the <i>Amazon EBS User Guide</i>.
     /// </para>
     ///  
     /// <para>
-    /// When you deregister an AMI, it doesn't affect any instances that you've already launched
-    /// from the AMI. You'll continue to incur usage costs for those instances until you terminate
-    /// them.
+    /// Deregistering an AMI does not delete the following:
     /// </para>
-    ///  
+    ///  <ul> <li> 
+    /// <para>
+    /// Instances already launched from the AMI. You'll continue to incur usage costs for
+    /// the instances until you terminate them.
+    /// </para>
+    ///  </li> <li> 
+    /// <para>
+    /// For EBS-backed AMIs: The snapshots that were created of the root and data volumes
+    /// of the instance during AMI creation. You'll continue to incur snapshot storage costs.
+    /// </para>
+    ///  </li> <li> 
+    /// <para>
+    /// For instance store-backed AMIs: The files uploaded to Amazon S3 during AMI creation.
+    /// You'll continue to incur S3 storage costs.
+    /// </para>
+    ///  </li> </ul> 
     /// <para>
-    /// When you deregister an Amazon EBS-backed AMI, it doesn't affect the snapshot that
-    /// was created for the root volume of the instance during the AMI creation process. When
-    /// you deregister an instance store-backed AMI, it doesn't affect the files that you
-    /// uploaded to Amazon S3 when you created the AMI.
+    /// For more information, see <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/deregister-ami.html">Deregister
+    /// an Amazon EC2 AMI</a> in the <i>Amazon EC2 User Guide</i>.
     /// </para>
     /// </summary>
     public partial class DeregisterImageRequest : AmazonEC2Request