anchor.diff:    $ vault mount aws
     Successfully mounted 'aws' at 'aws'!
   
  -. Configure the aws secret backend:
  +. Configure the AWS secret backend:
   
     $ vault write aws/config/root \
       secret_key=<secret-key> \
  
positive.code: +
  Note that the `kube2iam-ds.yaml` is assuming that your network configuration is based on `kubenet`, which is also the default kops configuration. If you have changed this as part of another exercise (e.g. switched to Calico) you will need to change the value of the `--host-interface` arg in the configuration file. For example, set to `cal+` if using Calico.
  
  === IAM Roles for worker nodes
  
  It is necessary to create an IAM role which can assume other roles and assign it to each kubernetes worker.
  
  We need the link:https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html[Amazon Resource Name (ARN)] of the IAM Role assigned to the worker nodes.  We will need this as part of creating pod roles.  We can obtain this by running the following command:
  
  
negative.code: $ aws iam create-access-key \
       --user-name vault-root
  
    {
        "AccessKey": {
            "UserName": "vault-root", 
            "Status": "Active", 
            "CreateDate": "2017-11-22T20:14:00.682Z", 
            "SecretAccessKey": "<secret-key>", 
            "AccessKeyId": "<access-key>"
        }
    }
  
  === Setup Vault
  
  