Git squash Notes

git rebase -i HEAD~3
git log --pretty=oneline -n 10

Change numbers to find where exactly we need to do HEAD~n
git rebase --abort
git push -f origin branch-name
gitk
gitx

vi commands
/pick
cw - change word
squash
n
.

https://robots.thoughtbot.com/git-interactive-rebase-squash-amend-rewriting-history

Secure Headers Images

How to run bundler-audit to check for security vulnerabilities in Rails

bundle-audit check

Strip trailing whitespace on Save with …callbacks! in Textmate

Open the bundle editor (⌃⌥⌘B) and open “Text” → “Menu Actions” → “Converting / Stripping” → “Remove Trailing Spaces in Document / Selection”.

Then in the drawer put callback.document.export in Semantic Class and Document / Replace Document as Input / Output.

Hooray! From now on each time you’ll save a document all trailing space will be stripped!

Fixing Haml Spacing problem with Textmate

Software Quality Attributes Rating Tool

www.gettingagile.com/wp-content/uploads/2009/05/softwarequalityattributes-ratingtool.xls

Notes from Software Debt Book

Leave the campground cleaner than you found it.

Always leave the code in better shape than when you started.

The following questions should help you decide whether to start refactoring when you see an opportunity for it:

1. Does this change directly affect the feature I am working on?
2. Would the change add clarity for the feature implementation?
3. Will the change provide automated tests where there currently are none?
4. Does the refactoring look like a large endeavor involving significant portions of the application components?

Refactor if the answer to the first three questions is an yes. If the answer to the fourth question is yes. Then I use experience as a guide to help me produce a relative size estimate of the effort involved in this refactoring compared to the initial estimate of size for the feature implementation. If the size of the refactoring is significantly larger than the original estimate given to the Product Owner, I will bring the refac- toring up to the team for discussion. Bringing up a large refactoring to the rest of the team will result in one of the following general outcomes:

The team thinks it is good idea to start the large refactoring because its estimated size does not adversely affect delivery of what the team committed to during this iteration.
The team decides that the refactoring is large enough that it should be brought up to the Product Owner. The Product Owner could add it to the Product Backlog or decide to drop scope for the current iteration to accommodate the refactoring.
Another team member has information that will make this refactor- ing smaller or not necessary. Sometimes other team members have worked in this area of code or on a similar situation in the past and have knowledge of other ways to implement the changes needed.


Simplicity — the art of maximizing the amount of work not done—is essential.

Design Review

Design review sessions are periodic meetings where team members are able to share and get feedback on design decisions. Effective design reviews involve the development team members. The design review provides a forum for the team to converge on common design decisions and ultimately clarity in the application’s structure. The typical design review session involves all development team members. The agenda for the meeting is sent out to the team beforehand and includes the one or more design decisions that will be discussed. At the meeting, each design decision is presented while the rest of the team asks questions and dis- cusses the merits and challenges they see. Through this discussion the devel- opment team captures action items to take into the software construction process.

How to get Google voice chat to work on mac os

sudo killall coreaudiod

Gitbook Notes

https://github.com/GitbookIO/gitbook/blob/master/docs/setup.md
https://toolchain.gitbook.com/syntax/markdown.html#images

Full Stack Developer Course Notes

Development Environment Setup

1. Install browser-sync https://browsersync.io/

npm install -g browser-sync

2. browser-sync --version

3. Start the browser-sync to watch all the files for changes.

browser-sync start --server --directory --files "*"

UI User Story Example

Miya is part of the awesome group called The Foundation. She is a developer by trade and she wants to send cold email to do market research in her area of interest, IP law. She tries quickemail.io and finds it's interface very confusing. She is new to cold email marketing. She signsup for toutapp and finds that it is very bloated. She posts on TF forum to get some recommendation for cold email marketing automation tools. They recommend vocus which is also not beginner friendly. She has questions like: Will this allow me to upload a CSV file and schedule the emails to send out based on template. Vocus website does not provide any answers to these questions.

