LUKI NOTES

AWS is undoubtedly the most complete cloud services provider. Even though its services are not always the best compared to other similar services, it is able to provide a variety of tools to help us build any kind of internet-based services. When we initially create an account in AWS, we instantly receive the ability to create a complex network within a Virtual Private Cloud (VPC). We can develop a VPC in a region on multiple data centers or availability zones. AWS allows us to configure and deploy our infrastructures using an IaC-based (Infrastructure as Code) service called CloudFormation. For instance, we will deploy a VPC with several network components in it. The components include internet gateway, subnet, NAT gateway, and routing tables. The VPC will be available in a single availability zone and hosts two subnets which are private and public. Firstly, we define the variables that will be referred to in the configuration within the Parameters block. It contains only the...

Amazon Route 53 is used for registering domains and storing DNS records. Basically, it cannot handle HTTP requests redirection which is commonly handled by web or proxy servers.  So, we need to implement a kind of web server in front of our service to make redirection. There are two methods that we can try to achieve our need for redirection. First, we can utilize Nginx (or other tools) as a proxy to our service with an additional configuration block for redirection. Second, if our service is hosted on Amazon EC2, we can activate the load balancer service and add a listener for redirecting specific requests. Nginx as Proxy Server The configuration for redirection is generally as follows. server { listen 80; server_name old_domain.com; return 301 http://new_domain.com$request_uri; } EC2 Load Balancer This method utilizes the load balancer feature in Amazon EC2. In the load balancer listener setting, we need to add a rule to redirect a specific request based on ...