Day 31: Stash Keeps What Status Won't Show, and Private Is a Flag, Not a Subnet
Both of today's tasks involved something real that the interface never mentions. Git keeps work in a place that git status will not tell you about. The RDS console wizard builds a resource on your behalf and never says it did. Neither is a bug, and both cost you time the first time you meet them. One Git task, one AWS task. Park uncommitted work with stash and bring a specific entry back, then…
Two specific lessons were learned during this experience. First, Git's stash feature creates a hidden work area that is not displayed by git status. To restore a specific stash entry, use git stash apply with the stash index number, and use git stash apply --index to also restore the staged state. Second, creating a private MySQL RDS instance on AWS requires configuring the instance with several specific settings.
This includes providing a private subnet group, specifying storage autoscaling parameters, and setting the --no-publicly-accessible flag to prevent the instance from receiving a public DNS name. Additionally, the CLI requires creating a subnet group manually, which includes specifying subnets in at least two availability zones.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
