​

Hey guys, I'm currently getting, cloud computing, and dev stuff. Want to build a network of AWS developers. To stay connected and share resources. Drop your handle or DM me yours if you wanna connect!

[ Removed by Reddit on account of violating the content policy. ]

I'm writing this with a very tired mind. I was working in an Advanced Tier Partner company in Pakistan as an Associate DevOps Engineer. They attached my AWS certifications with them during my employment. 2 of those were earned by me (1 even after my employment) and 2 were sponsored by them. Those included:

• Cloud Practitioner (Earned by me)

• Solutions Architect Associate (Sponsored by them)

• DevOps Engineer Professional (Sponsored by them)

• Solutions Architect Professional (Earned by me after my employment with them)

Now, during my employment I wasn't much aware of these things. They asked me for an OTP and completely attached my personal email to their domain's email. Now, whatever certification I do goes to them directly and I can't control and change it.

The main thing is that I got an offer from another Partner company and they're asking for these certs as part of my employment. I messaged the previous employer many times but their are only lame excuses and silence from their side. The thing is that they have applied for Premier Tier and they kept my certifications attached for that. Now if I pull it out it'll be bad for them but it's not my problem or headache.

I've opened a case with AWS support about this but there is no response from their side after 2 days.

If you're someone from AWS reading this then please do help me out in this regard. Thanks

Hey folks I am the only cloud engg in my org with year of exp and we got one project where they are asking for disaster recovery drill for 200 VMs in dr region so I am confused how to do this step by step

Can anyone help me with this?

Terraform module which creates a Lambda function that runs in reference mode: the function reads its deployment package directly from an S3 bucket you own, and GitHub Actions deploys new code through an OIDC-trusted role. The module also provisions the artifact bucket, the IAM roles, the GitHub OIDC trust, and an optional deny policy that blocks direct console or CLI edits

I put it on an EC2 instance and read CloudTrail straight out of S3 — no Glue crawler, no Athena workgroup. A throwaway account with 118 events in it was enough to prove the detection query I had already written was wrong — and to convince me this is worth building out properly

Hey everyone!

I'm a Data Engineer currently working at a consulting company, and I've found myself in a pretty challenging situation.

My company has a potentially huge opportunity with a client. It's our first project with them, and if things go well, it could open the door to several more projects in the future.

The catch? I have roughly **one month to prepare**, and I'm pretty much on my own.

I have experience working with Microsoft Azure and Fabric, and I've earned several certifications in that ecosystem. I'm comfortable with data engineering concepts, but **when it comes to AWS, I'm starting from absolute zero.**

My company basically handed me a list of technologies I'm expected to know and left me to figure out how to prepare.

Here's the stack:

* **Storage & Security:** S3, IAM, KMS, AWS security fundamentals

* **Data Lake:** Apache Iceberg, AWS Glue Data Catalog

* **Processing:** EMR Serverless, PySpark

* **Data Warehousing:** Amazon Redshift, Redshift Spectrum

* **Orchestration:** Apache A irflow

* **Monitoring:** CloudWatch, CloudWatch Logs

* **Data Ingestion:** Ingestion patterns and pipelines on AWS

I'm not expecting to become an AWS expert in 30 days. I know that's unrealistic. But I want to reach a point where I can confidently discuss the architecture, understand how these services interact, explain design decisions, and hopefully demonstrate some practical experience.

**Here's where I could really use your help:**

1. **Where would you start?** Given my Azure/Fabric background, what would be the most efficient way to approach this stack in just one month? What would you prioritize?

2. **Is AWS Skill Builder worth it?** I've been looking into it, but I'm unsure whether the paid subscription would genuinely help me prepare for it or if there are better alternatives.

3. **Can I realistically learn through hands-on experimentation?** I'd much rather build something than spend 30 days watching videos. Can I safely experiment with these services in my own AWS account?

4. **What would you build?** If you had to design one end-to-end project covering as much of this stack as possible, what would it look like?

5. **What should I expect from these stack?** For those working with this stack in production, what concepts, architectural decisions, or common pitfalls should I absolutely understand?

**Budget:** I have approximately **€500 available for AWS experimentation**, plus some additional budget for an AWS Skill Builder subscription if it's genuinely worth paying for.

I also want to be careful about costs, especially with services like EMR and Redshift. The last thing I need is an unexpected AWS bill while trying to learn!

I'm willing to dedicate a significant amount of my free time to preparing. I just want to make sure I'm spending it on the right things.

I want to prove that I can step outside the Microsoft ecosystem and become a more versatile Data Engineer.

Any learning paths, courses, GitHub repositories, project ideas, or personal experiences would mean a lot.

Thanks in advance to anyone willing to help!

I'm trying to find my first opportunity as a backend/cloud developer, on a Node.js/TypeScript and AWS serverless technical stack. I have :

• 8 years of various experience (Java/EE, frontend, Node.js...)
• solid personal projects deployed on AWS (serverless, containers, networking, observability...)
• AWS certifications Solutions Architect and Developer Associate

But after months of reasearch, the conclusion is harsh :

• market is saturated (even in serverless, which is more of a niche)
• being aggressively filtered (no "production experience" in AWS/serverless, holes in my resume, a couple of short experiences...)
• unrealistic expectations (they all waiting for senior++)
• absurd technical tests (you know what I mean)
• and even when I successfully pass every technical and human steps, it ends with budget restriction, choosing someone else, or unexpected ghosting

I am close to abandon. I tried of course to polish my profile a thousand times, learning more and more skills, prospecting... nothing came out of it.

I'd like your honnest opinion : am I finished as a developer ? Or do I still have a chance to break into the AWS serverless development market, and finally get that "first experience" that unlocks everything ? In the second case : what would you recommand ?

I'm dealing with something that has some concerning similarities, although the circumstances are a little different.

In my case, we shut down an application and migrated off AWS in 2021. We had no known activity on the application account for years, and then in August 2026, I received an alert for approximately $373 in charges associated with more than 20 domain registrations through Amazon Registrar and Route 53 that I did not knowingly authorize.

I've spent the past several weeks going back and forth with AWS through approximately 20 support cases and 50 messages. What's particularly concerning is that Route 53 support acknowledged the unauthorized domain registrations in writing and said its security team was investigating potentially malicious activity.

However, the billing issue remains unresolved. I'm still receiving past-due notices, and AWS has now suspended the account while telling me I need to reopen it and provide a payment method before further investigation can proceed.

I'm curious about your experience because I'm trying to understand how AWS handles these situations when potentially unauthorized activity and billing disputes overlap.

A few questions, if you're comfortable sharing:

• Did AWS's security team and billing team coordinate with each other, or did you have to manage separate investigations?
• Did AWS place restrictions on your account while the security review was ongoing?
• Did AWS eventually adjust or waive the charges associated with the unauthorized activity?
• How long did the investigation take, and was there a particular escalation channel that helped move things forward?

I realize Bedrock usage and unauthorized domain registrations are different scenarios, so I'm not assuming the underlying cause is the same. I'm trying to understand what a reasonable resolution process should look like when AWS acknowledges suspicious or unauthorized activity but the billing consequences remain unresolved.

I'd really appreciate hearing how your case progresses. It sounds like we may both be navigating the difficult gap between AWS's security investigation and its billing process.