Miya found the quickmail.io interface very confusing to use. Instead of days, you had to convert the days to hours for the followup sequence. It had variation and A/B testing as part of the setup which was not required for her initial set of emails to be sent. It was difficult to find the merge fields and had to contact support several times over the period of 5 days. She did not know whether it was a bug due to the browser she was using or which icon would display the merge fields. She had a specific task to complete but found it extremely difficult to use the product. The training video she found on youtube channel of quickmail.io was irrelevant and she wasted few hours of her time watching the unrelated video to her task. She was very frustrated.

As a developer she started to do research on open tracking and threading features found in other products. She figured out threading is not really required. She found out that only the first email open must be tracked and ignore the email open when they are replying to her email. Scheduling the emails to trigger would require a fair amount of work. She found some good resources on how to authenticate to use the Gmail API for sending emails.

Goal: Cold email and followup for contacting prospects

Business Model Canvas for SaaS Business

Key Partners
What can you outsource to whom?

Web Hosting Providers
IaaS Providers
Open Source Projects

Key Activities
What will you need to master?

Customer interviews
Product Development (Product design, Software Development)
Deployment and Maintenance

Key Resources
What do you ned to build up?

Code base
Developers

Value Propositions
What is your unique value proposition?

Business Productivity and Collaboration

Customer Relationships

Customer Conference
Associations
Events
Acquire and Lockin

Channels
How to communicate and deliver?

Self service
Web
Phone
Email

Customer Segments
Who are your customers?

IP Attorneys

Cost Structure
What are my costs?

Product development
Partner costs (IaaS)
Marketing and Sales
Hosting Fees
Customer Acquisition Costs
Salaries

Revenue Streams
How will you make money?

Usage based, by user or by transaction

The Four Pillars of Wealth

Clay Collins and Perry Marshal recommend:

1. Automated Sale
2. Recurring Revenue
3. Sell a reproducible product or a tool (break time for money dependency and scale)
4. No accounts receivable (Get paid in advance)

1. Find pains
2. Presell
3. Outsource product development

1. Find the problem
2. Sell the solution
3. Hire a developer

1. Idea discovery
2. Sketch the solution (create a paper prototype to solve the problem)
3. Presell the sketch
4. Outsource product development
5. Launch the product

Find booming industries and sell them software tools.

References

Notes from Dane Maxwell's video transcript 
Read The Automatic Customer by John Warrillow

Cold Email Guide

How to achieve reply rates of 40, 50 or 70%.

- Prepare a well targeted prospect list. Don't sell sweets to a diabetics list.
- Number one goal is to get a response (either positive or negative).
- Follow ups lead to 55% of responses.
- Follow up can be a one liner. Just wanted to make sure my email below didn't fall through the cracks.
- Be prepared for rejection.
- Aim for certain ratio and improve it (ex 1 positive reply for each negative reply)
- Contact at least 100 prospects before making any decision
- Make it short, layout a clear offering that compel them into replying
- Just reply 'yes' and I'll send you more information
- Use the name of the person in the email
- Get small commitments before going for big commitments
- You can pre-warm a relationship by using referrals like: Bugs Bunny mentioned I should get in touch with you
- Tuesday to Thursday is the best days to send

Problem Discovery Questions for Conference

I am attending a 3 day conference in my target market. I had to come up with questions based on the amount of time available. The goal is to learn about their problems.

One Question

1. What tasks take up the most time in your day?

Three Questions

2. What's the hardest part of your day?
3. What product do you wish you had that does not exist yet?

Seven Questions

4. What are some unmet needs you have?
5. What could be done to improve your experience with [process/role]?
6. What’s the hardest part about being a [demographic]?
7. What are your most important professional goals?

Google Trend for UX Design

Dealing with Vague Requirements in Software Development

1. Very vague and unknown requirements should be moved out of scope. Use scope control as a way to filter out.
2. Build a quick and dirty throwaway prototype to find answers to the vague / unknown requirements.
3. Identify the vague requirements and ask the product owner the right questions to fill in the blanks.
4. Conduct a requirements grooming session to flesh out the vague requirements.
5. Ask the stake holders to prioritize the backlog and work on the well defined requirements.

Downward Trend of Rails

Top Links for Second Week of Aug 2017

