Deploy RedCap in AWS Reference Architectures

I've built a fully private AWS API architecture over the past two days vpc, private subnets, an interface vpc endpoint for privatelink, a private api gateway with a resource policy locked to that endpoint, an internal load balancer bridging cloudfront into the vpc, lambda, dynamodb, cognito issuing jwts validated before any request reaches the lambda no public endpoint anywhere. everything forced through one path learned how privatelink actually works under the hood, why cloudfront cannot talk to a vpc endpoint directly, and why an alb has to sit in between to bridge that gap wrote it up as a reusable cdk template in typescript, fully documented, repo link in comments #AWS #CloudArchitecture

What does it take to process 2M documents a day, up to 99% accuracy across regulated industries? The answer: one serverless architecture on AWS. Buildsimple's full story: https://go.aws/4ypfjpO

I’ve just published a new article on AWS Builder Center about AWS Lambda. The article explains how Lambda works, how it fits into serverless and event-driven architectures, and some common backend use cases such as APIs, message processing, file processing, and automation. It also covers an important point: serverless does not mean Lambda is the right choice for every workload. 🔗 https://lnkd.in/dB7Nk7Mm #AWS #AWSLambda #Serverless #BackendDevelopment #EventDrivenArchitecture

☁️ AWS Serverless File Storage Architecture Designed and implemented a serverless file storage system using Amazon S3, AWS Lambda, API Gateway, and DynamoDB. The architecture supports secure file upload, download, listing, and deletion using S3 presigned URLs. 🔗 GitHub: https://lnkd.in/eGwNxjwZ #AWS #CloudComputing #Serverless #S3 #Lambda #APIGateway #DynamoDB #CloudArchitecture

Moving to AWS doesn't make you cloud-native. After 5 years of working with cloud-native architectures, here's the real shift: ❌ Lift and shift = same problems, now on AWS ✅ Cloud-native = design for failure, scale on demand, decouple everything The mindset change matters more than the services you use. S3, Lambda, SQS, RDS — these are tools. Resilience, observability, and loose coupling — that's the architecture. #AWS #CloudNative #Microservices #SoftwareArchitecture #BackendEngineering

I’ve just published a new article on AWS Builder Center about Amazon SQS. The article explains how message queues help decouple applications, improve resilience, and support asynchronous processing in backend and microservices architectures. I also cover the difference between Standard and FIFO queues, how SQS works with AWS Lambda, and the role of Dead Letter Queues (DLQs) when message processing fails. 🔗 https://lnkd.in/d5rJvw4g #AWS #AmazonSQS #EventDrivenArchitecture #BackendDevelopment #Microservices

Amazon Web Services (AWS) NAT Gateway or NAT Instance? Don't choose just because everyone else does! ☁️ Even in 2026, NAT Instances have their place in AWS architecture. NAT Gateway → Less management, managed scalability. NAT Instance → More control, customization and potential cost savings. And with Regional NAT Gateway, AWS has introduced another architecture option! A good architect understands the trade-offs before choosing the service. #AWS #AWSNetworking #NATGateway #NATInstance #CloudArchitecture #SolutionArchitect #CloudWithPartha

Day 47/108 — Route Tables 🚀 Today I learned about VPC Route Tables. 📚 What I learned: 1. Route tables define where network traffic should go. 2. Routes can direct traffic to destinations such as an Internet Gateway or NAT Gateway. 3. Subnets are associated with route tables. 🛠️ Hands-on: Created/explored route tables and routes. 💡 Key takeaway: Route tables control how traffic moves within and outside a VPC. Day 47/108 — Completed ✅ #AWS #CloudComputing #DevOps #LearningInPublic #CloudJourney

Amazon Aurora vs Amazon RDS — the choice isn’t simply about which one is faster. The right database depends on your workload, scalability needs, cost model, operational effort, and application requirements. Choosing the right fit early can prevent unnecessary complexity as your AWS environment grows. Planning your AWS database architecture? Make the decision based on the workload—not just benchmarks, connect with Harsh Sharma and Anchal Vashisht #AWS #AmazonAurora #AmazonRDS #CloudArchitecture #DatabaseStrategy