Tag Archives: howto

HowTo: migrate your DNS hosting to Route 53

Today we have migrated the DNS hosting of the domain http://nimbusarchitect.us to Amazon AWS Route 53. It’s easy, let’s have a look at the process.

For several services of AWS, you have to choose a region . You don’t for Route 53, so it’s a global service.

Screen Shot 2016-01-04 at 16.49.54

AWS allows you to transfer a domain to Route 53. This is the easy way: you don’t have to recreate your records if you use this wizard.

But if you like you can keep your current registrar. We wanted to keep using Transip because they are cheaper as a registrar and it’s practical to have one place to administer all domain names.

Use the following method in case you want to keep using your current registrar:
1. create your zone at Route 53
2. create your records / or import a zone file
3. change your name servers at your registrar (in this example Transip.nl)

DNS zone before the change:

Screen Shot 2016-01-04 at 16.43.37

DNS zone after the change to Route 53:

Screen Shot 2016-01-04 at 16.43.21

Projected costs: $0.50 a month…

SSH login on EC2 Linux without .pem file?

By default one has to use a .pem file to SSH into a Amazon linux instance. This is a pretty good idea, and safer than a password. But sometimes it’s more practical to use a username and password.  You still can, this is how:


Add your downloaded .pem file to you ssh store on Linux and Unix systems like OS X:

ssh-add /path/to/pemfile.pem

Login without .pem file? Follow these steps:

  1. login using your .pem file (ssh -l pemfilename.pem ubuntu@publicip (or instancename.availabilityzone.compute.amazonaws.com)
  2. Create a new user to be used to login with a password (sudo useradd -s /bin/bash -m -d /home/adminbert -g root adminbert)
  3. Set a strong password (sudo passwd adminbert)
  4. configure SSH by editing the config file. Change this PasswordAuthentication from no to yes (sudo nano /etc/ssh/sshd_config)
  5. Restart SSH (sudo service ssh restart)

You can now login using a username and password.

(ssh username@publicipaddress / or username@instancename.availabilityzone.compute.amazonaws.com))