https://robots.thoughtbot.com/a-crash-course-in-analyzing-memory-usage-in-ruby
https://blog.codeship.com/advanced-enumeration-with-ruby/
https://thisbitofcode.com/managing-localization-rails/
https://blog.showoff.ie/using-gemstash-for-private-gem-hosting-8b6170da766c
http://semaphoreci.com/blog/2017/08/03/tips-on-treating-flakiness-in-your-test-suite.html
https://semaphoreci.com/blog/2017/08/09/faster-rails-eliminating-n-plus-one-queries.html
https://www.nopio.com/blog/ruby-state-machine-aasm-tutorial/
http://www.pablocantero.com/blog/2017/08/06/using-ruby-and-amazon-sqs-fifo-queues
https://depfu.io/blog/2017/08/02/bundler-and-private-dependencies

css link

Shay Howe's Book

Find all articles that is not tagged in Rails

ids = Tagging.where(taggable_type: "Article").collect(&:taggable_id).uniq

Article.where.not(id: ids).collect(&:id)

API Documentation with Tabs for Languages

Slate generates html from a markdown document and provides syntax highlighting for different languages that displays in separate tabs.

For internal use, API blueprint is a good option. For external use, slate is a great option to publish documentation. It generates good looking and developer friendly docs. We can copy the slate generated static files to a static site deployed on Google cloud. This is the easiest deployment. It avoids extra work that is required with AWS such as uploading to S3, configuring a bucket as a webserver etc.

Questions

1. Is slate markdown compatible with API blueprint markdown file (.apib) ?
2. Is there a tool that will convert .apib file to slate markdown file?

I started with the schema.rb file from a Rails project that I am currently working on.


References

- Using API Blueprint With MSON
- HTTP Documentation with API Blueprint

Vue.js 2 The Complete Guide Course

Things to focus when watching the video:

1. Using tabs and highlighting selected tab.
2. Defining routes for each tab.
3. Real development workflow with Webpack and Vue CLI
4. Deploying the app to AWS S3

Top Ruby Links for Aug 4, 2017

1. with __dir__ we can restore order in the Universe

2. Lint your Ruby code with Overcommit and static analysis tools

3. Asynchronous Elasticsearch bulk reindexing with Rails, Searchkick and Sidekiq

Learn by doing Vue.js 2 the Right Way

1. Replacing hard-coded URLs with configuration file values for different environments.
    Use webpack-merge and interceptors to configure URL in config folder dev.env.js and prod.env.js
2. API documentation for using JWT for authentication.
3. Using scoped style
4. Using aletifyjs to display form error messages
5. What is the vue-resource interceptor equivalent in axios?
6. vue-auth - Jwt auth library for Vue.js
7. Use vue.js router global guards to protect URLs that require login.

Rails Interview Questions

Ruby

1. What is the difference between a lambda, a block and a proc?
2. What are #method_missing and #send? Why are they useful?
3. Getter and setter methods
4. method overloading (Ruby does not have this feature)
5. Include vs Extend
6. Symbol vs String
7. What does yield do?
8. Difference between && and AND operators
9. Multiple inheritance
10. public, private, protected
11. How can you call the base class method from a subclass? (super)



Rails

1. How do you sort an Array of objects by a particular attribute? What is a better way to do sorting with ActiveRecord?
2. Explain CSRF and how Rails combats it.
3. Explain mass-assignment vulnerability.
4. Explain various forms of caching available in Rails.
5. How is something like 30.seconds.ago implemented?
6. HashWithIndifferentAccess
7. N+1 Query problem
8. has_one, belongs_to, has_many, has_many_through, polymorphic
9. database transactions
10. load, auto_load, require_relative
11. load vs require
12. How can you call the base class method from inside of its overridden method?
13. sql injection (sanitize user input)
14. Include vs Prepend
15. How to implement single table inheritance?
16. Eager loading (includes the association)
17. render vs redirect

Elasticbeanstalk Transcript

