anchor.diff:          resource_directory_key: YOUR-AWS-RESOURCE-BUCKET
           fog_connection: *fog_connection
       ```
  -1. Replace `AWS_ACCESS_KEY` and `AWS_SECRET_ACCESS_KEY` with your AWS credentials, and `YOUR-AWS-BUILDPACK-BUCKET`, `YOUR-AWS-DROPLET-BUCKET`, `YOUR-AWS-PACKAGE-BUCKET`, `YOUR-AWS-RESOURCE-BUCKET` with the names of your AWS buckets. Do not use periods (`.`) in your AWS bucket names. In the AWS console, you must assign your credentials an IAM policy that allows all S3 actions on all of these buckets.
  -
  -1. Further configuration can be provided through the <code>fog_connection</code> hash, which is passed through to the Fog gem.
  +1. Replace `AWS_ACCESS_KEY` and `AWS_SECRET_ACCESS_KEY` with your AWS credentials.
  +
  +1. Replace `YOUR-AWS-BUILDPACK-BUCKET`, `YOUR-AWS-DROPLET-BUCKET`, `YOUR-AWS-PACKAGE-BUCKET`, and `YOUR-AWS-RESOURCE-BUCKET` with the names of your AWS buckets. Do not use periods (`.`) in your AWS bucket names. In the AWS console, you must assign your credentials an IAM policy that allows all S3 actions on all of these buckets. 
  +
  +1. You can provide further configuration through the <code>fog_connection</code> hash, which is passed through to the Fog gem.
   
   ##<a id="fog-aws-sse"></a> Fog with AWS Server-Side Encryption
   
  
positive.code: 
  <strong><%= modified_date %></strong>
  
  This topic describes the various options for configuring a blobstore for the Cloud Controller.
  
  Cloud Controller has four types of objects that need to be stored in a blobstore: <code>buildpacks</code>, <code>droplets</code>, <code>packages</code>, and <code>resource_pool</code>. By default, the blobstore configuration uses the Fog Ruby gem, but can also use the WebDAV protocol.
  
  This document demonstrates five common blobstore configurations: 
  
  * [Fog with AWS Credentials](#fog-aws-creds)
  * [Fog with AWS Server Side Encryption](#fog-aws-sse)
  
negative.code:         resource_directory_key: YOUR-AWS-RESOURCE-BUCKET
          fog_connection: *fog_connection
      ```
  1. Replace `YOUR-AWS-BUILDPACK-BUCKET`, `YOUR-AWS-DROPLET-BUCKET`, `YOUR-AWS-PACKAGE-BUCKET`, and `YOUR-AWS-RESOURCE-BUCKET` with the names of your AWS buckets. Do not use periods (`.`) in your AWS bucket names. 
  
  1. To provide further configuration, create a <code>fog_connection</code> hash to pass through to the Fog gem.
  
  1. Complete the steps documented in the <a href="http://bosh.io/docs/aws-iam-instance-profiles.html#director-with-s3-blobstore">AWS CPI and Director configured with an S3 blobstore instructions</a> section of the BOSH documentation.
  
  1. In the AWS console, configure an additional <code>cloud-controller</code> IAM role that gives access to both the BOSH S3 buckets and the Cloud Controller S3 buckets specified in your manifest:
  
      ```
      {
        "Version": "2012-10-17",
        "Statement": [{
          "Effect": "Allow",
          "Action": [ "s3:*" ],
          "Resource": [
            "arn:aws:s3:::BOSH_BUCKET_NAME",
            "arn:aws:s3:::BOSH_BUCKET_NAME/*",
            "arn:aws:s3:::YOUR-AWS-BUILDPACK-BUCKET",
            "arn:aws:s3:::YOUR-AWS-BUILDPACK-BUCKET/*",
            "arn:aws:s3:::YOUR-AWS-DROPLET-BUCKET",
            "arn:aws:s3:::YOUR-AWS-DROPLET-BUCKET/*",
            "arn:aws:s3:::YOUR-AWS-PACKAGE-BUCKET",
            "arn:aws:s3:::YOUR-AWS-PACKAGE-BUCKET/*",
            "arn:aws:s3:::YOUR-AWS-RESOURCE-BUCKET",
            "arn:aws:s3:::YOUR-AWS-RESOURCE-BUCKET/*",
          ]
        }]
      }
      ```
  If you are using the AWS console, an IAM Role is automatically assigned to an IAM Instance Profile with the same name, <code>cloud-controller</code>. If you are not using the AWS console, you must create an IAM Instance Profile with a single assigned IAM Role.
  
  1. In your Cloud Foundry deployment manifest, configure a resource pool to use the <code>cloud-controller</code> IAM Instance Profile:
  
      ```
      resource_pools:
      - name: cloud-controller-resource-pool
        network: default
        stemcell: { ... }
        cloud_properties:
          instance_type: c3.large
          iam_instance_profile: cloud-controller
      ```
  1. Assign all Cloud Controller jobs, identified by <code>api\_z\*</code>, and Cloud Controller Worker jobs, identified by <code>api\_worker\_z\*</code>, to the <code>cloud-controller-resource-pool</code>.
  
  ##<a id="fog-gcs"></a>Fog with Google Cloud Storage
  
  To configure your blobstores to use Google Cloud Storage Interoperability credentials, perform the steps below.
  
  1. Insert the following configuration into your manifest under `properties.cc`:
  
  