No Server November: Join the #noServerNovember challenge!

Ah, November. The month of re:Invent, pumpkin spice, and now: the #noServerNovember challenge.

Every week this month, we're releasing some Serverless Challenges that are designed to help experienced users level up, and brand new users get started. Do one, or three, for fun in your spare time!

If you do any of the challenges and tweet a link to your GitHub repo with the hashtag #noServerNovember, you just might win some official Serverless swag.

Be sure to check the rules before submitting!

As a side note, we also have a Serverless Examples Explorer on our website. So if you complete a challenge and feel good about it, submit it to our Examples Repo! It might get featured on serverless.com.

The challenges

There are currently 9 challenges and 1 hackathon to choose from!

Nov 26: Special edition re:Invent hackathon!

We've got even cooler prizes this week for our hackathon entrants. The re:Invent virtual hackathon can be done from anywhere, on a team or not on a team, however you want to enter.

Check out the hackathon assignment and get building!

Nov 19: Twilio reminder, Slack bot, stock ticker

Make an SMS reminder bot with Twilio.

Beginner track

Create a serverless-backed Twilio reminder bot that sends you a text message. Have it tell you to take out the trash. Or move your car to avoid parking tickets. Or text your mom happy birthday.

Here are some resources to get you started:

How to avoid parking tickets with Serverless

How to submit to the Reminder Bot challenge:

Tweet the link to your GitHub repo with a screenshot of the sent text message.
Include the hashtag #noServerNovember.

Make a Slack bot that suggests a random 80s action flick.

Intermediate/Advanced track

Create a serverless-backed Slack bot. Users should be able to type a slash command (such as /action), and receive the name of a random action flick.

Bonus points if you include the cover art, a link to the IMDB / Rotten Tomatoes page, a quote, or really anything else that makes it more robust.

Here are some resources to get you started:

How to submit to the 80s Action Flick challenge:

Tweet the link to your GitHub repo with a screenshot of the bot in action.
Include the hashtag #noServerNovember.

Create a cron + ETL-backed stock ticker.

Intermediate/Advanced track

Create a serverless-backed cron job that runs an ETL script to pull data from one SaaS service into another. For example, a phone number you can text to receive stock (or for additional buzzword bonus points, crypto) price information. We recommend going Twitter -> serverless backend (AWS Lambda, Microsoft Azure, or Google Cloud Functions) ->

Here are some resources to get you started:

ETL job processing with Serverless and redshift

How to submit to the Stock Ticker challenge:

Tweet the link to your GitHub repo and a screenshot of your Stock Ticker in action.
Include the hashtag #noServerNovember.

Nov 12: Cute Cats, Alexa skill, AnimalBot

Make a website that serves visitors cute cat gifs.

Beginner track

Make a website. On that website, pull in a random cat gif. At its most basic, the gif should change every time the page is refreshed. Bonus points if you create a custom domain name.

Here are some resources to get you started:

How to submit to the Cute Cat challenge:

Tweet the link to your GitHub repo and your Cute Cat webpage.
Include the hashtag #noServerNovember.

Build an Alexa skill that tells you a random fact about One Direction.

Intermediate/Advanced track (fun version)

Make a serverless-backed Alexa skill. When you say, “Alexa, tell me something about One Direction,” or “Alexa, hit me with some One Direction facts,” Alexa should answer you and tell you a random fact about One Direction.

Here are some resources to get you started:

Here are some One Direction facts; you’ll need to convert this to a database
Search Alexa examples in the Serverless Examples Explorer
Building Alexa skills with the Serverless Bespoken plugin
How to build a serverless Alexa skill

How to submit to the One Direction challenge:

Tweet the link to your GitHub repo, ideally also with a video (or sound clip) of the Alexa skill working, because that is way more fun.
Include the hashtag #noServerNovember.

Create a Twitter bot that recognizes animals in images.

Advanced track

Make a serverless, image-recognition-backed Twitter bot. When a user tweets at the bot: “@animalbot, what’s in this image?”, the bot should reply with the name of the animal, “It’s a panda!”

Here are some resources to get you started:

How to submit to the AnimalBot challenge:

Tweet the link to your GitHub repo and AnimalBot account.
Include the hashtag #noServerNovember.

Nov 5: Serverless Ipsum, DadJokeBot, GitHub Check

We've got three challenges this week to suit all levels! The Serverless Ipsum challenge can be done even if you've never set up an AWS account before, and have never coded anything in your life.

Every challenge you complete gets you one entry into the drawing.

Build a Serverless Ipsum generator.

Beginner track

Build a simple serverless-backed web app that displays Serverless Ipsum when it is loaded. Or Tony Danza Ipsum. Or The Office Ipsum. Or Reasons-I-Can’t-Take-Out-The-Trash Ipsum.

As long as it looks like Lorem Ipsum, but uses different words, we’re good. The page doesn’t have to look fancy, and you can do this even if you’ve never coded anything in your life!

Here’s a tutorial to get you started:

I just deployed a Serverless app—and I can’t code

Plus, some inspiration for all of you not-a-developer-yet-but-learning types:

From chef to Serverless developer in 4 years

How to submit to the Serverless Ipsum challenge:

Tweet the link to your GitHub repo and your Ipsum webpage.
Include the hashtag #noServerNovember.

Make a Twitter bot that tweets dad jokes.

Intermediate/Advanced track (fun version)

Write a serverless-backed Twitter bot. Make it tweet dad jokes. That’s really all there is to it.

Here are some helpful links to get you started:

How to submit to the DadBot Twitter challenge:

Tweet the link to your GitHub repo and your DadBot account.
Include the hashtag #noServerNovember.

Automate a GitHub Check with Serverless.

Intermediate/Advanced track (actually useful (!!!) version)

This project is one of our favorites around the office, for its sheer usability. Automating anything to do with GitHub is just incredibly useful.

For the easy version, set up a GitHub check that makes sure there’s a reference to a GitHub / Jira / etc issue in the PR title. For the harder version, set up a GitHub check to automatically lint & reformat your code on a new commit.

Or, do something else fun. We’ll leave this open-ended.

Here are some resources to get you started:

How to submit to the GitHub Check challenge:

Tweet the link to your GitHub repo with a screenshot of the Check in action.
Include the hashtag #noServerNovember.

Nov 26: Special Edition: re:Invent serverless hackathon

How it works

The first three Mondays in November, we'll release a new set of Serverless Challenges. We’ll also include some resources to get you started. The final week of November, we'll have a special edition re:Invent hackathon instead.

Find a challenge you like! Or better yet, find multiple challenges you like! You can enter separately for every challenge you complete, and you can complete any challenge at any time.

Do the challenge. Put it in GitHub. Tweet a link to your repo, plus any other relevant links or screenshots, with the hashtag #NoServerNovember.

Each entry qualifies you to win a prize. We will draw three winners every week, and we don't remove you from the pool until you win a prize. So if you complete a challenge during week 1, you could be in the drawing for weeks 2 and 3 as well. All the more reason to start early!

Draw dates:

Nov. 12
Nov. 19
Nov. 26

Rules

To qualify, the entry must use the Serverless Framework and a serverless backend (such as AWS Lambda, Google Cloud Functions, or Microsoft Azure).

You may only enter one time per daily challenge. You can, however, complete as many daily challenges as you want, and those will count as separate entries.

You must follow any additional instructions contained within the challenge descriptions to have your entry counted. Only entries that use the hashtag #noServerNovember will be qualified to win.