[docs] remove references to AWS

Documentation/configure-kubectl.md

@@ -2,9 +2,9 @@
 
 `kubectl` is a command-line program for interacting with the Kubernetes API. The following steps should be done from a local workstation to configure `kubectl` to work with a new cluster.
 
-To quickly launch a cluster, follow these guides for [AWS][kube-aws], [Vagrant][vagrant-multi], or [full step-by-step][manual] instructions. 
+To quickly launch a cluster, follow these guides for [AWS][kube-aws], [Vagrant][vagrant-multi] or [full step-by-step][manual] instructions.
 
-[kube-aws]: kubernetes-on-aws.md
+[kube-aws]: https://github.com/coreos/kube-aws/blob/master/README.md
 [vagrant-multi]: kubernetes-on-vagrant-single.md
 [manual]: getting-started.md
 

Documentation/kubernetes-upgrade.md

@@ -2,7 +2,7 @@
 
 This document describes upgrading the Kubernetes components on a cluster's master and worker nodes. For general information on Kubernetes cluster management, upgrades (including more advanced topics such as major API version upgrades) see the [Kubernetes upstream documentation](http://kubernetes.io/docs/admin/cluster-management.html) and [version upgrade notes](https://github.com/kubernetes/kubernetes/blob/release-1.4/docs/design/versioning.md#upgrades)
 
-**NOTE:** The following upgrade documentation is for installations based on the CoreOS + Kubernetes step-by-step [installation guide](https://coreos.com/kubernetes/docs/latest/getting-started.html). Upgrade documentation for the AWS cloud-formation based installation is forthcoming.
+**NOTE:** The following upgrade documentation is for installations based on the CoreOS + Kubernetes step-by-step [installation guide](https://coreos.com/kubernetes/docs/latest/getting-started.html).
 
 ## Upgrading the Kubelet
 

README.md

@@ -16,7 +16,6 @@ When designing these guides and tools, the following considerations are made:
 * An individual node can reboot and the cluster will still function
 * Internal cluster DNS is available
 * Service accounts enabled
-* Use a cloud-provider if we can, for instance on AWS
 * Follow Kubernetes guidelines for AdmissionControllers and other suggested configuration
 
 ## Kubernetes Topics
@@ -34,7 +33,6 @@ https://coreos.com/kubernetes/docs/latest/
 - [Step-by-Step for Any Platform](Documentation/getting-started.md)
 - [Single-Node Vagrant Stack](single-node/README.md)
 - [Multi-Node Vagrant Cluster](multi-node/vagrant/README.md)
-- [Multi-Node AWS Cluster](https://github.com/coreos/kube-aws)
 - [Multi-Node Bare Metal Cluster](Documentation/kubernetes-on-baremetal.md)
 
 ## Running Kubernetes Conformance Tests

multi-node/aws/README.md

@@ -0,0 +1,3 @@
+# kube-aws has moved!
+
+https://github.com/coreos/kube-aws