Let's update brew. We need to install aws-elasticbeanstalk. Let's create a new Rails 5.1 API only backend app. We don't need spring or action cable. We will use Postgresql as the database. The health controller renders status ok json. Let's start the server. We can hit the health endpoint using curl. The browser displays the JSON. We need to run eb init from the root folder of the Rails project. I will use the region 1, us-east-1. We can provide an application name. We are using Ruby. Let's use the option 1 for the platform version. We don't need CodeCommit. We can host a private repo for free on bitbucket. We need SSH access to our instance. We can provide a key pair name. It is better not to use generic name so that we know which keypair is used on which server. We need to provide a new passphrase. This generates the key pair. We see that the eb tool created some entries in the gitignore file. We can now create a production environment for our Rails app. This creates a zip file of our app and uploads the zip file to S3. It provides the details about the environment such as the application name, region, deployed version, environment id, platform, tier and so on. The environment is starting now. It automatically created a load balancer and security group for us.

We can check the status by using the eb status command. It is launching. Let's update the awcebcli tool. We get a permission denied error. We can use sudo to run the upgrade command. The environment is still in launching state. While we wait, let's see if we can set the secret key base environment variable. We cannot set any environment variable while the instance is still in launching state. We have to wait for some time. Now the instance is ready but is in red state. Let's set the secret key base environment variable. It is now updating the environment. After some time, it is in ready state but the health is yellow.

We can deploy our Rails app by using the eb deploy. Let's hit this URL in the browser. We get a 502 bad gateway error. The health check URL also gives the same error. Let's go to the AWS console. The health is in yellow state. We see the recent events and it's details. If we go to the causes screen, we see the warning. We can go to the logs tab and request the full logs. It will take some time to generate the log files. It will then appear as the download link. I looked at the eb-activity-log and found the PG connection bad error. The Rails app was not able to connect to Postgres database.

We need to add the configuration for the production database in the database.yml file. We can also run eb logs command to retrieve logs. It seems to hang and there is no feedback. So I downloaded the log file from the AWS console using the browser. We can create RDS instance using the AWS CLI command. This generates a small database instance with 1 GB storage for Postgres database. You need to provide the master user name and the master password.

We can get help for eb command by running eb. The eb open still gives the same error. I created a .ebextensions directory in the root folder of the Rails project and created a packages.config with the these contents. This will install the postgresql93-devel package on our EC2 instance. We need to add this file to the git and commit it. We can now deploy the changes. We did not change the code but provided a package that needs to be installed for the postgres database connection problem. It is in updating status. It is now in updating green status. We can see that it is still updating. It is now complete. We can now see the response of the health endpoint in the browser. We don't have anything to display in the home page.

AWS CLI Route 53 Transcript

We can install awscli command line tool using pip. We get a permission denied error. Let's use sudo to install it. We can see it is installed. We have to configure the awscli tool before we can use it. You need to provide your AWS access key id and AWS secret access key. Now we can use awscli to configure our domains. The aws command takes the aws service as the first argument, then the command we want to run.

In this case, we want to create a hosted zone for www.clickplan.net. We need to provide a unique caller reference that includes timestamp to recognize this particular command. The output JSON shows the name servers that is assigned to our domain. You can see the caller reference that we provided as the command line argument. We had to create the hosted zone for this domain. Because, clickplan.net domain was registered at namecheap. If you had registered the domain at Amazon, they will automatically create the hosted zone records. We need to copy the hosted zone id under the id: hosted zone entry. We can now list all the resource record sets for this particular hosted zone id. The output shows four resource records for name servers, the domain name and the time to live value. We also see one SOA entry record for this particular domain.

We can also list all the hosted zones in our account by using this command. You can see that there are two domains, clickplan.biz and clickplan.net. We see the caller reference we provided here.

You can login to the AWS console to see the results of running the command. You can see there are two domains, same as the command line output we just saw. We can see the details of the hosted zones such as name servers also here.

Deploying the Rails app to elastic beanstalk is covered in another episode. Let's use AWS CLI to point www.clickplan.net to the Elastic beanstalk URL. Therefore, instead of hitting the URL production.xyz.region.elasticbeanstalk.com in the browser to access the Rails 5.1 backend app, we can use www.clickplan.net.

