Edited for Grammar / Clarity Not sure about sources, but I recently gave a few on another post on this subreddit a few moments ago: -- Create Infrastructure that would support a 3 Tier Architecture -- LB/Compute/DB -- how many VPCs would you setup? How many Subnets? How are your NACLs & SGs created for Least-Privilege? What would your Route Tables look like? When would you use a NAT, when would use a IGW? How would you make it a Hybrid architecture / account for Bastion Hosts (aka Jump Boxes, if you're weird) -- What Load Balancing services would you use for that 3 Tier Architecture? Can you speak through the difference between Layer 4 and Layer 7 Load Balancing? How would you do it in ELB, how would you do it via Nginx or HAProxy? -- What will you use for your Compute layer? Can you setup an ASG & EC2 Fleet to point your ELB at? Can you talk through different scaling events, cooldowns and/or grace? How will they communicate with the DB Layer? What instance sizes would you provision to start with? -- What will you do for your DB Layer? Can you talk through RDBMS vs NoSQL? OLAP vs OLTP? Would you use a managed solution or spin up your own on EC2? -- How will you monitoring this infrastructure? What services would you use and do you know how to set them up? Can you read Flow Logs to figure out if someone is trying to run recon, versus a user who cannot get in? How would you roll up all of the different data sources? -- How would you secure this? What SG / NACL rules would be too permissive, or not enough? How would you handle Global Access? What services can you leverage to protect it? Would you use Native Tools, 3rd Party or a Combination? -- How will you scale / alleviate load on your 3-Tier? When would you Horiz. Scale versus Vert. Scale, and why? When would you use Read Replicas or maybe Elasticache? Can you talk through Caching, Sharding, Redis v Memcached? These are some I have been asked during interviews / have asked potential candidates. Hope that helps. More on reddit.com

You can find a list of community submitted learning resources here: https://dataengineering.wiki/Learning+Resources I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns. More on reddit.com

You can definitely expect a range of debugging scenario questions in AWS interviews beyond just networking. For instance, you might be asked about troubleshooting issues with AWS S3, like why an object isn't accessible or why a bucket policy isn't working as expected. Another common area is debugging IAM roles and policies, where you might need to figure out why a user or service doesn't have the expected permissions. RDS issues, such as connectivity problems or performance bottlenecks, are also fair game. These scenarios test your ability to diagnose and resolve issues across different AWS services, so it's good to be familiar with the AWS Management Console, CloudWatch logs, and AWS CLI for troubleshooting. When it comes to preparing for these questions, hands-on practice is invaluable. Try setting up different AWS services and intentionally misconfiguring them to see what kind of errors you encounter and how you can resolve them. For more structured guidance, you might find resources like the AWS Well-Architected Framework and AWS re:Invent videos helpful. If you're looking for a tool to help you navigate these tricky interview questions and ease the pain of the job search process, an interview helper AI can be a great resource. I’m on the team that made it, and it’s designed to help you ace your job interviews by providing real-time suggestions and answers. More on reddit.com

No, those questions are for you to resolve any doubts you have with the company, not to impress me as an interviewer. More on reddit.com