Lambda was unable to decrypt the environment variables because KMS access was denied

I've just run into the very same issue as guys in serverless framework community: [279](https://github.com/serverless/examples/issues/279).

After `chalice deploy` I've found two of my Lambdas (one connected to SNS and another to S3 events) dysfunctional with the error

`The ciphertext refers to a customer master key that does not exist, does not exist in this region, or you are not allowed to access.`

The error appeared in AWS console only with complete silence in logs. Hence the failure isn't easy to discover as it just silently refuse to process SNS/S3 events.

Despite the issue could be easily fixed by application deletion and re-deployment, it might be quite painful in production environment.

The report concerns chalice deploy and Lambda functions connected to SNS and S3 events; begin by reproducing that deployment and inspect the AWS console error. Done means the deployed functions no longer fail with the KMS access error, and the failure is discoverable rather than silently preventing event processing.

Written by the indexing model from the issue text.