<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/aws/</link><description>Recent content in AWS on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>SSH Wouldn't Connect, So I Spent the Day Peeling an Onion</title><link>https://blog.lynxflow.co/en/posts/aws-vps-ssh-dpi-tunnel/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/aws-vps-ssh-dpi-tunnel/</guid><description>&lt;img src="https://blog.lynxflow.co/images/aws-vps-ssh-dpi-tunnel-cover.webp" alt="Featured image of post SSH Wouldn't Connect, So I Spent the Day Peeling an Onion" /&gt;Connection closed by 18.183.98.38 port 22 — I stared at that line for a while today.
It was supposed to be simple. Spin up two small AWS Lightsail instances, one in Tokyo (18.183.98.38), one in Seoul (43.201.19.231), both 2 vCPU / 2 GB / 60 GB / Ubuntu 24.04, and drop a Nezha probe on them to monitor the little fleet I run. Drop the key, chmod 600 the pem, write two aliases tokyo and seoul into ~/.ssh/config. An hour&amp;rsquo;s work.</description></item></channel></rss>