DOC/MINOR: discovery: adding configuration file snippets for YAML format

Author: prometherion

discovery/AWS.md

@@ -45,6 +45,22 @@ service_discovery {
 }
 ```
 
+```yaml
+  aws_regions:
+  - description: "Allowlist example"
+    allowlist:
+      - key: tag-key
+        value: "Must:Have:This:Tag:Key"
+    enabled: false
+    id: 96b14c57-b011-42e5-8d01-b58feba07319
+    name: john.doe
+    region: "us-east-1"
+    retrytimeout: 10
+    serverslotsbase: 10
+    serverslotsgrowthincrement: 10
+    serverslotsgrowthtype: exponential
+```
+
 As `allowlist`, the `denylist` option allows to filter out specific instances matching the desired filters.
 
 ```hcl
@@ -77,6 +93,25 @@ service_discovery {
 }
 ```
 
+```yaml
+  aws_regions:
+  - description: "Denylist example"
+    allowlist:
+      - key: tag-key
+        value: "Must:Have:This:Tag:Key"
+    denylist:
+      - key: "tag:Environment
+        value: Development"
+    enabled: false
+    id: 96b14c57-b011-42e5-8d01-b58feba07319
+    name: john.doe
+    region: "us-east-1"
+    retrytimeout: 10
+    serverslotsbase: 10
+    serverslotsgrowthincrement: 10
+    serverslotsgrowthtype: exponential
+```
+
 ## Authorization
 
 Data Plane API needs the plain AWS credentials to interact with it.
@@ -101,6 +136,21 @@ service_discovery {
 }
 ```
 
+```yaml
+  aws_regions:
+  - description: "Credentials example"
+    secretaccesskey: "************************************soLl"
+    accesskeyid: "****************L7GT"
+    enabled: false
+    id: 96b14c57-b011-42e5-8d01-b58feba07319
+    name: john.doe
+    region: "us-east-1"
+    retrytimeout: 10
+    serverslotsbase: 10
+    serverslotsgrowthincrement: 10
+    serverslotsgrowthtype: exponential
+```
+
 > In case of Data Plane API running in an EC2 with a IAM Role attached (as [`AmazonEC2ReadOnlyAccess`](https://console.aws.amazon.com/iam/home#/policies/arn:aws:iam::aws:policy/AmazonEC2ReadOnlyAccess$serviceLevelSummary)), there's no need for additional credentials.
 
 ## Server options
@@ -158,6 +208,16 @@ service_discovery {
 }
 ```
 
+```yaml
+  aws_regions:
+  - enabled: true
+    name: john.doe
+    region: "us-east-1"
+    secretaccesskey: "************************************soLl"
+    ipv4address: private
+    retrytimeout: 60
+```
+
 The resulting output will be the following, YMMV.
 
 ```
@@ -208,6 +268,17 @@ service_discovery {
 }
 ```
 
+```yaml
+  aws_regions:
+  - accesskeyid: "****************L7GT"
+    enabled: false
+    name: my-service-discovery
+    region: "us-east-1"
+    secretaccesskey: "****************soLl"
+    ipv4address: private
+    retrytimeout: 60
+```
+
 As a result of this action, Data Plane API will not update the discovered `backend` sections and their `server` entries: no data will be lost.
 
 > Potentially, due to the spawn of newer EC2 instances or reboots with a change of the IPv4 address, data could be outdated.