The documentation is confusing because things are spread across different guides such as Route53, Beanstalks etc. It is also confusing due to two different hosted zone ids. The hosted zone id for www.clickplan.net is different from hosted zone id for the AliasTarget. The AliasTarget hosted zone id value is the same as the region where you deployed your domain. In my case us-east-1 is the region where I deployed clickplan.net using Beanstalk.

We create a JSON file that provides the values for the action, domain name, the type of record, and the hosted zone id of the region where beanstalk instance is deployed. We also need to provide the beanstalk instance URL in the dns name.

Let's create A record for the clickplan.net backend Rails API only app. We can run this command and provide the path to the JSON file. The status is pending. You can check the status by running this command. We provide the change id we got from the output of the previous command. The output shows that the status is INSYNC, which means Route53 has completed it's job. It will take some time to propagate the changes. Wait for a few hours for the DNS resolvers and servers to pick up this change.

You can use the dig command to check if the changes has propagated to all the DNS servers. You can see the question section for clickplan.net A record. The answer section shows two entries in the A record. Each entry has an IP address, these IP addresses might change because they correspond to the IP address of the elastic beanstalk instance.

We can run the eb open command to open the URL. Now we can use our domain name to access the health check endpoint. Let's make the home page display the health check. We need to add the change to git and deploy the latest code. The upload is complete. Let's check the status. It is in pending state. We need to wait from some time. The status is now ready and green. Let's go to the root url. It does not display the health status. If we open the console, we see everything seems to be ok. Let's run the app locally. It works locally. Reloading the browser does not solve the problem. We see that the old URL still works. Let's use curl to avoid any browser caching issues. It is not a browser caching issue.

I forgot to checkin the changes to the routes.rb. We can now deploy the changes. We can check the status. It is updating. We need to wait for a few minutes. The status is now ready and green. We can now see the health check JSON in the home page. It works!

Elasticbeanstalk

Deploying Rails App to Elastic Beanstalk using AWS CLI

$ brew update
$ brew install aws-elasticbeanstalk

$ **rvm or rbenv optional setup here**
$ gem install rails
$ rails new pine
$ cd pine
$ git init && git add -A && git commit -m "Rails 5.1 Skeleton"

$ rails g health index

Define route and return { status: 'ok' } JSON in index action.

$ git add .
$ git commit -am "Added health controller"
$ git push

$ eb init
Select a default region
1) us-east-1 : US East (N. Virginia)
Select an application to use
1)[ Create new Application ]
Enter Application Name
(default is "rails5app"):
Application rails5app has been created.
It appears you are using Ruby. Is this correct?
(y/n): y
Select a platform version.
1) Ruby 2.3 (Puma)
Do you want to set up SSH for your instances?
(y/n): y
Select a keypair.
1) [ Create new KeyPair ]
(default is 1): 1

$ git commit -am "Post EB init"
$ eb create production

Wait for some time.

$ eb status

$ eb setenv SECRET_KEY_BASE=$(rails secret)

eb deploy

to push any changes

Add 'pg' gem to Gemfile. Add:

production:
    <<: default="" p="">    adapter: postgresql
    encoding: unicode
    database: <%= ENV['RDS_DB_NAME'] %>
    username: <%= ENV['RDS_USERNAME'] %>
    password: <%= ENV['RDS_PASSWORD'] %>
    host: <%= ENV['RDS_HOSTNAME'] %>
    port: <%= ENV['RDS_PORT'] %>
   
to database.yml.


Setup RDS instance
 
How to do the above using CLI?
 
Add a folder .ebextensions, and a file ruby.config

packages:
 yum:
  git: []

Add a file 0001_setup_swap.config in the .ebextensions folder with the following text:

commands:
  000_dd:
    command: echo “noswap”#dd if=/dev/zero of=/swapfile bs=1M count=3072
  001_mkswap:
    command: echo “noswap”#mkswap /swapfile
  002_swapon:
    command: echo “noswap”#swapon /swapfile
   
How to setup redis using CLI?

development:
 host: ‘localhost’
 port: ‘6379’
test:
 host: ‘localhost’
 port: ‘6379’
production:
 host: ‘your-name.iz6wli.0001.use1.cache.amazonaws.com’
 port: ‘6379’

