Set a gradual deployment policy — CodeDeploy and Lambda deployment policies

Your goal

Create a gradual Lambda deployment policy and inspect its first traffic share.

Why this matters

A gradual release policy limits the first share of traffic given to a new version. You will configure a canary percentage and interval. This lab stores the policy without switching actual traffic.

Words you will use

A canary rollout gives a new version a small first share of traffic. A percentage sets that share. An interval sets how long the first stage lasts. A deployment configuration is the saved policy.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create a deployment application

Create a CodeDeploy application for Lambda. An application groups deployment settings. This lab does not create a live production service or switch any visitor traffic.

2. Choose the first traffic share

Create a time-based canary deployment configuration. Choose the percentage for the new version’s first share and set a five-minute interval. Small rollouts still need monitoring and a rollback plan.

Initial traffic percentage: Choose 10–50 percent. This is a saved policy, not an active rollout. Suggested practice value: 10.

3. Read the deployment configuration

Retrieve the policy and check its percentage and interval. The configuration is not attached to a deployment group, and no actual traffic has been shifted.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.