Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Hotswap vs full deploy

This revision card explains Hotswap vs full deploy. It starts from the need that waiting for a full CloudFormation deploy on every Lambda code tweak slows class labs. It describes cdk deploy --hotswap can push Lambda code/asset changes faster, skipping some CFN waits (not for all changes). The how-to section covers how to use hotswap in lab iterations; use full deploy for IAM, VPC, and production releases. An example on the card is code-only change updates the function in seconds; role change still needs full deploy.

Hotswap vs full deploy Waiting for a full CloudFormation deploy on every Lambda code tweak slows class labs. cdk deploy --hotswap can push Lambda code/asset changes faster, skipping some CFN waits (not for all changes). Use hotswap in lab iterations; use full deploy for IAM, VPC, and production releases. Code-only change updates the function in seconds; role change still needs full deploy.
Hotswap vs full deploy · Download PNG
Read card text

What this card says

Why do we need it?

Waiting for a full CloudFormation deploy on every Lambda code tweak slows class labs.

What is it?

cdk deploy --hotswap can push Lambda code/asset changes faster, skipping some CFN waits (not for all changes).

--hotswap

How to do it

Use hotswap in lab iterations; use full deploy for IAM, VPC, and production releases.

Example

Code-only change updates the function in seconds; role change still needs full deploy.

See all AWS revision cards