r/AWS_cloud

Hey everyone!

I'm working through the hands-on labs on AWS Educate, but I'm getting overwhelmed by the endless steps and services in every project.

There are so many CLI commands, roles, and settings (EC2, Lambda, S3, DynamoDB...) that it feels impossible to memorize or remember the whole flow. I feel like I'm just clicking through instructions without really retaining it.

For anyone who's been through this:

• How do you actually remember and make sense of all these steps?
• Do you take notes, draw diagrams, or use a specific approach so it sticks?

Would love to hear how you deal with this. Thanks!

I’m considering a fully online internship that requires me to pay a fee. There doesn’t seem to be any real company work or proper projects, but they provide a certificate.

Does a certificate from this type of paid internship have any real value to recruiters?

Also, I’m currently learning AWS and aiming for a Cloud Engineer role. Where can I find genuine AWS/Cloud internships with real hands-on experience? Any recommendations for platforms or companies?

I am a Data Engineer. I am getting caught up by work all day. As a result I have got imposter syndrome . I would like to have a study buddy who can push me.

If you are interested in Data Engineering we can discuss that as well.

Let me know anyone interested. 🧐

I'm enrolled in AWS Academy and want to get the most out of it, both practically and theoretically. The problem is I'm spending a lot of time on the theory, but the information just doesn't stick — I forget it fast. If anyone's been through this, how did you actually make it stick? Also, if anyone has notes (basics or architecture-related) they wouldn't mind sharing, that'd be amazing. Thanks!"

Anyone here from the UK or who knows the actual range rather than the Internet search based average figures can please let me know what is the salary upper and lower band for AWS Data Center Senior Electrical Engineer - Design with L6 level in London?

Could you please keep it with:

1. Base?

2. Bonus - Year 1 & 2?

3. RSU total?

Also what is your opinion on AWS office LHR16 Vs LHR14 ?

Thanks 🙌

Im studying cse engineering currently 3rd year in chennai,even though i studying a btech cse degree i have literally zero knowledge of coding or other technical skills like linux,github,dataeng,fullstack blah blah,though i dont wanna get unemployed sitting as good for nothing in home after completing my degree i dont have any guidance i dont have many freinds so all i wanna know is can i choose azure cloud engineering as my career and get employed as fresher ?how to learn?where to learn?is az 104 completion enough to land on a job? Also do i need to complete any other coding or otger skills like devops or fullstack before choosing cloud. These are my biggest doubts if any kind soul can answer all my questions who is currently working as a cloud engineer please please please please please dm meeeeeeeee ty if u read fully

Been building this on nights/weekends for the past couple months. Background: I've spent 3.5 years doing PAM engineering (CyberArk), so this is basically me translating that into cloud-native.

