Skip to main content

Severless Application with Node.js, & AWS CodeStar and Cloud9




Instructions: Here
Technologies;
  1. Node.js
  2. AWS CodeStar
  3. AWS Cloud9


Node.js is running Javascript on Chrome's V8 engine that is event-driven. I used it quite a bit in the past year without actually understanding what it truly does - Run Javascript without a browser. Including applications that use JS.

According to the instructions above, Cloud9 is an IDE (Integraded Development Enviroment) where you write, run, and debug code of popular programming languages.

CodeStar builds and deploys the applications:

"Create service role?" "Why yes, I believe I will."
The above image is from the instructions linked above.

On the project template page, I pick Node.js:



Then I name it 'nodejs-serverless-project' 'serverless-brooklyn'


It's not as if the name prevents the tutorial from working, right?

And I select AWS CodeCommit.

CodeStar will set up a complete integration pipeline (While monitoring with CloudWatch), Commit helps with version control, CodeBuild will build and test, CloudFormation will deploy to Lambda.

Here is the project dashboard for serverless-brooklyn;



AWS made a commit to the master branch;




Here comes the fun part!



And this, this, is the ... coding area;


Reminds me heavily of Visual Studio.

Let's move into the correct directory. Fun fact - the instructions on the page actually changed to incorperate my project name.


Changing some things in the HTML up here.



Let's see if anything has changed; Changes are marked in red, the file named.



If you know about git, you know what we do next - Push it, comment it. As I didn't initialize this with my GitHub account, I don't and simply close the resource. We're here to learn, not to get charged.


EMPLOYERS: More things with Node.js - Who wants to be limited to a browser all the time to run Javascript?

Comments

Popular posts from this blog

What Do You Need? [AKA; List of Offered Services / My Next Role] (2020)

UPDATED 2021 I am a trusted outsourced remote consultant for your company.   I enjoy having the flexibility to take on temporary projects from time to time! I start at part-time, temp work for now. If we like each other, we can renegotiate. If anything sounds weird, out there, or unusual - Feel free to e-mail me .  3 Services Offered Technical: Cloud Technician     Azure [ See tag ] WORKING ON: Infrastructure As Code (Specifically Terraform/Azure and CloudFormation/AWS)  Support [Web: Example Job Description ] [Text : Example Description ]     I help you with adjustments in HTML, CSS, and Javascript.     When you email a business a question and they answer? That's me.   IT Operations Tech [ Example Job Description ]     Hardware and SaaS support.     Cisco routing and switching (Networking). CCNA, A+, Sec+, Azure certified WORKING ON: Junos Networking  Writing :      You want to pay me to write more of *waves hand* this blog? I am game .     I write B2C e-mails going out to o

Contactless Tech’s Role in the New Guest Experience ft. Intelity and The George

 Contactless hospitality technology is growing. You want to get away, and you'll be damned if a little thing like a deadly virus will stop you! But you still don't want to touch things. Ew. During the chat between INTELITY CEO Robert Stevenson and THE GEORGE Director of Operations Kerrie Hunter, you’ll learn how the historic boutique hotel has adapted a mobile-first guest experience in the wake of COVID-19—and how they see contactless technology affecting the future of hospitality. I don't remember how I found INTELITY (probably hoping to score a position with them), but I liked them enough to stay on the e-mail lists.  

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H