You are right on the money that Airwave can do this. Generally my provisioning steps for a new IAP deployment with Airwave is as follows:
1) Bring up my lab IAP with my initial config that I wish to serve as the baseline.
2) Manually connect the 1st IAP to airwave with the appropriate group/organizational string. When you do this, Airwave will automatically import the template configuration which will subsequently be used to push to your other devices.
3) Create my provisioning rules in Aruba Activate which will direct new IAP's to Airwave for their provisioning guidance once they have a valid uplink. (Note if you aren't using Aruba Activate, this is a free service that enables the zero touch provisioning - can provide some detail of you are new to it)
4) Test configuration/firmware push - either with a new site, or a defaulted IAP.
5) Make any modifications to the config, test, repeat!
If you've already got the IAP's live on Airwave, you'd need to move them to the group you'd setup with the corresponding configuration and have them sync the config and check for errors. Note there is a slight lag in feature parity between GA IAP code and what is supported in Airwave so if you're looking to enable GA code feature sets, there is likely to be some mismatches as some of the variables are not yet supported.
Note in current 7.7.5 Airwave code, you can now enable the IAP Gui Config and do this from the familiar IAP Setup screen.
All this to say you are 90% of the way there! Do let us know you're versions of IAP and Airwave if you need so more help.
Cheers, Adam