move and revise AWS constraints (#846)

* move and revise AWS constraints

* revise intro

* fixup

* fixup

* remove note

* remove note

* move and revise AWS constraints

* revise intro

* fixup

* fixup

* remove note

* move requirements to provisioner page

* revised moved content

* feedback from jicowan

* fix typos

* revise

* Apply suggestions from code review

Co-authored-by: Chris Negus <cnegus@redhat.com>
Co-authored-by: Ellis Tarn <ellistarn@gmail.com>

* fixup

* Update website/content/en/pre-docs/provisioner-crd.md

Co-authored-by: Ellis Tarn <ellistarn@gmail.com>

* Update website/content/en/pre-docs/provisioner-crd.md

Co-authored-by: Ellis Tarn <ellistarn@gmail.com>

Co-authored-by: Chris Negus <cnegus@redhat.com>
Co-authored-by: Ellis Tarn <ellistarn@gmail.com>

website/content/en/pre-docs/AWS/constraints.md

@@ -0,0 +1,144 @@
+---
+title: "Provisioning Configuration"
+linkTitle: "Provisioning"
+weight: 10
+---
+
+## spec.provider
+
+This section covers parameters of the AWS Cloud Provider.
+
+[Review these fields in the code.](https://github.com/awslabs/karpenter/blob/main/pkg/cloudprovider/aws/apis/v1alpha1/provider.go#L33)
+
+### InstanceProfile
+An `InstanceProfile` is a way to pass a single IAM role to an EC2 instance.
+
+It is required, and specified by name. A suitable `KarpenterNodeRole` is created in the getting started guide.
+
+```
+spec:
+  provider:
+    instanceProfile: MyInstanceProfile
+```
+
+### LaunchTemplate
+
+A launch template is a set of configuration values sufficient for launching an EC2 instance (e.g., AMI, storage spec).
+
+A custom launch template is specified by name. If none is specified, Karpenter will automatically create a launch template.
+
+Review the [Launch Template documentation](launch-templates.md) to learn how to create a custom one.
+
+```
+spec:
+  provider:
+    launchTemplate: MyLaunchTemplate
+```
+
+### SubnetSelector
+
+Karpenter discovers subnets using [AWS tags](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html). 
+
+Subnets may be specified by any AWS tag, including `Name`. Selecting tag values using wildcards ("*") is supported.
+
+
+When launching nodes, Karpenter automatically chooses a subnet that matches the desired zone. If multiple subnets exist for a zone, one is chosen randomly.
+
+**Examples**
+
+Select all subnets with a specified tag:
+```
+  subnetSelector:
+    kubernetes.io/cluster/MyCluster: '*'
+```
+
+Select subnets by name:
+```
+  subnetSelector:
+    Name: subnet-0fcd7006b3754e95e
+```
+
+Select subnets by an arbitrary AWS tag key/value pair:
+```
+  subnetSelector:
+    MySubnetTag: value
+
+Select subnets using wildcards:
+```
+  subnetSelector:
+    Name: *public* 
+
+```
+
+### SecurityGroupSelector
+
+The security group of an instance is comparable to a set of firewall rules.
+If no security groups are explicitly listed, Karpenter discovers them using the tag "kubernetes.io/cluster/MyClusterName", similar to subnet discovery.
+
+EKS creates at least two security groups by default, [review the documentation](https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html) for more info.
+
+Security groups may be specified by any AWS tag, including "name". Selecting tags using wildcards ("*") is supported.
+
+‼️ When launching nodes, Karpenter uses all of the security groups that match the selector. The only exception to this is security groups tagged with the label `kubernets.io/cluster/MyClusterName`. The AWS Load Balancer controller requires that *only a single security group with this tag may be attached to a node*. In this case, Karpenter selects randomly.
+
+**Examples**
+
+Select all security groups with a specified tag:
+```
+spec:
+  provider:
+    securityGroupSelector:
+      kubernetes.io/cluster/MyKarpenterSecurityGroups: '*'
+```
+
+Select security groups by name, or another tag:
+```
+ securityGroupSSelector:
+   Name: sg-01077157b7cf4f5a8
+   MySecurityTag: '' # matches all resources with the tag
+```
+
+Select security groups by name using a wildcard:
+```
+ subnetSelector:
+   Name: *public*
+```
+
+### Tags
+
+Tags will be added to every EC2 Instance launched by this provisioner.
+
+```
+spec:
+  provider:
+    tags:
+      InternalAccountingTag: 1234
+      dev.corp.net/app: Calculator
+      dev.corp.net/team: MyTeam
+```
+
+## Other Resources
+
+### Accelerators, GPU
+
+Accelerator (e.g., GPU) values include
+- `nvidia.com/gpu`
+- `amd.com/gpu`
+- `aws.amazon.com/neuron`
+
+Karpenter supports accelerators, such as GPUs.
+
+
+Additionally, include a resource requirement in the workload manifest. This will cause the GPU dependent pod will be scheduled onto the appropriate node.
+
+*Accelerator resource in workload manifest (e.g., pod)*
+
+```yaml
+spec:
+  template:
+    spec:
+      containers:
+      - resources:
+          limits:
+            nvidia.com/gpu: "1"
+```