From 734170013c4511eb506a3dcb28eee2e57da0a7c7 Mon Sep 17 00:00:00 2001
From: ashleyhull-versent <ashley.hull@versent.com.au>
Date: Wed, 5 Sep 2018 23:07:28 +1000
Subject: [PATCH] ROUTE53: Documentation for AWS Token PR (#403)

* Update route53Provider.go

* includes optional Token

* Appended Token and additional information for
---
 docs/_providers/route53.md         | 13 ++++++++++++-
 docs/assets/creds.json-example.txt |  3 ++-
 2 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/docs/_providers/route53.md b/docs/_providers/route53.md
index 69535f97d..a519e960a 100644
--- a/docs/_providers/route53.md
+++ b/docs/_providers/route53.md
@@ -12,7 +12,8 @@ You can specify the API credentials in the credentials json file:
 {
  "r53_main":{
       "KeyId": "your-aws-key",
-      "SecretKey": "your-aws-secret-key"
+      "SecretKey": "your-aws-secret-key",
+      "Token": "optional-sts-token"
  }
 }
 {% endhighlight %}
@@ -22,8 +23,18 @@ You can also use environment variables, but this is discouraged, unless your env
 ```
 $ export AWS_ACCESS_KEY_ID=XXXXXXXXX
 $ export AWS_SECRET_ACCESS_KEY=YYYYYYYYY
+$ export AWS_SESSION_TOKEN=ZZZZZZZZ
 ```
 
+{% highlight json %}
+{
+ "r53_main":{
+      "KeyId": "$AWS_ACCESS_KEY_ID",
+      "SecretKey": "$AWS_SECRET_ACCESS_KEY"
+ }
+}
+{% endhighlight %}
+
 You can find some other ways to authenticate to Route53 in the [go sdk configuration](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html).
 
 ## Metadata
diff --git a/docs/assets/creds.json-example.txt b/docs/assets/creds.json-example.txt
index 34bbea84c..ac6bb4352 100644
--- a/docs/assets/creds.json-example.txt
+++ b/docs/assets/creds.json-example.txt
@@ -3,6 +3,7 @@
   },
   "r53_ACCOUNTNAME": {
     "KeyId": "change_to_your_keyid",
-    "SecretKey": "change_to_your_secretkey"
+    "SecretKey": "change_to_your_secretkey",
+    "Token": "optional_sts_token"
   }
 }