E17 · Woori FIS · Feb 2026 – Oct 2026
Operations tools that run on a PC with no internet
Turning repeated requests into tools and a standard process
4 tools31 Python packages, bundled offline
- Python
- boto3
- AWS
- Automation
- Closed network
In one line
I built an offline development environment and four Python tools for work PCs with no internet, turning repeated traffic requests into a standard process.
Background
Work PCs in the financial sector have no internet access because of network separation (a Korean financial regulation), so ordinary development tools are hard to install.
Security group (a virtual firewall in front of servers) requests kept coming in. Each one meant following the network, security groups, and routes by hand in the console.
What I did
An offline development bundle. I packaged WinPython, Terraform, Terragrunt, boto3 (the Python library for AWS), and other tools, 31 Python packages in all, into an offline development environment that starts from a single executable.
I solved the problems that come with working offline.
- Generated Terraform configuration files to match the environment
- Resolved version conflicts between libraries
- Handled errors from the editor trying to reach the internet
What I did
Four Python tools. Select a tab to see each tool.
- What it does
- Collects network, routing, database, load balancer, security group, and server status
- Input
- Target account
- Output
- Excel file
Result
- Tools replaced checking the console by hand
- Separating security group problems from routing problems cut unnecessary allow rules that would have been added just to open more access
- Handling repeated requests became a standard process that anyone can follow the same way
What I learned
The fix a requester asks for (“please open it”) and the real problem (a missing route) can differ. When a request comes in, check what is actually failing first.