Kitchen.aws.yml (using aws driver for kitchen testing)

---

driver:

  name: ec2

  aws_ssh_key_id: private_key

  security_group_ids: ["sg-xxxxxxxxxxxx”]

  region: us-xxxxxxxxxxx

  availability_zone: a

  require_chef_omnibus: true

  subnet_id: subnet-XXXXXXXXXXXXX

  instance_type: t2.nano

  associate_public_ip: true

  interface: private

  tags:

    Name: test-kitchen-cookbookname (it will be easy to identify)

    application_name: chef-testing

  block_device_mappings: 

    - device_name: /dev/xxxxxxx

      ebs:

        volume_size: 5    (disk size)

        delete_on_termination: true  

transport:

  # username: centos

  ssh_key: ~/.ssh/private_key(.pem)

  connection_timeout: 10

  connection_retries: 5

verifier:

  name: inspec

provisioner:

  name: chef_solo

  roles_path: ../../roles

  data_bags_path: ../../data_bags

  environments_path: ../../environments

  cookbook_path: ../../cookbooks

  always_update_cookbooks: true

platforms:

  - name: centos-6

  # - name: centos-7

suites:

  - name: default

    run_list:

      - recipe[cookbookname::xxxxxxxxxx(recipe)]

    verifier:

      inspec_tests:

        - test/smoke/default

    attributes:


---------------------

How to use the kitchen commands when we use the ec2-driver?

Kitchen converge:

KITCHEN_YAML=".kitchen.aws.yml" kitchen converge default-centos-7

Kitchen list:

KITCHEN_YAML=".kitchen.aws.yml" kitchen list default-centos-7

Kitchen login:

KITCHEN_YAML=".kitchen.aws.yml" kitchen login default-centos-7

(this is how, we have to execute the kitchen commands).