Error on Article #000006316 vSZ on AWS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2019 07:48 AM
I just went through this exercise and it took me a while to find the mistake. There is an error on the .docx attached for the above mentioned article.

https://support.ruckuswireless.com/articles/000006316Specifically, steps 7. On this step a reference to creating a JSON file called role-policy.json where the unix/linux command to create it calls it role-policy-json and the awscli command to apply it is also looking for role-policy.json, you will get an error.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2019 08:00 AM
Thank you for pointing to the error. Will correct it shortly.
Regards,
-Ankush
Regards,
-Ankush
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2019 08:08 AM
I have made the changes in the KBA Document. It will reflect on the support portal in a day.
Regards.
-Ankush
Regards.
-Ankush
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2019 08:11 AM
Please refer to the below video on installing the vSZ on AWS.
https://www.youtube.com/watch?v=JaXgHThbyT0&t=143s
- Anusha
https://www.youtube.com/watch?v=JaXgHThbyT0&t=143s
- Anusha
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2019 06:39 PM
This method of setting up the vSZ on AWS isn't great because you don't get any interaction with AWS. There is no cloud-init or aws-cloudformation-bootstrap. I got close to getting it set up but there were many painful roadblocks in the way and I never quite got it working properly. I got as far as finding the locked filesystem, which stops cloud-init running once it is installed. The filesystem can be mounted locally and you will get full shell access if you make sure the shell script for the CLI is not available on initialization. Is proper AWS support going to be available in the future?

