On EC2 Dashboard, find your new instance and scroll the view to the right to see what Security Group your instance is in. It will take a few minutes.Īs your instance is being launched, you need to configure AWS security groups so that you and your website visitors will be able to access your app (and you will be able to connect to it via SSH). Click Launch InstancesĬlick View Instances and go make yourself a cup of coffee while AWS is launching your new instance. You will be asked to select an existing key pair or create a new key pair - it doesn't matter, we will be using a web based SSH client from AWS console to select any option. On the next screen confirm again by clicking Launch Click Review and launch as we are blasting through the complexity here and will take all the default setting and only change the few we need later. Assuming you are running a simple app then go for the cheapest instance: t3a.nano. Select the first one from the list: Amazon Linux 2 AMI for the 64-bit (x86) - basically the first default option That's it, we are ready to roll! Launch an EC2 instance Node js app in a git repo - make sure your Node app is ready and available to clone from a git repoĪWS account - if you don't have one yet, you can sign up here > Processing Dependency: libm.so.6(GLIBC_2.27)(64bit) for package: 2:nodejs-18.3.0-1nodesource.x86_64Įrror: Package: 2:nodejs-18.3.0-1nodesource.x86_64 (nodesource)Įrror: Package: 2:nodejs-18.3.0-1nodesource.You need a few things before we start the launch: > Package nodejs.x86_64 2:18.3.0-1nodesource will be installed Loaded plugins: extras_suggestions, langpacks, priorities, update-motd But after several tries I can't able to install node and got the error shared below. I purchased Amazon Linux 2 machine using AWS LightSail and tried to install node on that machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |