HACKATHON

IT’S ON!

The first-ever Ignite Virtual Hackathon has begun!

Yep, it’s a virtual hackathon contest to develop innovative solutions to vexing challenges for securing public cloud workloads on Amazon® Web Services (AWS®) or Microsoft® Azure® using our VM-Series firewalls.

Do you have the skills? Because this thing is about to get very, very real!
Enter the Ignite Virtual Hackathon to win some very cool prizes while showcasing your mad automation and scripting chops to your peers!

Your challenge: Create scripts or templates to streamline VM-Series deployment workflows and secure your applications and data on AWS or Azure. For example:

  • Eliminate manual implementation steps using AWS Lambda or Azure Functions.
  • Accelerate your public cloud deployments using VM-Series APIs bootstrapping Cloud Formation or ARM Templates.
  • Automate the creation of a scalable, highly available environment across multiple regions.

Your scripts can utilize any AWS or Azure Services as well as any and all third-party tools, such as Chef and Puppet along with all of the VM-Series APIs and bootstrapping.

Submit your entry by June 1, 2017 to be eligible to win a Mavic Pro Drone, an Oculus Rift® + Touch, or a pair of Bose® QuietComfort 35 Wireless Headphones. Prizes will be awarded for both AWS and Azure categories. Winners will be selected based on:

  • Level of innovation and automation.
  • Complexity of problem being solved.
  • Clear demonstration of the solution.
  • Integration with native cloud services.
  • Ease of use and completeness of documentation.


The winning solutions for both AWS and Azure (three for each category) will be announced publicly at Ignite on Tuesday, June 13, 2017. We’ll notify the winners in advance so they can prepare a brief presentation to be delivered during the Virtual Hackathon breakout session at Ignite ’17, either live at the conference or via video submission.

Submission Guidelines:

  • Post your solution to GitHub, submit your entry here, and abide by the official contest rules and regulations which you can find here.
  • Include a description (250 words or less) in a README file on GitHub, as well as any necessary documentation and/or a video demo

So what are you waiting for? SUBMIT YOUR ENTRY

Resources to get you started:

Register Now