Implemented Blue-Green deployment with Amazon ECS.
Two services (Blue & Green) behind ALB for zero-downtime traffic switching. Tested successfully with
"Hello - I'm BLUE".
Built using ECS Cluster, ECR, CodeBuild, and ALB.
#AmazonECS#BlueGreen#AWS#DevOps
AI can code, but one of the most important skills for software engineers now is learning how to read code deeply.
In the past, writing code was the main skill. Today, reading, understanding, reviewing, debugging, and improving code are becoming even more important.
Built an Agentic Workflow with AWS Bedrock Agents.Asked: "How many S3 buckets are in my AWS account?"Got: "You have 3 total. 1 is publicly accessible."Powered by Step Functions, Lambda, and Bedrock Agent.
#AWS#AWSAgents#AmazonBedrock#Cloud
If you rely on AI for everything without understanding the output, you’ll struggle when things break in production.
The engineers who will stand out in the AI era are the ones who can understand systems, spot bad logic, fix bugs, review architecture decisions,
Just implemented VPC Traffic Mirroring on AWS.
Source instance now mirrors all traffic to a target for inspection, with zero impact on production flow.tcpdump + CloudWatch metrics = magic.
Super useful for security monitoring and troubleshooting.
#AWS#VPC#TrafficMirroring
Just shipped a VPC middlebox routing lab on AWS.
Configured custom route tables and network interfaces for full traffic control across the VPC.
Learned a lot about advanced AWS networking today.
#AWS#VPC#Networking
One of the best pieces of career advice I’d give anyone entering tech:
Focus on fields that still heavily require critical thinking, problem-solving, and human decision-making.
Areas like cloud engineering, DevOps, Site Reliability Engineering (SRE), cybersecurity,
That’s why many vibe coders who don’t fully understand software engineering give AI very implicit instructions instead of explicit requirements.
The result is often messy architecture, insecure logic, technical debt, and systems that become difficult to scale or maintain.
Saying a framework, language, or cloud provider is “the best” is usually the wrong mindset.
Most cloud platforms offer similar core services with differences in pricing, ecosystem, scalability, support, and specialized tooling.
The right choice always depends on the system you’re building, the scale, the team, the budget, and the business requirements
That’s why understanding system design and software architecture matters so much. It helps you choose the right tools instead of blindly following trends
Saying a framework, language, or cloud provider is “the best” is usually the wrong mindset.
Most cloud platforms offer similar core services with differences in pricing, ecosystem, scalability, support, and specialized tooling.
@Damilolawo1a Every path in tech is different.
But one of the best ways to learn is through project-based learning.
Build projects, solve real problems, break things, fix them, and keep improving. That process teaches far more than endlessly consuming tutorials.
@V1rendra_ uhhmmm i think when you have simple system (or mvp) go for vercel. If you have complex system u have to use cloud platforms (AWS, GCP, or AZURE...)