Describe example yaml files in docs (#196)

Author: chrisnegus

docs/configure/https.md

@@ -4,6 +4,8 @@ The Getting Started guide uses HTTP (insecure) communications by default.
 Using the examples here, you can change that to HTTPS (secure) communications.
 If you choose, you can further customize your HTTPS connections by adding custom domain names and certificates, as described below.
 
+**NOTE**: You can get the yaml files used on this page by cloning the [AWS Gateway API Controller for VPC Lattice](https://github.com/aws/aws-application-networking-k8) site. The files are in the `examples/` directory.
+
 ### Securing Traffic using HTTPS
 
 By adding https to the amazon-vpc-lattice gateway, you can tell the listener to use HTTPs communications.

docs/deploy.md

@@ -3,6 +3,8 @@
 Follow these instructions to create a cluster and deploy the AWS Gateway API Controller.
 Run through them again for a second cluster to use with the extended example shown later.
 
+**NOTE**: You can get the yaml files used on this page by cloning the [AWS Gateway API Controller for VPC Lattice](https://github.com/aws/aws-application-networking-k8) site. The files are in the `examples/` directory.
+
 1. Set your region and cluster name as environment variables. See the [Amazon VPC Lattice FAQs](https://aws.amazon.com/vpc/lattice/faqs/) for a list of supported regions. For this example, we use `us-west-2`:
    ```bash
    export AWS_REGION=us-west-2

docs/getstarted.md

@@ -8,6 +8,9 @@ Both clusters are created using `eksctl`, with both clusters created from the sa
 
 Using these examples as a foundation, see the [Configuration](configure/index.md) section for ways to further configure service-to-service communications.
 
+
+**NOTE**: You can get the yaml files used on this page by cloning the [AWS Gateway API Controller for VPC Lattice](https://github.com/aws/aws-application-networking-k8) site. The files are in the `examples/` directory.
+
 ## Set up single-cluster/VPC service-to-service communications
 
 This example creates a single cluster in a single VPC, then configures two routes (rates and inventory) and three services (parking, review, and inventory-1). The following figure illustrates this setup: