A company is developing an application that uses AWS Lambda functions. A DevOps engineer must create an AWS CloudFormation template that defines a deployment configuration for gradual traffic…

Question

Options

• AUse an AWS::CodeDeploy::DeploymentConfig resource. Define a TimeBasedCanary
• BUse an AWS::CodeDeploy::DeploymentGroup resource. Define the DeploymentStyle property as
• CUse an AWS::Lambda::Version resource with the VersionWeight property to control the
• DUse an AWS::Lambda::Alias resource with the RoutingConfig property to specify weights for

• A
  12% (2)
• B
  6% (1)
• C
  6% (1)
• D
  76% (13)

Explanation

For gradual traffic shifting in Lambda deployments, AWS Lambda aliases support the RoutingConfig property, which specifies the percentage of traffic routed to different versions of the Lambda function. This enables weighted traffic shifting between versions as part of deployment strategies. The AWS::Lambda::Alias resource's RoutingConfig can specify multiple versions with weights, enabling canary or linear deployment strategies without needing CodeDeploy resources explicitly. AWS CodeDeploy resources like DeploymentConfig and DeploymentGroup are used primarily for blue/green deployments and managing deployment strategies outside Lambda aliases. Lambda versions themselves do not have a VersionWeight property; instead, weighted routing is managed via aliases.

No community discussion yet for this question.