← Documents

Technical Skills (Infra & System)

🖥️

One line — Hands-on infrastructure: I run a 3-server Home Cloud (Linux, NAT gateway via router port-forwarding, HTTPS with auto-renewing Let’s Encrypt) for development/testing, and have designed & deployed AWS networking (NAT Gateway / NAT Instance) myself.

Home Cloud — dev / test server operations

I operate three Linux servers directly within my home network via a NAT gateway (through router port forwarding), primarily for development. To enable HTTPS, I use Let’s Encrypt as the CA and have automated certificate renewal. These were initially built for service development and are now used as both personal dev servers and test environments. My in-house Reinforced Security Agent PoC also ran on this Home Cloud, leveraging Nginx error.log, access.log and deny.log.

Internet Router NAT gateway · port forwarding Linux server 1 (dev) Linux server 2 (test) Linux server 3 (Nginx) Let’s EncryptHTTPS 자동 갱신 Nginx logs (error/access/deny) → Reinforced Security Agent PoC
실제로 집에서 운영하는 3-서버 인프라 — 라우터 포트포워딩(NAT) + Let’s Encrypt HTTPS

AWS Cloud deployment — NAT Gateway / NAT Instance

Based on the experience above, I designed and deployed an AWS network architecture myself. The diagram below focuses on the key components I structured (sensitive details removed). It was written to share with teammates how to effectively use NAT Gateways and NAT Instances.

Related blog post: [AWS] NAT Instance: 직접 구성 & AMI로 NAT Gateway 대체 (1부)

VPC Public subnet IGW NAT Gateway / NAT Instance(AMI 로 직접 구성) Private subnet App server DB / 내부 서버 Private 서버의 아웃바운드는 NAT 를 통해서만 인터넷으로 (인바운드 차단)
직접 설계·배포한 AWS 네트워크 — Public(IGW·NAT)/Private(앱·DB) 분리, NAT Gateway 를 NAT Instance(AMI)로 대체