Easy ReviewDOP-C02
Configuration Management and IaC9

Proton

Understand Proton templates, end of support, and migration alternatives.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

Platform templates and end of support

AWS Proton was a platform service for deploying serverless and container applications from standardized infrastructure templates. Support ended on October 7, 2026, so the workflow below is historical.

How it works

  1. A platform administrator registered templates, including a service templateA service template defines the infrastructure needed to deploy and maintain an application in an environment. defining application infrastructure and compatible environments.
  2. A developer selected a service template and supplied a source code repository.
  3. Proton provisioned a service and a deployment pipeline, an automated sequence for delivering changes. Each service instanceA service instance is an instantiation of a service template in a specific environment. represented the service template in a specific environment.
  4. Proton identified instances using older template versions so an administrator could request an upgrade.

Exam cues

  • If the question says a team wants to use Proton for a new workload, remember that support has ended.
  • If the question says replace Proton with a Git-driven CloudFormation workflow, think CloudFormation Git sync, because AWS lists it as an alternative, although it lacks Proton-style environments and advanced pipeline features.

Remember

  • New customer signup ended after October 7, 2025; support ended October 7, 2026.
  • CloudFormation Git sync does not include Proton-style environments or advanced pipeline features.

Trap: CloudFormation Git sync is an alternative for a Git-driven workflow, but it does not provide Proton-style environments or advanced pipeline features.

Proton template workflow
123TemplatesProtonPipelineService instance
  1. Administrators register environment and service templates.

  2. A developer selects a service template and Proton provisions a pipeline.

  3. The pipeline deploys code to a service instance in an environment.

Da documentação da AWS (15)
  • AWS Proton provided automated infrastructure provisioning and deployment for serverless and container-based applications using versioned templates.
  • A Proton service template defines the infrastructure needed to deploy and maintain an application or microservice in an environment.
  • Administrators could specify which environment templates were compatible with a Proton service template.
  • A Proton service instance instantiates a service template in a specific environment.
  • A Proton service normally includes service instances and a pipeline.
  • A platform administrator registers templates and a developer selects a service template and source repository; Proton provisions the service and its pipeline.
  • Proton identified service instances using outdated template versions and allowed administrators to request upgrades.
  • AWS Proton support ended on October 7, 2026.
  • New customers could not sign up for Proton after October 7, 2025.
  • Proton data was retained until October 7, 2026 and deleted after that date.
  • AWS lists CloudFormation Git sync as an alternative for a Git-based workflow, with no Proton-style environments or advanced pipeline features.
  • Proton minor template versions require a backward-compatible schema.
  • A Proton minor version does not require the developer to supply new information when updating.
  • Proton did not check whether infrastructure code in a minor template version was backward compatible.
  • Proton major template versions can introduce incompatible changes that typically require new developer inputs.

Environment management and migration

AWS Proton environment templates defined shared infrastructure for applications. After Proton support ended, teams needed an alternative for infrastructure automation, while deployed CloudFormation stacks and their resources remained intact.

How it works

  1. An environment templateAn environment template defines infrastructure shared by multiple applications or resources. defined infrastructure shared by multiple applications or resources.
  2. A customer managed environment template connected to existing provisioned infrastructure without Proton managing it.
  3. After support ended, the Proton console and resources became inaccessible. Deployed CloudFormation stacks and their resources remained intact.
  4. AWS lists CloudFormation Git sync and CodePipeline with CodeBuild as alternatives, with different tradeoffs.

Exam cues

  • If the question says multiple applications need shared infrastructure, think environment template, because it defined their common resources.
  • If the question says retain management of existing infrastructure, think customer managed environment template, because Proton connected to that infrastructure without managing it.
  • If the question says use a Git-based workflow, think CloudFormation Git sync, because AWS lists it as an alternative, though it lacks Proton-style environments and advanced pipeline features.
  • If the question says use CodePipeline and CodeBuild as an alternative, think more implementation work and less built-in developer self-service, because those are the tradeoffs AWS lists.

Remember

  • Proton support ended on October 7, 2026.
  • Deployed CloudFormation stacks and their resources remained intact after support ended.

Trap: Intact CloudFormation stacks do not mean Proton is still accessible. The Proton console and resources became inaccessible after support ended. CloudFormation Git sync does not provide Proton-style environments.

Da documentação da AWS (7)
  • A Proton environment template defines shared infrastructure used by multiple applications or resources.
  • A customer managed environment template connects to existing provisioned infrastructure, which Proton does not manage.
  • Deployed CloudFormation stacks and their resources remain intact after Proton support ends.
  • AWS Proton support ended on October 7, 2026.
  • After support ended, the Proton console and Proton resources became inaccessible.
  • AWS lists CloudFormation Git sync as an alternative for a Git-based workflow, with no Proton-style environments or advanced pipeline features.
  • AWS lists CodePipeline and CodeBuild as an alternative with more implementation work and less built-in developer self-service.

Flashcards

toque para virar
Resposta

·

Todos os 9 flashcards em lista

A team is choosing an infrastructure automation service for a new workload. Is AWS Proton available for this purpose?

No. AWS Proton support ended on October 7, 2026. AWS lists CloudFormation Git sync as an alternative for a Git-based workflow.

A team replacing AWS Proton wants CloudFormation changes driven by a Git repository. Which AWS-documented alternative fits?

CloudFormation Git sync, although it does not provide Proton-style environments or advanced pipeline features.

In a historical AWS Proton design, several applications needed shared infrastructure. Which template defined those common resources?

An environment template.

Before AWS Proton support ended, a team wanted to deploy services onto existing infrastructure while retaining its management. Which environment option fit?

A customer managed environment template. Proton connected to the existing infrastructure without managing it.

A team used AWS Proton to deploy infrastructure through CloudFormation. What happened to the deployed stacks when Proton support ended?

The deployed CloudFormation stacks and their resources remain intact.

Can a team continue using the AWS Proton console to automate infrastructure after support ended?

No. The Proton console and Proton resources became inaccessible after support ended.

A team is considering CloudFormation Git sync as an AWS Proton alternative. Does it include Proton-style environments?

No. CloudFormation Git sync supports a Git-based workflow but does not include Proton-style environments or advanced pipeline features.

A team wants infrastructure automation after AWS Proton support ended. What tradeoff comes with the CodePipeline and CodeBuild alternative?

It requires more implementation work and has less built-in developer self-service.

A team wants to retain AWS Proton-style environments when moving to CloudFormation Git sync. Does Git sync provide them?

No. AWS lists Git sync as a Git-based alternative, but it has no Proton-style environments.

Você concluiu todos os tópicos da DOP-C02!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified DevOps Engineer - Professional (DOP-C02) no Easy Review. Venha estudar também!