I’m sorry to here you have been having trouble with archiving your devices data. I hope I can help fix the issue. I did check our logs and found an archiving job that has been erring with an “Access Denied” error. Is this your application id, 59b88b9aec028e00079ef592? If this is not your application then there a few other places I can look, but for the rest of this comment, I’m assuming it is yours.
I would double check your permissions you have for the account on AWS. When you save the archive configuration it checks to see that the bucket exists and that your user can access it. However, it does not specifically check that the user can write to it. Attached is a screenshot of the AWS permission, the only one you should need is the Write Objects permission. The screenshot shows a user with full permission but that is not necessary for archiving to work.
As far as being able to explicitly test the setup, we will be adding a feature to archiving which will allow the user to archive all device data that is currently older than 31 days. This will kick off immediately and begin archiving data. We will also be adding a feature to send out emails to the users if an archive failed to complete. If you have any other suggestions on how to make this feature better, please let us know.
Let me know if this fixes your problem.