Creating ALB with modified GUI
In the process of setting up the ALB to change the region, I noticed that the GUI had changed. So, I would like to write this part and move on. Keeping records will definitely be helpful when creating a new AWS instance.
1. First, select the Load Balancer type. Since the purpose is https:// security registration, ALB was selected.
2. In the next process, each item must be entered.
- Load balancer name required (written arbitrarily)
- For the VPC, make sure that the instances you want to connect to are the same!
- You must select at least two Mappings regions, and all of them were selected.
- The security group was the same as the security group used when creating the instance, and the default security group was not selected. I could have created a new security group, but since it was the same, I didn't create it again.
- The listener created the default HTTP 80 and HTTPS 443, created a target group, and connected it.
- The target group will be connected to the instance, so register the instance. This part has changed from before. The target was used for load balancing and was set to the existing HTTP 8080 port.
Once you have created a load balancer, you need to modify Route53 so that this load balancer can be connected. Just set the previously created record type A as an alias and edit it with the ALB, the region (Seoul), and the created alias.
The thing to note here is that if the listener's HTTPS 433 is not registered in the security group created when creating the instance, you must add it to the security group in order for https:// to be properly secured and the web page to be opened.
You might also like…
8 Sep
GPT-6 Astra: What the Benchmarks Actually Show
5min25 Aug
Unreal MCP: How Claude Code Now Drives the Unreal Editor Directly
5min25 Aug
When Do AI Glasses Developer Platforms Actually Open? A 2026 Timeline
4min6 Jul
3D Gaussian Splatting vs Unreal Engine: Two Ways to Build a 3D World - and Where Each One Ships
7min2 Jul