AWS User Group KRK meetup #69 with Grand Parade

• Welcome and intro
• "When Scaling Fails – Queueing Users with AWS" - Mateusz Greń, SRE Architect, Grand Parade
• "How to terminate your AWS resources and optimize costs in a QA world" - Krzysztof Szyper, Solution Architect, Brainly
• Discussion, Q&A & Giveaways

Mateusz Greń: Mateusz is an SRE Architect and self-taught problem solver with over 7 years of cloud experience, specialising in AWS but with experience in GCP and Oracle Cloud as well. Since the beginning of his IT career, he has been with reliability and customer focus in mind. As part of SRE at Grand Parade, he has been working on developing solutions that address various internal and external pain points, shaping the flow of users into our services.

Will speak about:

Providing a smooth customer journey in cases where scaling is no longer the answer. In this high stakes, high throughtput story, I’ll talk you through why we decided to build a queueing solution, how we leveraged the AWS Solutions Library to quickly build a solution fit our domain-specific use case and the benefits it gave us.

Krzysztof Szyper

Since 2012, I have specialized in designing and delivering robust cloud solutions, with a strong focus on AWS, supplemented by engagements with GCP and other cloud platforms. My daily activities revolve around leveraging Terraform and Terragrunt to automate and scale cloud infrastructure efficiently. I am deeply committed to the principles of DevOps and FinOps, actively mentoring teams and promoting best practices to foster operational excellence and financial efficiency across projects.

Will speak about:

Almost every Amazon Web Services (AWS) tutorial starts with setting up IAM users as a way to interact with your AWS APIs. Unfortunately, that way of access is very dated and will not be used in any respected company. As IAM users and using a pair of access and secret keys is not considered secure and maintainable - for example, when onboarding and offboarding users. Even 3rd party services start to use their own IAM roles instead of those access keys for cross-account access to your infrastructure.