Change user guide to note Lattice address range (#45)

* Change user guide to note Lattice address range

* More fixes

* Small changes

* Other small changes

* Fixed address range

Author: chrisnegus

docs/how-it-works.md

@@ -26,7 +26,7 @@ Run through them again for a second cluster to use with the extended example sho
    ```bash
    eksctl create cluster —name <my-cluster> —region us-west-2
    ```
-1. TODO: I don't know how to do this step (link?): TODO: Also, Liwen said to say "Lattice-managed prefix" instead of 169.254.0.0/16. Configure security group: To receive traffic from the VPC Lattice fleet, all Pods MUST explicit configure a security group to allow traffic from the 169.254.0.0/16 address range.
+1. Configure security group: To receive traffic from the VPC Lattice fleet, all Pods MUST explicitly configure a security group to allow traffic from the 169.254.171.0/24 address range.
 
 1. Create an IAM OIDC provider: See [Creating an IAM OIDC provider for your cluster](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html) for details.
    ```bash
@@ -54,7 +54,7 @@ Run through them again for a second cluster to use with the extended example sho
    ```
    ```bash
    aws iam create-policy \
-      --policy-name AWSMercuryControllerIAMPolicy \
+      --policy-name VPCLatticeControllerIAMPolicy \
       --policy-document file://recommended-inline-policy.json
    ```
 1. Create the `system` namespace:
@@ -68,7 +68,7 @@ Run through them again for a second cluster to use with the extended example sho
       --cluster=<my-cluster-name> \
       --namespace=system \
       --name=gateway-api-controller \
-      --attach-policy-arn=<AWSMercuryControllerIAMPolicy ARN CREATED IN CREATE_POLICY STEP> \
+      --attach-policy-arn=<VPCLatticeControllerIAMPolicy ARN CREATED IN create-policy STEP> \
       --override-existing-serviceaccounts \
       --region us-west-2 \
       --approve
@@ -116,7 +116,7 @@ This example creates a single cluster in a single VPC, then configures two route
    ...
    status:
    conditions:
-   message: 'aws-gateway-arn: arn:aws:vpc-service-network:us-west-2:694065802095:mesh/mesh-0d01b22a156d2cc2f' 
+   message: 'aws-gateway-arn: arn:aws:vpc-lattice:us-west-2:694065802095:servicenetwork/sn-0ab6bb70055929edd'
    reason: Reconciled
    status: "True"
    ```
@@ -172,11 +172,11 @@ This example creates a single cluster in a single VPC, then configures two route
 
 1. During preview, you are required to install the VPC Lattice CLI:
    ```bash
-   aws configure add-model --service-model file://scripts/aws_sdk_model_override/models/apis/mercury/2021-08-17/api-2.json —service-name ec2-lattice
+   aws configure add-model --service-model file://scripts/aws_sdk_model_override/models/apis/vpc-lattice/2022-11-30/api-2.json --service-name vpc-lattice
    ```
 1. Use the VPC Lattice CLI to find the DNS name. You can use the `curl` command to get information about each service by adding the service name to the end of the HTTPRoute DNS name. Those names are gathered from AWS Route53 instead of Kubernetes CoreDNS.
    ```bash
-   aws ec2-lattice list-services \
+   aws vpc-lattice list-services \
      --endpoint-url=https://vpc-service-network.us-west-2.amazonaws.com (https://vpc-service-network.us-west-2.amazonaws.com/)
    ```
    ```
@@ -225,12 +225,12 @@ This example creates a single cluster in a single VPC, then configures two route
    ```
    Requesting to Pod(parking-6cdcd5b4b4-g8dkb): parking handler pod
    ```
-1. From inside of the pod, use `curl` to connect to the review service:
+1. From inside of the pod, use `curl` to connect to the inventory service:
    ```bash
-   curl rates-00422586e3362607e.7d67968.vpc-service-network-svcs.us-west-2.amazonaws.com/review 
+   curl rates-00422586e3362607e.7d67968.vpc-service-network-svcs.us-west-2.amazonaws.com/inventory 
    ```
    ```
-   Requesting to Pod(review-5888566ff6-89fqk): review handler pod
+   Requesting to Pod(inventory-5888566ff6-89fqk): inventory handler pod
    ```
 1. Exit the pod:
    ```bash
@@ -356,7 +356,6 @@ With VPC Lattice you can also avoid some of these common problems:
 As a Kubernetes user, you can have a very Kubernetes-native experience using the VPC Lattice APIs.
 The following figure illustrates how VPC Lattice object connect to [Kubernetes Gateway API](https://gateway-api.sigs.k8s.io/) objects:
 
-TODO: Replace with new figure from end of this slide deck: https://amazon.awsapps.com/workdocs/index.html#/document/6398b63682b6fae1ac462edde9af07acc45014557df1dd92b32ccc2c6a744de5
 [Image: VPCLatticeToKubernetesGatewayAPI.png]
 
 As shown in the figure, there are different personas associated with different levels of control in VPC Lattice.
@@ -370,5 +369,3 @@ Notice that the Kubernetes Gateway API syntax is used to create the gateway, HTT
 
 ## Further information
 
-TODO: Add links to other docs, blogs, or software (will any be ready in time for re:Invent?)
-