How to setup background job processing SQS using CLI?

eb init - Creating Application
eb create - Creating environment
eb console - Opening Elastic Beanstalk Dashboard
eb list - Show current environment
eb use - Switch environment
eb logs - Logs Checking
eb deploy - Deployment

Type eb create
For environment name prompt, enter your-app-name-staging.

Type eb create
For environment name prompt, enter your-app-name-production

eb console

Check the UI for the health status of both environments.

// Switching and deploying to staging
eb use your-app-name-staging
eb deploy

// Switching and deploying to production
eb use your-app-name-production
eb deploy
 
// Filename: deploystaging.bash
#!/bin/bash

eb use meclub-staging
eb list
eb deploy


chmod 700 deploystaging.bash

// Execute script
./deploystaging.bash

References

Configure AWS Elastic Beanstalk to Scale
How to setup and deploy a Rails 5 app on AWS Beanstalk with Postgresql, Redis and more.
Elastic Beanstalk Docs

Phil Sturgeon Rest API Notes

First Document the API

1. Start with the resources. List all the resources and it's attributes in a text document. Skip defining relationships on the user.
2. Use data structures that can be used in requests and responses. Use JSON API specification in the data structures.
3. Convert the draft document of resources to data structures using API Blueprint syntax.
4. Use apiary.io to document the API using markdown.
5. Use MSON.
6.  You can show success and failure cases by using multiple transactions. Request . Request .

https://philsturgeon.uk/api/2016/11/22/apis-documentation-first/

Mocking APIs with API Blueprint

1. Apiary provides mocking server. No coding needed.
2. If you don't want to pay apiary. You can use drakov.

npm install -g drakov
drakov -f yourapi.apib

3. Use http CLI to test teh response.

http GET http://localhost:3000/products --json

https://philsturgeon.uk/api/2016/12/02/mocking-apis-with-api-blueprint/

Rails Serialization for REST APIs

1. Use active model serializers with json_api adapter.

https://philsturgeon.uk/api/2016/12/11/building-rest-apis-with-rails-basic-serialization/

Keeping API Documentation is Up to Date with Code

1. npm install -g dredd

2. dredd init

3. Use seeds to populate the database.

4. Run the dredd in test environment.

RAILS_ENV=test rake db:drop db:create db:migrate db:seed
dredd

5. Create a Makefile to simplify and run make docs_test.

# Makefile
.PHONY: docs_test
docs_test:
  @echo "Seeding database for documentation testing"
  @RAILS_ENV=test rake db:drop db:create db:migrate db:seed:dredd
  @echo "Running dredd... check logs/dredd.log for more information"
  @RAILS_ENV=test dredd > log/dredd.log && echo "Documentation is all good!"

https://philsturgeon.uk/api/2016/12/21/building-rest-apis-with-rails-documentation-testing/

https://philsturgeon.uk/api/2017/01/03/building-apis-with-rails-handling-errors-nicely/

Create a Hosted Zone using CLI

Install AWS CLI

pip install --upgrade --user awscli
aws --version

aws-cli/1.11.123 Python/2.7.10 Darwin/14.5.0 botocore/1.5.86

Configure AWS CLI

$ aws configure
AWS Access Key ID [None]: YOUR-ACCESS-KEY-ID  
AWS Secret Access Key [None]: YOUR-SECRET-ACCESS-KEY
Default region name [None]: us-east-1
Default output format [None]:

Provide the access key ID and secret access key when prompted. Accept defaults for region and format (json).

Create a Hosted Zone in Route 53

If you registered your domain with Amazon, they will automatically create a hosted zone with a set of name servers. Otherwise, you can create the name servers using Amazon CLI like this:

aws route53 create-hosted-zone --name www.clickplan.net --caller-reference 2017-07-23-13:35

