TLDR I joined Amazon Web Services on the 11th of October – i.e. AWS – and it rocks.
When you join Amazon you are signing up to learn a lot of things about the company and the ways in which the company gets things done. Before I get into all that, I’m going to tell you a bit about my career and what led me to Amazon. After all, it is surreal and unexpected for many that know me that I’m here. This relationship has definitely been a 2-way story, and one where it finally fit in a mutually beneficial way.
I finally wrapped up my name server and DNS mapping needs with Name.com, Route 53 and Elastic Beanstalk. Since this was a little confusing I thought a short write up was in order. Thanks to Evan @evandbrown for helping out!
The first thing needed is a delegation set of name servers for your DNS and name server provider. These can be found by creating a hosted zone. The way to do this is open up the AWS Management Console and navigate into the Route 53 management area. The Route 53 icon is under the Compute & Networking section on the management console.
Upon navigating to the Route 53 console area click on the Create Hosted Zones button.
When the zone is created then the delegation set can be found under the Hosted Zone Details. This delegation set now needs setup as the name servers for whoever, in this case name.com, is the domain provider.
Open up the management console for the name server administration.
Upon adding them the list should look something like this.
Once the name servers are setup, those will need time to propagate. Likely this could take a good solid chunk of time, somewhere in the hours range likely, and don’t be surprised if it takes a little bit more than a day.
While the propagation starts navigate back to the AWS Management Console and open up the EC2 section of the console. On the right hand side of the Resources list there is a Load Balancers section. Click it.
In this section there is a listing of all load balancers that have been created manually or by Elastic Beanstalk.
Make note of the Load Balancer Name for selection in Route 53. This is what Route 53 needs in order to point an alias at for incoming traffic to that particular Elastic Beanstalk application. In this particular image above there are 4 load balancers listed, the easiest way to prevent confusion is to take note of the load balancer name at the time of creation, but this is the easiest way to find them otherwise.
Now when going back to the hosted zone to set it up with the appropriate information, create a new record with the appropriate name, in this case I was setting up the admin.deconstructed.io (no it isn’t live yet, I just set it up to test it out) to point to an alias target. Just leave the Type set to A – IPv4 address and click the radio control so that Alias is set to Yes. In the alias target select the appropriate load balancer for the Elastic Beanstalk (or whatever it points to) application.
That’s it, give it a few hours (or a day) and eventually the domain or subdomain will be pointed appropriately at the Elastic Beanstalk load balanced application.
I’m kind of surprised, I didn’t even realize that IBM has made some inroads into cloud computing. I however shouldn’t have been at all surprised, as IBM has made great changes over the years. Their offering doesn’t seem as well laid out as AWS or Azure but it is a significant presence just being IBM.
IBM Cloud Computing looks like most of the other things the company does these days, which is primarily services based. I don’t mean web services either, even though I’m sure they use those, but literally services based versus offering actual products, hardware, or some type of applications. They do have their iNotes and other tools like that in the cloud. Otherwise it isn’t immediately obvious how their cloud compares to Azure, AWS, vmware or Force.com. IBM’s website for cloud computing seems as disorganized as vmware’s or Force.com’s, which make Azure and AWS seem super well put together and structured. With clearly defined features and tools for developing in their respective clouds.
Overall the services look attractive if IBM is already a provider of other services. Kind of like Azure looks more attractive to the .NET Stack of Developers and AWS looks more attractive to PHP or Java Developers. Even though both Azure and AWS support .NET, Java, PHP, and more, just from the IaaS or PaaS perspective though.
This begs the questions:
What are the differences between the IBM Cloud Computing Services, Azure, AWS, Force.com, vmware, and others?
Besides IBM, Azure, AWS, Force.com, and vmware, what other cloud services are really doing it right and pushing forward with redundancy, uptime, compute capabilities, and other key features?
Anyone guessing on consolidations in the future with the current big players (AWS, Azure, Force.com)?