0:00 Okay, so to actually start building out our 0:02 backend on AWS, 0:04 we're gonna take advantage of another service called Elastic 0:08 Beanstalk. So we can look for Elastic Beanstalk to 0:12 run and 0:12 manage our web apps. And so this is where we're gonna actually host our 0:16 Node.js application. 0:18 So we can see here that Beanstalk automatically handles 0:21 deployment, 0:22 capacity provisioning, load balancing, and automatic scaling 0:26 on our web application, as well as introducing health monitoring, 0:30 patches, and security updates. So it's essentially a fully managed 0:33 platform to run a Node.js application. 0:36 So let's go ahead and click on the Create Application button 0:39 to go ahead and create 0:40 ours. So for the environment here, we're going to stay on the default web 0:44 server environment, and then we're gonna go ahead 0:46 and give it a name. 0:48 So I'll call mine Chatter Backend. 0:52 And then we have the option to provision an environment name. 0:56 So an environment name in Beanstalk is essentially a 1:00 copy of the application, but with different environment settings 1:04 applied to it. So for example, we could have a separate environment for 1:08 local, staging, and production environments and make 1:11 separate changes to each of those environments and have an independent URL. 1:16 In our case, we're just gonna go ahead and create one prod environment, 1:20 so I'll call it Prod. 1:23 So next up, we have the ability to provision a custom 1:25 domain 1:27 using the AWS default domain here. 1:30 I'm gonna leave it blank just for an auto-generated value. 1:34 Later on, I'm gonna show you how we can actually 1:36 provision a custom 1:37 domain for this backend and get rid of this AWS 1:41 specific domain. So for now, let's just leave it auto-generated. 1:45 Next up, we have the actual platform, which is the actual underlying 1:49 image or software that's going to run our application.
The rest of the transcript is for members.
Sign in 