Access controls and network rules can both fail, and when they do, encryption is what stands between an attacker and readable data. It is the last line of defence, and in the cloud it is mostly a matter of configuration rather than code: nearly every storage and database service can encrypt data, but you have to choose how, and who controls the keys.
Encryption at rest protects data sitting in storage, while encryption in transit (TLS) protects it as it moves between systems. Both rely on keys, so the real security question becomes who can use them. A key management service such as AWS KMS creates and guards keys, controls who may use them through policies, rotates them, and logs every use for auditing.
Applications also need credentials of their own: database passwords, API tokens, and access keys. Hard-coding them in source code is one of the most common ways they leak, so secrets management stores them centrally, encrypted, access-controlled, and rotated automatically. The lessons use AWS examples, and the ideas carry over to Azure and Google Cloud. Watch them in order, then continue on to Cloud Security Posture Management.
An introduction to AWS KMS: how encryption keys are created, stored, and managed across AWS services.
A hands-on demonstration of creating a KMS key, using it to encrypt data at rest, and auditing key usage in CloudTrail.
A walkthrough of storing credentials in Secrets Manager, rotating them, and deleting them safely.