Ravi Sir's Cards › AWS
GSI vs LSI pick
This revision card explains GSI vs LSI pick. It starts from the need that wrong index type wastes money or locks you after create. On the card, the building blocks include GSI — new PK anytime, eventually consistent. LSI: same PK, create-time only, can be strong. The how-to section notes name access , then choose GSI/LSI/second table , then pick projection , then watch cost. An example on the card is priya Raman rejects a late LSI request and adds a sparse GSI instead.
Read card text
What this card says
Why do we need it?
Wrong index type wastes money or locks you after create.
What is it?
GSI: new PK anytime, eventually consistent. LSI: same PK, create-time only, can be strong.
GSI
How to do it
Name access → choose GSI/LSI/second table → pick projection → watch cost.
Example
Priya Raman rejects a late LSI request and adds a sparse GSI instead.