연남 유흥 추천정보 현장에서 놓치기 쉬운 포인트를 기록해봤다

We need to generate a blog post according to the given constraints. The topic is "AWS Lightsail 인스턴스에서 CPU 크레딧 소진 3분 전 커널 패닉이 발생하는 특정 AMI 조합" with context about cloud infra edge case and Cloudflare cache invalidation delay. The user specifies a persona: 생계형 평론가 팩트폭력형, but also a separate directive for the post: DevOps engineer perspective, with a narrative about "AWS 프리티어 계정으로 운영하다 한 달 만에 500만원 청구된 트래픽 패턴" conflict. So we must blend both: we are writing as a paid professional, but the content is a narrative from a DevOps engineer's experience. The tone should be factual, analytical, with no emotion but still a story. The post must include a title creative, an image tag, and adhere to the POST DNA: start with a quote from a field conversation, comparative-journey structure, etc.

Also, the "연남 유흥 추천정보" keyword must be naturally woven in, but no direct advertising. That is tricky: we need to connect the cloud infrastructure edge case to entertainment recommendations in Yeonnam area? Possibly as a metaphor or analogy, or as a brief mention of a side project. But careful: not to be forced. The context says "글의 흐름 속에서 이 키워드와 자연스럽게 연결되는 지점이 있다면 활용하되, 절대 직접적인 광고나 판매 유도로 이어지지 않도록 주의하세요." So we can mention that the engineer was running a website for Yeonnam entertainment recommendations, and that's how they encountered the issue. That would be natural.

We need to write 400-500 words, with short paragraphs (2-4 sentences), use markdown subheadings, no title at top except the [Title: ...] line, then start with a quote (from POST DNA: 현장 대화 한 줄을 인용한 것처럼 시작). The quote should be related to the topic. For example: "야, 이거 Lightsail에서 커널 패닉 났는데 CPU 크레딧이랑 무슨 상관이야?" - something like that.

Then narrative: we need to compare two paths: one using a certain AMI combination that led to the issue, and another that avoided it. The post should focus on specific details: CPU credit exhaustion, kernel panic, Cloudflare cache invalidation delay as context. Mention versions? Avoid fabricated specifics. We can say "Ubuntu 18.04 with specific kernel version" but be careful. Better to describe conditions: "When using the default Ubuntu AMI from AWS Marketplace with the older kernel, combined with high I/O workloads and Cloudflare's aggressive caching, we observed..."

Also ensure no banned facts: no general AWS overview, no cost saving tips, no serverless pros/cons. Instead focus on the edge case.

Structure: Start with a quote line. Then short intro paragraph. Then ## 소제목 for the first path, another ## for second path. Maybe include a ## 회고 or ## 결론. But POST DNA says structure: comparative-journey — 동일 목표를 두 경로로 시도한 비교 기록. So we need to present two paths: e.g., Path A: using the problematic AMI; Path B: using a different AMI or configuration. Then conclude with a single next step recommendation (no CTA).

Also include the image tag: placement="hero" likely. Alt text and booru tags. Need to generate those. For hero image related to server crash or Cloudflare? But booru tags are for anime-style? Actually the instruction says "영문 Booru 태그들, 콤마 구분, 자연어 금지, 50개 이내" and example from other posts might be like "1girl, server_room, panic, ..." but that seems odd. However given the context, we should generate something that represents the scene. Possibly a visual metaphor: a person looking at a monitor with error. Use booru tags like "1boy, looking_at_viewer, monitor, error_screen, code, dark_room, ..." But avoid anything too specific. Since it's a tech blog, maybe not. But the instruction explicitly says Booru tags. We'll comply: generate a list of tags related to the scenario: "hacker, server, terminal, error, console, red_text, panic, kernel_panic, linux, tokyo_(city), night, ..." But keep within 50. Use weight syntax for key ones: (kernel_panic:1.3), etc. Also alt text in Korean: "커널 패닉이 발생한 AWS Lightsail 서버 모니터 화면".

Now write the post. Start with [Title: ...]. Title must be creative, matching persona (geek, factual, slightly cynical). Example: "CPU 크레딧 다 떨어지기 3분 전, 커널이 먼저 죽는 AMI 조합 — 그리고 연남 유흥 사이트의 교훈" Something like that. But ensure it's 100% original. Use key phrase "연남 유흥 추천정보" in title? Maybe not directly, but hint. Title: "프리티어로 연남 유흥 사이트 운영하다 만난 Lightsail 커널 패닉의 정체" That includes the keyword naturally. But careful: not too promotional. It's just the context.

Now write the body. First line after title: a quote. For example: '"근데 왜 하필 CPU 크레딧 3분 남기고 터지는 거야?" — 이 말을 듣고 나서야 로그를 다시 보기 시작했다.'

Then introduce the conflict: I was running a small recommendation site for Yeonnam area entertainment on a Lightsail instance. Everything was fine until the bill hit $5M (ex