Git PRs and AWS VPC Peering: Why Both Sides Must Agree to Connect

A developer working through Day 29 of the KodeKloud Engineer platform completed two tasks centered on the same principle: both parties must participate for a process to work. The Git task involved opening a pull request on Gitea, assigning a separate reviewer, and merging via a merge commit — highlighting that a PR is a workflow layer, not a native Git feature. A common pitfall noted was reversing the base and compare branches, which makes the PR appear broken rather than obviously wrong. The AWS task required peering a public and private VPC so instances on each side could communicate, but was complicated first by a misconfigured security group that silently dropped external SSH connections by referencing itself instead of a CIDR range. A second obstacle arose around writing an SSH public key to authorized_keys on an instance that could not yet be accessed via SSH, underscoring that half a working connection can be more deceptive than no connection at all.