What does a AWS::Serverless::Function DeploymentPreference Type of AllAtOnce actually do?

When using an AWS SAM template to define an AWS::Serverless::Function, what practical difference is there between not specifying a DeploymentPreference property and specifying one with a Type of AllAtOnce?

With this minimal configuration (no Alarms or Hooks specified), is the end result somewhat identical in that the new version is immediately published? Presumably the CodeDeploy version creates an alias as well, but are there any other differences to be aware of?

주제

서버리스 컴퓨팅 개발자 도구 관리 및 거버넌스

태그

서버리스 AWS Lambda AWS CodeDeploy AWS CloudFormation

언어

English

rePost-User-6116601

질문됨 일 년 전217회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

This page explains the different deployment options - https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/automating-updates-to-serverless-apps.html

전문가

Indranil Banerjee AWS

답변함 일 년 전

rePost-User-6116601
일 년 전
Thank you, I have already read that and all other documentation I can find on the subject. Unless I'm missing something really obvious, I can't see that it answers my question.

Specifcally, I note that adding AutoPublishAlias alone will create an alias on the Lambda function. What difference does adding a DeploymentPreference with Type AllAtOnce make compared to not adding it at all (other than the obvious that it creates CodeDeploy resources - but what effect does that actually have)?

What does a AWS::Serverless::Function DeploymentPreference Type of AllAtOnce actually do?

관련 콘텐츠