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?
Labels:

Comments

Post a Comment

Popular posts from this blog

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
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more