{

    "HostedZone": {

        "ResourceRecordSetCount": 2, 

        "CallerReference": "2017-07-23:15:35", 

        "Config": {

            "PrivateZone": false

        }, 

        "Id": "/hostedzone/Z3F02TIXYMYTDY", 

        "Name": "www.clickplan.net."

    }, 

    "DelegationSet": {

        "NameServers": [

            "ns-1438.awsdns-51.org", 

            "ns-975.awsdns-57.net", 

            "ns-150.awsdns-18.com", 

            "ns-1978.awsdns-55.co.uk"

        ]

    }, 

    "Location": "https://route53.amazonaws.com/2013-04-01/hostedzone/Z3F02TIXYMYTDY", 

    "ChangeInfo": {

        "Status": "PENDING", 

        "SubmittedAt": "2017-07-24T01:36:35.194Z", 

        "Id": "/change/CO73DYX4SHITQ"

    }

}

You can see that the status is pending. It will take some time for this to complete. I checked the status in the AWS console. You can see that clickplan.biz ns records was created by Amazon, since that domain was registered on Amazon. We see the ns records for the domain registered on namecheap below that we created using AWS CLI.

After few hours, we can run the following command to check the resource record sets:

aws route53 list-resource-record-sets --hosted-zone-id Z3F02TIXYMYTDY

{

    "ResourceRecordSets": [

        {

            "ResourceRecords": [

                {

                    "Value": "ns-1438.awsdns-51.org."

                }, 

                {

                    "Value": "ns-975.awsdns-57.net."

                }, 

                {

                    "Value": "ns-150.awsdns-18.com."

                }, 

                {

                    "Value": "ns-1978.awsdns-55.co.uk."

                }

            ], 

            "Type": "NS", 

            "Name": "www.clickplan.net.", 

            "TTL": 172800

        }, 

        {

            "ResourceRecords": [

                {

                    "Value": "ns-1438.awsdns-51.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400"

                }

            ], 

            "Type": "SOA", 

            "Name": "www.clickplan.net.", 

            "TTL": 900

        }

    ]

}

You can see that there are two resource records have been created. One is of type NS and the other is SOA.

Retrieve a list of hosted zones.

$ aws route53 list-hosted-zones

{

    "HostedZones": [

        {

            "ResourceRecordSetCount": 2, 

            "CallerReference": "RISWorkflow-RD:3b4397e2-1ea4-4809-bb0c-b1c1714c4527", 

            "Config": {

                "Comment": "HostedZone created by Route53 Registrar", 

                "PrivateZone": false

            }, 

            "Id": "/hostedzone/Z5PP9SH99T8H9", 

            "Name": "clickplan.biz."

        }, 

        {

            "ResourceRecordSetCount": 2, 

            "CallerReference": "2017-07-23:15:35", 

            "Config": {

                "PrivateZone": false

            }, 

            "Id": "/hostedzone/Z3F02TIXYMYTDY", 

            "Name": "www.clickplan.net."

        }

    ]

}

The first record was created by Amazon when I registered clickplan.biz domain with Amazon domain registration. The second record was created by the command we ran using CLI for the clickplan.net domain that was registered with namecheap.

TO BE TESTED

The next step is to create a record set (A record and CNAME). The A record must point to the Elastic Beanstalk instance. 

 To create a new record set, first create a JSON file to describe the new record:

{

  "Comment": "CNAME record set for the zone.",

  "Changes": [

    {

      "Action": "CREATE",

      "ResourceRecordSet": {

        "Name": "clickplan.net.",

        "Type": "CNAME",

        "TTL": 60,

        "ResourceRecords": [

          {

            "Value": "www.clickplan.net"

          }

        ]

      }

    }

  ]

}

aws route53 change-resource-record-sets --hosted-zone-id 1234567890ABC --change-batch file:///path/to/record.json

{

  "ChangeInfo": {

    "Status": "PENDING",

    "Comment": "A new record set for the zone.",

    "SubmittedAt": "2017-07-24T00:00:00.000Z",

    "Id": "/change/CHANGEID123"

  }

}

The status of adding the new record is currently pending. Poll the server to get the updated status:

$ aws route53 get-change --id CHANGEID123

{

  "ChangeInfo": {

    "Status": "INSYNC",

    "Comment": "A new record set for the zone.",

    "SubmittedAt": "2013-12-06T00:00:00.000Z",

    "Id": "/change/CHANGEID123"

  }

}

