I don't know if this is just limited to this combo, but Ansible was not properly gathering the facts needed to properly trigger the ec2 tasks when I deployed the latest official CentOS 7 image to the latest burstable instance classes (t3). Basically, a bunch of the ansible_* facts were NA and the default network config fact dict changed names. All of this behavior may change with an Ansible update, but it would be nice to roll in backwards compatible, non-interfering support.
I don't know if this is just limited to this combo, but Ansible was not properly gathering the facts needed to properly trigger the ec2 tasks when I deployed the latest official CentOS 7 image to the latest burstable instance classes (t3). Basically, a bunch of the ansible_* facts were NA and the default network config fact dict changed names. All of this behavior may change with an Ansible update, but it would be nice to roll in backwards compatible, non-interfering support.