Testing the new iam_profile_name, which I understand can be used to set the role when creating a new instance via kitchen-ec2 I updated the corresponding .kitchen.yml file, but the instance does not get any role assigned. Folowing is the config I used and the results from the created instance. I am thinking maybe I missed something obvious that I can't see?
Luis-Cosmes-MacBook-Pro:ffdc-common lcosmes$ head .kitchen.yml
---
driver:
name: ec2
aws_ssh_key_id: [my_ssh_key_id]
region: us-east-1
availability_zone: us-east-1b
security_group_ids: ["sg-YYYYYY"]
subnet_id: "subnet-aaaaaaa"
instance_type: t2.small
iam_profile_name: master
* "master" role exists in IAM *
Luis-Cosmes-MacBook-Pro:ffdc-common lcosmes$ aws iam get-role --role-name master --query 'Role.{RoleName:RoleName,Arn:Arn}'
{
"RoleName": "master",
"Arn": "arn:aws:iam::663255216447:role/master"
}
* kitchen converge creates the new instance, and doesn't spit any errors *
Luis-Cosmes-MacBook-Pro:ffdc-common lcosmes$ kitchen converge def
-----> Starting Kitchen (v1.4.0)
$$$$$$ WARN: The driver[Kitchen::Driver::Ec2] config key `username` is deprecated, please use `transport.username`
-----> Creating <default-amazon>...
Creating <>...
If you are not using an account that qualifies under the AWS
free-tier, you may be charged to run these suites. The charge
should be minimal, but neither Test Kitchen nor its maintainers
are responsible for your incurred costs.
Instance <i-b517ad65> requested.
EC2 instance <i-b517ad65> created.
...
* The created instance, however, does not contain a role *
Luis-Cosmes-MacBook-Pro:ffdc-common lcosmes$ aws ec2 describe-instances --instance-ids i-b517ad65 --query 'Reservations[*].Instances[*].IamInstanceProfile'
[
[]
]