Merge pull request #320 from kmala/master

docs(s3): add instruction for using IAM creds

Author: kmala

src/installing-workflow/configuring-object-storage.md

@@ -32,6 +32,7 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
             ```
             export AWS_ACCESS_KEY, AWS_SECRET_KEY, AWS_REGISTRY_BUCKET, AWS_DATABASE_BUCKET, AWS_BUILDER_BUCKET, S3_REGION
             ```
+              * To use [IAM credentials][aws-iam], it is not necessary to set `AWS_ACCESS_KEY` or `AWS_SECRET_KEY`.
 
           * For `STORAGE_TYPE=azure`:
 
@@ -144,3 +145,4 @@ Azure (`DATABASE_STORAGE=azure`):
 
 [minio]: ../understanding-workflow/components.md#object-storage
 [generate-params-toml]: https://github.com/deis/charts/blob/master/workflow-dev/tpl/generate_params.toml
+[aws-iam]: http://docs.aws.amazon.com/IAM/latest/UserGuide/introduction.html

src/managing-workflow/production-deployments.md

@@ -10,9 +10,9 @@ Workflow makes use of [Minio][] to provide storage for the [Registry][], [Databa
 [Logger][] components. Minio is provided out of the box as a central storage compartment, but it is
 not resilient to cluster outages. If Minio is shut down, all data is lost.
 
-In production, persistent storage can be achieved by running an external S3-compatible blob store.
-For users on AWS, the convenience of Amazon S3 and make the prospect of running a Minio-less
-Workflow cluster quite reasonable.
+In production, persistent storage can be achieved by running an external object store.
+For users on AWS, GCE/GKE or Azure, the convenience of Amazon S3, Google GCS or Microsoft Azure Storage
+makes the prospect of running a Minio-less Workflow cluster quite reasonable.
 
 Running a Workflow cluster without Minio provides several advantages:
 

src/understanding-workflow/components.md

@@ -75,9 +75,9 @@ processes.
 
 **Project Location:** [deis/minio](https://github.com/deis/minio)
 
-All of the Workflow components ship their persistent data to cluster configured
-S3 compatibile Object Storage. For example, database ships its WAL files,
-registry stores Docker images, and slugbuilder stores slugs.
+All of the Workflow components that need to persist data will ship them to the
+object storage that was configured for the cluster.For example, database ships
+its WAL files, registry stores Docker images, and slugbuilder stores slugs.
 
 Workflow supports either on or off-cluster storage. For production deployments
 we highly recommend that you configure [off-cluster object storage][configure-objectstorage].