Malone Xchange Favicon

Cloud Blog

Introduction

Title description, Mar 7, 2019
Image

The point of this blog is to help beginner's get started with AWS and Ec2. This is the first entry of many to come. In this series I will document my succeses and failures with AWS.

I am having trouble setting up my Ec2 account/platform/instance. I did not read all the documentation. I am preoccupied and spreading myself thin with other projects. I could email Amazon for help and tell them," Hello! I am inexperienced and do not know how to setup my system. Right now I am at a loss on how to proceed. Here is my account information. I am trying to setup a personal website for learning purposes. What do I need to do at this point to make that happen?" . I really should do that but need to make progress elsewhere due to time constraints. I am new to cloud services so it is going to take me awhile to figure it out.

Reasons I should drop everything and focus on learning AWS

I signed up for the Ec2 containerization package. Amazon offers 12 months free account. I figured it was a good way to learn something new and add to my skills. I bought a domain through Route 53 for $12. Since I own this domain I want to use it to view my site and help with site building. A live site is easier to run and manage than a dead one.

Aws is not easy for beginners and this puts a lot of people off. Aws is challenging and and the hardest way to start out. This is my first site, blog, anything so I took the hard way. Haing knoweledge about cloud, cloud computing, Azure, AWS, Google compute engine, and related fields is impressive to others. It makes you look good and stand out as being more knowledgeable.

Just because something is less approachable does not mean we should back down and accept defeat. Maturity requires learning new things and finding ways to teach ourselves things and seem daunting. The more we do what others don't the more we show and demonstrate leadership.

Reasons to put Aws on ice

I just ordered Donald Knuth's, "Art of Programming" and Evi Nemeth's (and others), "UNIX and Linux System Administration Handbook (5th Edition)". I have never used linux or managed networks before. Brushing up on some basic adminstration terminology and processes would help. I signed up for AWS to force myself to start learning services that frankly I should have been exploring several years ago. Signing up gets the ball rolling. I have been ignoring AWS service since 2011 so a few weeks won't hurt. I am still building my site and organizing content. Having to learn multiple things at once is not very efficient.

I think reading the linux adminstration book will help me further my pursuit of learning AWS. One of the authors, Ben Whaley, seems to be quite an expert on AWS. I am going to read skim his book first.

It was difficult skimming through Amazon's documentation but mostly I was preoccupied and lazy. I did not devote time to it. I could have watched there intro videos, got lost, called support, had them guide me on track, or if they couldn't at least know that AWS was not a solution for me at this time. Luckily through a web search of "o'reilly aws" I found this, "https://www.oreilly.com/library/view/aws-system-administration/9781449342562/ch01.html" and it seemed to help me understand where I was and what needed to happen next.

Current Status with AWS

I started an AWS account not really having researched the proposition or knowing how to use it. Amazon has tons of documentation but is aimed at experts and businesses not casual users. The term overkill might apply here for a first website. My account with AWS was started last weekend. First thing I did was buy a domain name from Route 53. The thinking was they would be my web host. Then I was able to log in and launce an Ec2 instance using linux 2. I setup security and assigned an elastic IP. I even setup a volume. This is where I am.

After some reading it seems I need to download and install CLI and assign an AMI to my instance. Previously I had seen and hears these terms before but it was not clear what either of these were. CLI sounds like a command line prompt but I was confused over how it worked. For example I am running a linux instance. Do I use cli on a web browser through my AWS account? Do I download a program and run that? If I download a program, which pversion for my computer and my instance? What version to use to that a windows can talk to a linux instance? If a CLI is a simple terminal program can I not use other utilities? Can I use powershell? Can I use IIS? How does putty play into all of this? So I was pretty lost. O'reilly lead to Amazon documents which lead to: I need to download the windows version of CLI, install it, use it to connect to my instance from my computer.

The reason I was so lost was inexperience and lack of untuitiveness on Amazon's part. They have tons of documentation but a single good book on AWS adminstration touts all that. A logical step for me to prove I am serious about learning, understanding, and using AWS would be to buy a book focused on AWS administration. I am thinking something from the O'reilly series.

Readers may ask, "Why does he want to learn AWS?" in an attempt to evaluate whether it is a productive use of time or even the correct solution to my needs. They are asking what my needs are and if I am approaching the problem correctly. I get that but it seems when people with a little bit of knowledge use logic like that to it leads to them telling beginners basically not to learn new skills and let others manage their data for them. That type of approach makes learning new comupter skills difficult because there is a sense of wanting to limit individuals from becoming more skillful. I want to learn AWS because I want to learn how to run a website on it. Why specifically AWS? Because it is weird and esoteric but I feel it might get me more control over my website. Scaleabilty seems to be a big selling point for them. A lot of big sites such as Netflix and Quora use AWS as their webhost so that is reassuring that is used by major companies. Whwn learning any new technology you have to ask yourself if it will be empraced by companies. In the case of AWS the answer is a resounding yes. Having the technical skills and understanding to be able to relate what is happening and how things are structured only adds to your acumen. SSo I want to know what other companies know so I can better understand them and modern business in general. It is helpful to understnd how business operates and a lot of businesses turn to AWS and AWS's competitors.

I may not have the most sound plan or strategy but over evaluation leads to indecision. There are thinkers and doers. I pulled the switch by signing up so i must make the most of it. I am going to buy the O'reilley book, "AWS System Administration by Federico Lucifredi, Mike Ryan". It explains everthing I need to know to be an AWS Systems Admin.

There is a seminar hosted by the AWS community March 27, 2019 in Santa Clara, CA. I want to go to it for networking and learning purposes. I believe you can follow upcoming events here at Amazon's event's page.

Update

2:30 AM 3/28/2019
Image

I had planned on attending AWS seminar but got delayed. They have another one April, 8th but I will not likely attend that one either. I wanted to use cloud computing to setup software development but have not learned the basics of simple storage yet. I have not learned The use of linux command line and have been learning Microsoft cmd.exe instead. The goal is not to choose one over the other but compare both. I am learning both at the same time.I should start buying more books and make them availible to others somehow or I should read them thoroughly and paraphrase key topics. A new version of the linux command book came out last week supposedly. I would think that is a good read to use with Linux on AWS.

About Me

Popular Post