About Sundararajan narasiman



View all posts by Sundararajan narasiman

Enable static website hosting in S3

Home | SharePoint 2013 | Enable static website hosting in S3

AWS Simple Storage Service (S3) offers one of the powerful capability to host static websites. In this post let’s cover the steps for the same.

Create a sample bucket by name ‘mytestdomain.com’. The convention is that bucket name should match with the website domain name.

In this case the domain name for the static website is mytestdomain.com. The S3 bucket should match that name.

image

Enable public read access to this bucket.

image

Enable static web site hosting for the bucket by selecting ‘Use this bucket to host a static website’ and specifying the index document and error document.


image

Upload the index.html and error.html file and grant the public read access to it. Now access the static website url

provided by S3. It should be in this format.

http://s3bucketname.s3-website-region.amazonaws.com/

It should render the index.html in the browser

image

To render this website with the actual domain name, we need to leverage Route 53 DNS service offered by AWS.

Create a hosted zone for our custom domain.

image

Once the hosted zone is created, S3 presents with list of name servers. It should be mapped with the domain registrar for routing the request through Route 53.

The next step is to create a Record Set for the Hosted Zone bye selecting the Alias Target to the S3 bucket enabled for static website hosting.

image

It takes few minutes for the record set changes to get propagated. After that try accessing the website domain url. It should render the index page. This completes this article.





Working with a Github private repository from windows 10 PC

Home | SharePoint 2013 | Working with a Github private repository from windows 10 PC

Github has become almost the defacto standard when it comes to code repository for DevOps. Github occupy large foot print in the Devops space – either in the form of open source GIT or in the form of commercially supported offerings through ISV’s. Github also comes into two flavors – public repository and private repository. As the name indicates, the public repositories are open to entire world without any restrictions. The private repositories are useful when a team wants to collaborate in a closed manner. The aim of this post is to elaborate the steps required for working with Github private repositories from Windows 10.


The first step is to set up keys for SSH and it to ssh key agent.

Open bash for windows 10.

ssh-keygen -t rsa -b 4096 -C “your_email@example.com

When prompted enter a filename to save the keypair.Also enter the passphrase for the keys.
image

You will see a confirmation for generation of keypair.
test
The next step is to add generated private key to the SSH agent. Before adding ensure that SSH agent is running
image
Navigate the path where the key pairs are present. Then type this command.
ssh-add keyname
It should prompt for the passphrase created with the key. Enter the passprase and you should get confirmation like below.
image
Now we have completed adding the private key portion of the key pairs to the SSK agent. The next 
step is to add the public key portion of this keypair into the Github repository.
Navigate to the folder in Windows 10 PC where the key pairs are located. Copy the contents of public key file (.pub).
image
Paste the contents of the public key file to the key field.
Now we can navigate to the bash on windows 10 and start performing all the regular git bash commands.
This completes the set up for accessing Github private repositories from Windows 10 PC.


Client.Timeout exception in docker client

Home | SharePoint 2013 | Client.Timeout exception in docker client

I was trying to pull some docker images from DockerHub. I got this error message “Client.Timeout exceeded while waiting headers”.

image

After doing a bit of debugging and going through online forums, i tried this option of changing the DNS server to Fixed  and restarted the Docker engine.

image

After that I was able to execute all the Docker commands successfully.

image

Back to blogging

Home | General | Back to blogging

For almost three years I have not used this space for sharing my thoughts on technology. I could not do this for various reasons. In a span of three years lot has happened in my professional life and I’ve switched planes and nowadays I’ve diversified myself by exploring into open source technologies as well. We live an interesting time where we see a tremendous explosion in new technologies especially Artificial Intelligence, Big Data, Machine Learning etc. I will be sharing my experiences on what i work and learn from a developer standpoint. Stay tuned !!!