A new record has been created and has been propagated to all hosts.

To create a A record:

Create the JSON file with the following:

{

    "Comment": "Create A record to point to Elastic Beanstalk",

    "Changes": [

        {

            "Action": "UPSERT",

            "ResourceRecordSet": {

                "Name": "www.clickplan.net",

                "Type": "A",

                "TTL": 300,

                "ResourceRecords": [

                    {

                        "Value": "This must be elastic beanstalk : FIGURE OUT THIS PART"

                    }

                ]

            }

        }

    ]

}

aws route53 change-resource-record-sets --hosted-zone-idZ1W9BXXXXXXXLB --change-batch file:///root/change-resource-record-sets.json

Check status:

aws route53 get-change --id C2JAIG0XXXXXXX

Helpful output to create JSON file for the aws cli command:

$ aws route53 change-resource-record-sets --generate-cli-skeleton
{
    "HostedZoneId": "", 
    "ChangeBatch": {
        "Comment": "", 
        "Changes": [
            {
                "Action": "UPSERT", 
                "ResourceRecordSet": {
                    "Name": "", 
                    "Type": "SPF", 
                    "SetIdentifier": "", 
                    "Weight": 0, 
                    "Region": "eu-west-1", 
                    "GeoLocation": {
                        "ContinentCode": "", 
                        "CountryCode": "", 
                        "SubdivisionCode": ""
                    }, 
                    "Failover": "PRIMARY", 
                    "MultiValueAnswer": true, 
                    "TTL": 0, 
                    "ResourceRecords": [
                        {
                            "Value": ""
                        }
                    ], 
                    "AliasTarget": {
                        "HostedZoneId": "", 
                        "DNSName": "", 
                        "EvaluateTargetHealth": true
                    }, 
                    "HealthCheckId": "", 
                    "TrafficPolicyInstanceId": ""
                }
            }
        ]
    }

}

# This is an example that creates an A record.

$ aws route53 change-resource-record-sets --cli-input-json '{

    "HostedZoneId": "Z35CNAMBBVZ957",

    "ChangeBatch": {

        "Comment": "This is a test and may be deleted.",

        "Changes": [

            {

                "Action": "CREATE",

                "ResourceRecordSet": {

                    "Name": "noah-test.zephyrhealth.com",

                    "Type": "A",

                    "TTL": 600,

                  "ResourceRecords": [

                    {

                      "Value": "192.168.0.1"

                    }

                  ]

                }

            }

        ]

    }

}'

# You may want to test your new A record using `host`:

$ host noah-test.zephyrhealth.com

noah-test.zephyrhealth.com has address 192.168.0.1

# This updates an existin A record.

$ aws route53 change-resource-record-sets --cli-input-json '{

    "HostedZoneId": "Z35CNAMBBVZ957",

    "ChangeBatch": {

        "Comment": "This is a test A and may be deleted.",

        "Changes": [

            {

                "Action": "UPSERT",

                "ResourceRecordSet": {

                    "Name": "noah-test.zephyrhealth.com",

                    "Type": "A",

                    "TTL": 600,

                  "ResourceRecords": [

                    {

                      "Value": "192.168.1.2"

                    }

                  ]

                }

            }

        ]

    }

}'

# This creates an alias (CNAME) to an A record.

$ aws route53 change-resource-record-sets --cli-input-json '{

    "HostedZoneId": "Z35CNAMBBVZ957",

    "ChangeBatch": {

        "Comment": "This is a test CNAME and may be deleted.",

        "Changes": [

            {

                "Action": "CREATE",

                "ResourceRecordSet": {

                    "Name": "noah-test-cname.zephyrhealth.com",

                    "Type": "CNAME",

                    "TTL": 600,

                  "ResourceRecords": [

                    {

                      "Value": "noah-test.zephyrhealth.com"

                    }

                  ]

                }

            }

        ]

    }

}'

References

AWS CLI Reference

AWS CLI Installation
AWS CLI Configuration
Listing Resource Record Set

Amazon Route 53 via Command Line

Updating AWS DNS records from the CLI
AWS - Amazon Web Services