DevOps & Cloud Engineer | AWS | CI/CD | Terraform | Docker | Golang | Kubernetes | Java | Python | MySQL
🚀 DevOps & Cloud Engineer | AWS | CI/CD | Terraform | Docker | Golang | Kubernetes I'm a DevOps & Cloud Engineer passionate about automating infrastructure and building reliable, scalable cloud systems. I bring hands-on experience with AWS services, CI/CD pipelines, and Infrastructure as Code to streamline software delivery and enhance operational efficiency. From writing backend logic in Golang to provisioning cloud infra with Terraform, and deploying Dockerized apps using Jenkins, I’ve worked across the stack to integrate development and operations seamlessly. 🔧 Core Skills: DevOps: Jenkins, GitHub Actions, Docker, Ansible, Terraform Cloud: AWS (EC2, S3, IAM, Lambda, Route 53, CloudWatch) IaC & Automation: Terraform, Ansible, Shell scripting Containerization & Orchestration: Docker, Kubernetes Backend Development: Golang, REST APIs, MySQL, MongoDB Frontend (for full-stack apps): ReactJS, JavaScript, Tailwind CSS Tools: Git, GitHub, Linux, VS Code 🛠️ Project Highlights: ⚙️ Built automated CI/CD pipelines with Jenkins, Docker, and GitHub Actions ☁️ Deployed and managed staging/production environments on AWS 🔧 Provisioned cloud infrastructure using Terraform and Ansible 🧠 Wrote backend APIs in Go and connected to full-stack apps 📊 Set up IAM roles, monitoring (CloudWatch), and cloud security best practices 📚 I share learnings and tutorials on Hashnode. 📩 Let’s connect: mdsharjil32@gmail.com
Markdown supported · ⌘↵ to post
Anik Sikder
This is an incredibly clear and practical breakdown of a frustrating and often overlooked LocalStack + Terraform issue! 🔥
I’ve run into similar mysterious errors caused by provider version mismatches, and it’s easy to get stuck chasing phantom fields that you never defined. The step-by-step “identify → choose strategy → cleanup → verify” approach is exactly what every dev needs to troubleshoot this smoothly.
The distinction between locking to AWS Provider v4.x for stability versus managing v5.x manually really helped clarify my own projects. Also, highlighting the localstack_providers_override.tf as a hidden gotcha is gold, I don’t think many realize that file exists and auto-generates in the background.
One question for the community: for those using Option B (v5.x manual config), how are you managing updates to LocalStack endpoints and compatibility as both evolve? Any tips or tools to keep things in sync without too much manual overhead?
Thanks for sharing this - definitely saving me time and headache on my next local infra build! 🚀