Deployment fails when using splunk AMI 8.1.0

[sourabhparvatikar]

When I change the AMI used in the template for us-west-2 to latest Splunk AMI (splunk_AMI_8.1.0_2020-10-19_17-02-46-7b65de6c-5006-4ca2-bd75-fdba95ae5d9d-ami-0841021191958485f.4 - ami-00ec39a01d30f499a), the userdata scripts fail since the new AMI installs splunk files and data after the launch while the old AMI had everything installed before userdata scripts executed

[lmsilvero]

Hi, same happened to me with the version 8.2.2 Ami Id: ami-04bd6f47d7c4931fc. It seems like the ansible playbooks runs after of user data code. I've tried to put a waiter condition for a cloud-init like this
"while [ ! -f /var/lib/cloud/instance/boot-finished ]; do echo 'Waiting for cloud-init...'; sleep 1; done\n"
but it was not a good solution.
Anyone know how to fix it with the new AMIs?