In the last post in this series, we saw how we can execute a piece of a code when something is uploaded to the S3 bucket. We saw all the configuration we might have to go through. We also saw how we can test our trigger manually and automatically when object is uploaded. At last, we also came accross a trouble and shooted it. In this section, we will continue our venture.

Today I'll go through how get and configure a HTTPS certificate from Let's Encrypt for all the subdomain. I have already posted about how we can automate installation of Jenkins & Nginx with Ansible. I have also done a post where I talk about how to enable HTTPS on a non-wildcard basis i.e. only for the root domain and not on subdomain.

I have been tinkering with this new framework and have a little bit of experience with FastAPI as of now. What I've though of is to do a post about authentication and authorization. I'm sure going to do a registration and login system and nothing fancy this time. I am going to use JWT as authorization mechanism.

You know what is difference between a senior software enginner and a junior? One of the diffrence is that senior develop organised thinking over the span of time. Why not practice it from the start?

In this post, we are going to see how we can use existing AWS infrastructure to create thumbnail for uploaded images. In this venture, we are going to use S3 trigger to execure Lambda function to do whatever we want. But in this case, we'll create thumbnail so that we can save on some bandwidth when only a smaller version of image is required on the frontend. So let's get started.

I don't claim to be a DevOps expert. I just know some basic ssh and scp, that's all. I have done whatever server configuration till date by ssh'ing into instances and then configuring them by hand. But now-a-days I feel like spinning up and destroying a server has increased in my life style.

There are a plenty of VPN providers out there. What's common between all of them? You can't trust them. They may have a no-log policy but as a company, there is always a tendency that they might share our browsing data to some third party. In this post you'll learn how you can spin up your own VPN with Amazon AWS.

In this short post, I will show how we can forward port from a remote host to a local computer. We will forward a port from AWS EC2 to local computer with openssl.

I have been using AWS with Terraform to provision my development instance on AWS cloud. When I wanted to configure dotfiles, change SSH port and configure some cron jobs, I hit a bottleneck. I literally was not able to do those tasks with user scripts because they had no effect. That was the time when creating custom image of the distro came into my mind.

This is my rundown of AWS's whitepaper about Implementing Microservices on AWS. In this article I talk more about micrsoservices and less about AWS. I also talk about paths already engraved around microservices. So, without further ado, let's get started.

I've dabbled over many languages in the past, from PHP, Java, Python, C/C++, JavaScript and now Go (some of them I only know the syntax of). I never experienced concurrency the way it does in Go. In my first company I did some concurrent programming using Python threads, but the threads didn't share any data between them.

Suppose you are working with softwareA which depends on libraryA, instead of copy-pasting the libraryA over and over again when a new version of the library is released what we can do is use submodule to make this process DRY and elegant.

In 2014, Google hinted that they are running tests taking into account whether sites use secure, encrypted connections as a signal in our search ranking algorithms. This means it will affect SEO in some way. Today in the age of HTTP2, https is defualt. Default in the sense that many server software will only allow HTTP2 when https is configured.