The problem I kept running into reading about this space: every tool I looked at (Cloudsplaining, Prowler, even AWS's own IAM Access Analyzer) stops at detection. They'll tell you a role has a wildcard action or an unused key, and then... that's it. You get a report. Somebody has to go fix it by hand. Even the free/open-source ones don't touch remediation.

So I built NHI Risk Analyzer — discovers IAM users/roles/groups, runs it against a set of detection rules (grounded in Rhino Security Labs' documented privilege escalation paths + Cloudsplaining's policy analysis methodology + CIS benchmark stuff for credential hygiene), and then actually does something about what it finds:

Architecture is offline-first — it snapshots the AWS account state to JSON once, then evaluates all the risk rules against that snapshot with zero live API calls. Makes the whole rule engine testable and fast (unit tests run in under a millisecond) and means findings are reproducible against an exact point in time instead of drifting mid-scan.

Still rough in places — trust policy analysis isn't built yet, surgical wildcard-narrowing (vs. the current boundary-containment approach) is next, and it's AWS-only for now. Not trying to oversell it, it's a v1. But the core loop — detect, decide safely, act — actually works end to end, which is the part I couldn't find anywhere else at this tier.

Repo: In comments

Would genuinely appreciate anyone poking holes in the detection logic or the remediation safety assumptions — that's exactly the kind of feedback I'm here for.

Which AWS certification we can choose AWS certified developer or solutions architect? Can any one please suggest one which worthy to do and advantages of doing them

Sharing one of the AWS projects our team at Maximyz Cloud recently completed with RupeeCircle, a peer-to-peer lending platform.
The challenge was pretty straightforward: as the platform scaled, managing infrastructure, security, monitoring, patching, and compliance manually was becoming difficult.
We helped them move towards a more automated and reliable AWS setup using services like AWS Systems Manager, Control Tower, CloudWatch, CloudTrail, EC2 Auto Scaling, and RDS Multi-AZ.
The results:
• 80% less manual operational work
• 60% faster incident resolution
• Patch compliance went from 60% → 100%
• 25% reduction in operational costs
• 99.99% platform uptime
We're going to use this community to share more of the projects we're working on, including the architecture decisions, challenges, and actual outcomes.
Here's the full case study if anyone wants to take a look:
https://maximyzcloud.com/case-study/rupeecircle-a-peer-to-peer-lending-platform/

I'm trying to understand how AWS CloudFront handles a failed background revalidation when using stale-while-revalidate.

Suppose I have something like:

Cache-Control: max-age=300, stale-while-revalidate=60, stale-if-error=86400

After the object becomes stale, CloudFront serves the stale response and asynchronously revalidates it with the origin.

What happens if that background revalidation fails?

Does CloudFront simply keep the existing stale object in the cache?

Does stale-if-error get invoked when the background revalidation fails?

If both stale-while-revalidate and stale-if-error apply, does SWR take precedence over SIE, similar to Fastly?

Does the failed background request affect the TTL/expiry of the existing cached object?

I'm particularly interested in the behavior of the background request itself, rather than a normal synchronous request to the origin that returns an error.

Last week I finally shipped my side project. Pretty standard stack: Next.js frontend, Node backend, PostgreSQL, Redis for sessions/caching. Nothing fancy.
I went with AWS because “that’s what real companies use” and I figured I’d need to scale once marketing kicks in.

I set up:
ECS / Fargate for the app
RDS for Postgres
ElastiCache for Redis
ALB
Some NAT Gateway stuff so the services could talk outbound

I have maybe 30-40 real users so far. Traffic is still tiny.
This morning I opened the billing dashboard.
$2,047 for the first 7 days.
Most of it is just idle costs, data transfer, and the NAT Gateway apparently. I barely have any actual usage.
I’m actively marketing this thing now so a cheap VPS isn’t really an option long-term, I need something that can scale when (if) users actually show up. But I also can’t keep burning $8-10k/month while the product is still early.
How the hell are people shipping fullstack apps these days without getting destroyed by cloud bills?
What are you using that actually scales and doesn’t require a full-time DevOps person just to keep costs reasonable?

I’m looking for some advice from people currently working in cloud engineering.
I basically have no experience in cloud right now. I worked as a computer repair technician for almost three months, where I worked with computers, hardware, troubleshooting, repairs, etc., but I don’t have any professional cloud experience.
I’ve recently become interested in cloud engineering and I’m trying to figure out the best path to get into the field. I’ve been looking into certifications and different courses, and I’m currently considering a Cloud Engineering Academy/Starter program that I found.
The problem is that the academy is somewhat expensive for me right now, so I’m not sure if it’s actually worth paying for or if I could learn everything I need through cheaper/free resources and build my experience that way.
For someone starting basically from zero, what would you recommend?
Should I start with something like AZ-900/Azure Fundamentals?
Should I learn networking and Linux first?
Is getting a certification actually necessary?
Should I try to get an entry-level IT/cloud support job first?
And most importantly, is a paid cloud engineering academy worth it for someone in my situation, or should I avoid spending the money and follow a self-study path?
I’m willing to put in the work. I just don’t want to spend a lot of money on a course if there’s a better path I could take on my own.
Any advice from people who actually work in cloud engineering would be greatly appreciated.

Hi everyone,
I’m currently looking for a job change and would really appreciate any referrals or leads.
I have 4 years of experience as a Cloud Infrastructure Engineer at Accenture, working across AWS, Azure, Windows & Linux infrastructure. My experience includes cloud infrastructure management, server administration, patching, monitoring, backup & DR, VMware, IAM, networking, PowerShell/Bash automation, and incident/change management.
Key skills:
• AWS & Azure Infrastructure
• Windows & Linux Administration
• EC2, S3, VPC, IAM, CloudFormation, SSM
• Azure VMs, Recovery Vault & Update Manager
• PowerShell, Bash & AWS CLI
• VMware ESXi / vCenter
• Patching & Vulnerability Management
• Monitoring – CloudWatch, Dynatrace, Grafana, Splunk
• Backup & Disaster Recovery
• Active Directory, DNS, DHCP & Networking
I’m currently serving my notice period, with my LWD on September 21, 2026, and I’m actively looking without an offer in hand.
📍 Preferred locations: Bengaluru | Hyderabad | Coimbatore | Chennai | Kerala
💼 Open to: Cloud Infrastructure / CloudOps / AWS / Azure / Windows / Infrastructure Engineer roles
If you know of any relevant openings or can refer me, please DM me or comment below. Any leads or referrals would be greatly appreciated.
Thank you! 🙏
#OpenToWork #JobSearch #CloudEngineer #CloudInfrastructure #AWS #Azure #CloudOps #WindowsAdministrator #InfrastructureEngineer #BengaluruJobs #HyderabadJobs #ChennaiJobs #CoimbatoreJobs #KeralaJobs #Hiring #Referral

Anyone here is use Floci for their dev work? If so, what has been your experience?

How can i be a cloud security engineer in 3 years

I have 3 years to study, what can i learn to be a cloud security engineer (free courses) and what projects can i do, give me your advice please i need it.

Thanks all

I have a small EC2 Linux instance that becomes unreachable after I SSH into it frequently. It also takes few minutes to shut it down even CPU is at 0%.

Instance details:

- Instance type: t3.micro

- OS: Ubuntu 22.04 LTS

- CPU credit mode: Unlimited

- vCPU: 2

Has anyone experienced an EC2 instance becoming unreachable after repeated SSH access?

(I posted on r/aws but tied to wait for moderation)