197 articles
Knowledge Base
AWS
197 articles in the AWS category · page 9 of 9.
- Migrating a CodeCommit repo to GitHub — refs, LFS, hooks, and the cutover redirect A clean CodeCommit-to-GitHub migration moves all refs, LFS objects, and hook contracts. Here is the mirror-push pattern, the validation checklist, and the redirect for stragglers.
- Launch templates vs launch configurations — what migration actually looks like Launch configurations are deprecated. AWS no longer lets you create them. Here is what the migration to launch templates actually entails on a 5-year-old ASG, the features you get back, and the gotchas in the path.
- CloudTrail and GuardDuty — the baseline that gives you forensics and the findings that actually matter Multi-region CloudTrail to S3 with KMS and Object Lock, Organizations trail vs per-account, GuardDuty findings that justify action vs the noise floor, EventBridge for auto-response. Here is the setup.
- Git on AWS after CodeCommit: Gitea, Bitbucket DC, GHES, and the Actions pattern Post-CodeCommit, Git-on-AWS means self-hosting Gitea, Bitbucket Data Center, or GitHub Enterprise Server in a VPC — or accepting GitHub.com with OIDC. Trade-offs for residency-bound workloads.
- Sticky sessions are a smell — when they're the right answer anyway Stickiness pins a client to one target. That breaks horizontal scaling, biases load, and creates incident shapes that look like 'one host is hot'. The better target is stateless app + Redis. Here is when stickiness is still the right call.