anchor.diff:  
   Pod will be using this role to request IAM credentials during runtime.
   
  +. Edit `templates/deplloymnet-with-vault.yaml` to replace `<public-ip-address>` with the public IP address of the EC2 instance where Vault server is running.
   . Create the Pod:
   
     $ kubectl apply -f templates/deployment-with-vault.yaml
  
positive.code:           "Path": "/", 
            "CreateDate": "2017-11-22T20:13:39.273Z", 
            "UserId": "AIDAI6SQOXCLURVV2J7BK", 
            "Arn": "arn:aws:iam::091144949931:user/vault-root"
        }
    }
  
  
negative.code: +
  And this shows the listing of S3 buckets in your account.
  +
  . Kubernetes Auth backend is configured for the token to expire in 60 seconds. This was done during Kubernetes Auth backend configuration by setting the `-period=60s` on the `vault write auth/kubernetes/role/demo` command. This means the temporary IAM role created for this Deployment will eventually disappear. Trying to access the S3 listing after a few minutes will give an error:
  +
  ```
  $ kubectl exec -it $(kubectl get pods -l app=vault-sidecar -o jsonpath={.items[0].metadata.name}) aws s3 ls
  