Amazon Web Services: The Developer Associative Journey

What do you need to know to become a AWS Certified Developer Associative.

•3 min read
Amazon Web Services: The Developer Associative Journey

In this series, I'll share my journey with Amazon Web Services over the next months. I plan to learn about new services and revisit ones I've already worked with, documenting my experience along the way.

Join me as I explore the world of AWS and gain new insights into cloud computing to become an AWS Certified Developer Associative.

The motivation

A few years ago, I had the opportunity to work with AWS (Amazon Web Services) and it was a truly transformative experience. One of the main motivations behind revisiting and writing this guide stems from the incredible impact it had on my past projects and the ever-evolving nature of cloud computing.

Setting up and provisioning resources became a breeze with services like EC2 (Elastic Compute Cloud), which allowed for seamless scalability and reduced infrastructure costs. The flexibility to choose different instance types and pay only for what was utilized was a game-changer.

Moreover, the ability to easily host websites on AWS S3 (Simple Storage Service) and serve them through CloudFront CDN (Content Delivery Network) enhanced the performance and ensured reliable global accessibility for my applications. It simplified the deployment process, enabling me to focus on the core functionality of my projects.

AWS constantly introduces new services and keeps improving the existing ones, making it essential to stay updated and expand my knowledge.

Starting the journey

The overview begins by introducing readers to the concept of cloud computing and its rapid growth in recent years. It explains how AWS emerged as a major player in this field, providing a range of services that enable businesses to scale, store data, and run applications on the cloud.

The guide then goes on to explore the various components and services offered by AWS. It covers services such as compute, storage, databases, networking, along with others. Each service is explained in detail, highlighting its purpose, features, and use cases.

How are we going to organize all this content?

Because there are too many services, information, use cases, and practical examples to share with you, i'm gonna separate all of this in chapters. The ideia is to bring not only conceptual data, but also a hands-on.

Take a look at the chapters bellow:

  • Chapter 01: Introduction to Cloud Computing
  • Chapter 02: The AWS Ecosystem and Services
  • Chapter 03: Mastering the AWS Console Access with IAM
  • Chapter 04: Using EC2 to build a scalable Applications
  • Chapter 05: The power of Route 53
  • Chapter 06: More than assets to store in S3
  • Chapter 07: Understand Serverless and how to use Lambdas, Gateways and Step Functions
  • Chapter 08: The amazing DynamoDB
  • Chapter 09: SQS and SNS for clear communication
  • Chapter 10: How to use Cloud Information and check the health of your services
  • Chapter 11: The Developer Tools behind AWS. Learn how to use CodeCommit, CodeDeploy, CodePipeline and others.
  • Chapter 12: More about Security, Identity, & Compliance and how to use Cognito and Secrets Managers.
  • Chapter 13: All about the exam and how to be prepared to get theAWS Certified Developer — Associate
Vitor Britto
Buy Me A Coffee
Senior Software Engineer

Hello, I'm Vitor Britto 👋

With almost two decades of experience in software development, I have dedicated my career to creating elegant solutions for complex problems. Currently, I work as a Senior Software Engineer, focusing on web and mobile application development and best practices in software development.

I am passionate about sharing knowledge and contributing to the software development community. Through this blog, I share my experiences, learnings and insights about software development, architecture and modern technologies.

In addition to development, I am an enthusiast for clean code, design patterns and agile methodologies. I believe that the best software is not only functional but also sustainable and scalable.