Skip to content

AWS Proton

- 1. What is AWS Proton? (The "Elevator Pitch")

AWS Proton is a fully managed delivery service designed for Platform Engineering teams to manage infrastructure for container and serverless applications.

  • The Problem: In a company with 100+ microservices, developers might define their own infrastructure (CloudFormation/Terraform) differently, leading to a "mess" of unstandardized configurations.
  • The Solution: A central "Platform Team" creates Templates (standardized infrastructure stacks). "Developer Teams" then use these templates to self-serve and deploy their apps without worrying about the underlying infrastructure details.

- 2. Key Exam Terminology

To answer Proton questions correctly, look for these specific terms:

  • Platform Team vs. Developer Team: The exam often sets up a scenario with two distinct roles. The Platform team creates the standards; the Developer team consumes them.
  • Templates:
  • Environment Templates: Shared resources used by multiple applications (e.g., VPCs, shared Load Balancers, ECS Clusters).

  • Service Templates: Infrastructure dedicated to a single application (e.g., Fargate Task Definition, Lambda function, CI/CD pipeline).

  • Self-Service: Developers can deploy their own services using the approved templates without needing Administrator access to AWS.

  • Version Control: If the Platform Team updates a template (e.g., adds better logging), Proton can push these updates to all running services that use that template.

- 3. "Cheat Sheet": Proton vs. Service Catalog vs. CloudFormation

This is the most confusing part for candidates. Here is how to pick the right answer:

Service Primary Use Case (Exam Keywords) Key Difference
AWS CloudFormation "Infrastructure as Code (IaC)" The engine that actually builds the resources. Proton uses CloudFormation templates under the hood.
AWS Service Catalog "Menu of approved IT services," "Governance," "Compliance" Focuses on discrete resources (e.g., "Launch a compliant EC2 instance"). It is broader (can be anything) but less focused on the software deployment lifecycle.
AWS Proton "Platform Engineering," "Microservices," "Containers/Serverless" Focuses on deployment workflows. It manages the entire stack (including CI/CD pipelines) specifically for modern apps. It allows for centralized updates of the stack.

Exam Rule of Thumb:

  • If the scenario mentions "managing a catalog of approved EC2 images/S3 buckets for compliance," choose Service Catalog.
  • If the scenario mentions "standardizing CI/CD pipelines and infrastructure for serverless/container microservices," choose AWS Proton.

- 4. Typical Exam Scenario

Question:

A large company has multiple development teams building microservices using AWS Lambda and Amazon ECS. The Platform Engineering team wants to ensure that all services are deployed using a standard CI/CD pipeline and adhere to specific security configurations (logging, encryption). They want to minimize the operational overhead for developers while maintaining central control over infrastructure updates. Which service should they use?

Answer: AWS Proton

  • Why? It specifically targets "microservices," "Lambda/ECS," and "standardizing CI/CD pipelines" with central control over updates.

- 5. Summary for SAA-C03

You do not need to know how to write a Proton template (Jinja code) for the exam. You do need to know:

  1. It is for Containers and Serverless.
  2. It separates Infrastructure definition (Platform team) from Deployment (Developer team).
  3. It allows for centralized management of infrastructure standards across many different applications.