Without trying to sound rude. You've posted a repository with no code at all. Some readme files about how I can install some npx scripts that will look at my aws account and have access to some credentials. The repo has 5 commits, and it was created 3 days ago. And we're supposed to trust it and just use it? More on reddit.com

Prep on "tell me about a time when..." Questions. There will be no leetcode questions. Brush up on networking, DNS, load balancing , peering, http and SSL/tls. More on reddit.com

Thought these were questions to ace the interview process at AWS and not AWS-type job interview :) More on reddit.com

I’ve actually done over 50 interviews for cloud support engineer roles, and you don’t actually have to have any AWS knowledge coming into the role (they do love to see that you have tried to learn AWS in between applying and your interview, as this goes to the “Learn and Be Curios” LP). You’ll apply for a specific ‘profile’ like Linux, Networking, Windows, Database, Deployment, etc. If applying for one of the core profiles like Linux or Networking, you’ll need to meet the bar in technical knowledge in that area. If they feel that you have a good foundation, then they can teach you everything you need to know about how AWS works. So say your applying for the Networking profile; this is my biggest suggestion: don’t focus on AWS specific knowledge such as how VPCs work, or public vs private subjects, endpoints, etc. They won’t ask you about any of that. They will test for foundational networking knowledge that is situation based and focuses on troubleshooting something that you have little visibility into (which is exactly what you will be doing). More on reddit.com