Git Force-Push and AWS NAT Instance: Key Lessons from a 30-Day Lab Challenge

A developer completing day 30 of the KodeKloud Engineer platform tackled two tasks that required deliberately disabling built-in safety mechanisms. In Git, a hard reset was performed to rewind branch history, followed by a force-push — a practice generally discouraged on shared branches but acceptable in isolated lab environments. The author clarified that the real rule is not to avoid force-pushing entirely, but to understand whose history is being overwritten, recommending --force-with-lease over plain --force. On the AWS side, a NAT instance was configured in a public subnet to allow a private EC2 instance to reach S3, after discovery revealed the task's environment was missing an internet gateway entirely. Both exercises highlighted that protective defaults exist for good reason, and bypassing them safely requires understanding what they guard against.