Comments for Wrapping Up

From @jayair on Mon Apr 10 2017 01:10:53 GMT+0000 (UTC)

Link to chapter -

Copied from original issue:

From @badfun on Fri May 05 2017 17:36:30 GMT+0000 (UTC)

Hi guys,
I’ve followed your tutorial through to setting up the endpoints, skimmed ahead on the front-end stuff, and gone through the source code. I don’t see anything about Lambda in here at all. Am I missing something?

From @PatrykTies on Fri May 05 2017 17:39:48 GMT+0000 (UTC)

Whole back end api is based on lambdas, this tut using serverless framework to create lambdas. Just spend 1-2 hrs and finish back end part of this tutorial and you will see lambdas in action. This is best tut ever! Thanks guys for making it.

From @badfun on Fri May 05 2017 18:11:54 GMT+0000 (UTC)

Ah I see. Setting up Administrator Access means we don’t have to explicitly setup Lambda access. I didn’t deploy but now have so the functions have been created and can see them.
Yes great tutorial Thanks!

From @deepseafishing on Wed Aug 02 2017 18:34:14 GMT+0000 (UTC)

hey @jayair can u perhaps how i can make this service into mobile app like the picture you show it here? did u have to make the front end all again?

From @jayair on Wed Aug 02 2017 22:21:05 GMT+0000 (UTC)

@deepseafishing Oh we didn’t really make it into an app here. We just added the web app to our home screen. But since we set the icons properly earlier in the tutorial, it shows up pretty nicely on our home screen.

From @pjamieson on Tue Aug 22 2017 19:55:17 GMT+0000 (UTC)

Great tutorial. Thanks!

For anyone who might be interested, I’ve refactored the React client to use Redux, with a and the refactored code up at Comments and suggestions welcome.

From @jayair on Tue Aug 22 2017 22:09:12 GMT+0000 (UTC)

@pjamieson That looks pretty good! I’ll check it out in detail and share it with the rest of community.

From @pjamieson on Tue Aug 22 2017 23:38:52 GMT+0000 (UTC)

Thanks, Jay. The code (still a work-in-progress) is deployed at

On Aug 22, 2017, at 3:09 PM, Jay V wrote:

@pjamieson That looks pretty good! I’ll check it out in detail and share it with the rest of community.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread

From @triunm on Sun Oct 08 2017 14:14:48 GMT+0000 (UTC)

This is the best material to get started w/ serverless in aws. Thank you guys!

From @x11joe on Sat Nov 11 2017 21:40:26 GMT+0000 (UTC)

Amazing tutorial. The amount of detail that goes into this tutorial is simply amazing. Taking into account all the little things I wanted, like www redirects, cache, scripts to make deploying easy, serverless framework for the api, https, redirecting urls to where you need to go if your session timed out!! (you didn’t even have to cover this), but its amazing that you did! Simply the best tutorial I have ever read. In fact so much so, I would like permission to create a set of videos (giving you guys credit of course), to help explain it further given the particular troubles I went through. I have a tutorial video youtube thing I am doing. Let me know if this is okay :).

I became a patron for you guys to help you out also :). Let me know if you ever need help.

I wanted to note that a chapter on SEO is very critical since React renders with javascript the search engines can’t find the text on the page. Could you write a chapter on this topic (pretty please :slight_smile: ), since i think its equally as important as some of the other points that were given.

From @jayair on Mon Nov 13 2017 00:00:04 GMT+0000 (UTC)

@x11joe Thanks for the kind words and support. It means a lot!

I think adding more detail through a video would be very helpful. Especially if you can build on the tutorial and add your perspective. We would love to link to it in the tutorial. I know one of our other readers is also working on a video series. You can take a look at it if you need some ideas or inspiration -

From @rtorcato on Tue Nov 21 2017 19:42:06 GMT+0000 (UTC)

You guys should have a chapter on costs. This should compare the cost of running this type of infrastructure over running a lamp/lemp type server setup. I know they are not comparable because of scale, but for a small to medium sized site I think the serverless architecture ends up being more expensive.

From @jayair on Wed Nov 22 2017 18:54:29 GMT+0000 (UTC)

@rtorcato We do a quick calculation on the cost of running this tutorial app in this chapter here - For very large sites Serverless can be more expensive but for small to medium it is a lot cheaper. This has been true in our experience and here is some simple analysis on this -

From @Ajacs on Thu Nov 30 2017 03:36:04 GMT+0000 (UTC)

Guys I get this message when I try to login : UnexpectedParameter : Unexpected key ‘UserContextData’ found in params, any idea ?

This is the version of libraries:

"amazon-cognito-identity-js": "^1.27.0",
"aws-sdk": "^2.157.0"

From @jayair on Sat Dec 02 2017 18:42:53 GMT+0000 (UTC)

@Ajacs Which step of the tutorial is causing this issue for you?

From @SpencerGreene on Sat Dec 16 2017 06:53:10 GMT+0000 (UTC)

I will second and third the comments here - a great tutorial, well written and thorough.

If you were going to add anything else, I’d suggest a “forgot password” chapter, since that would show how to send the user an email. And a +1 on the SEO comment above!

From @iggiFW on Wed Apr 04 2018 21:39:43 GMT+0000 (UTC)

I didn’t run any tests during this tutorial, and by the end of it, the standard create-react-app tests are broken for me. Running “npm test” yields:

> notes-app-client@0.1.0 test /Users/Bazo/serverlessReact/notes-app-client
> react-scripts test --env=jsdom

2018-04-04 15:24 node[65744] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2018-04-04 15:24 node[65744] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2018-04-04 15:24 node[65744] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
      throw er; // Unhandled 'error' event

Error: Error watching file for changes: EMFILE
    at exports._errnoException (util.js:1036:11)
    at FSEvent.FSWatcher._handle.onchange (fs.js:1406:11)
npm ERR! Test failed.  See above for more details.

On the Jest and Facebook GH issues they suggest changing the npm command from

    "test": "react-scripts test --env=jsdom",


    "test": "jest",

which then yields a different error:

npm test                                                                                                         ⏎

> notes-app-client@0.1.0 test /Users/Bazo/Desktop/projekkz/serverlessReact/notes-app-client
> jest

 FAIL  src/App.test.js
  ● Test suite failed to run

    /Users/Bazo/Desktop/projekkz/serverlessReact/notes-app-client/src/App.test.js: Unexpected token (7:18)
         5 | it('renders without crashing', () => {
         6 |   const div = document.createElement('div');
      >  7 |   ReactDOM.render(<App />, div);
           |                   ^
         8 |   ReactDOM.unmountComponentAtNode(div);
         9 | });
        10 |

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.357s
Ran all test suites.
npm ERR! Test failed.  See above for more details.

It seems to be a problem with babel maybe? It has a problem with the JSX caret symbol. When I run a brand new create-react-app and run ‘npm test’, tests work fine. I’m using latest npm. I’ve tried deleting node_modules, package.json.lock and reinstalling them, but the problem is still there. Anyone else having this issue? (Great tutorial by the way, I think adding one test at the end to show that tests work would make it stronger).

From @jayair on Wed Apr 04 2018 22:29:07 GMT+0000 (UTC)

@iggiFW I’m seeing a different error on my end but yeah tests are something we’ll add at some point. I’m not entirely sure why you are seeing a JSX related error.

From @miloofcroton on Fri Apr 06 2018 10:48:21 GMT+0000 (UTC)

Hey, just wanted you guys to know that the link is no longer pointing to any section on the homepage. No mas tools section.