Set 5, Question 27 & 60

[tyzh]

27: Easiest way to encrypt S3-IA and rotate key every 365 days.

Wouldn’t AWS owned key is a better choice because “AWS KMS automatically rotates AWS managed keys every year (approximately 365 days).”, and free 🤑

60: Reduce lambda cold start time

Why is increase memory allocation is the answer? Reference also seem pointing to provisioned concurrency.

• This discussion was modified 1 year, 9 months ago by  tyzh.

[Carlo-TutorialsDojo]

Hello tyzh,

Thanks for your feedback.

Could you post a snippet for each question so I can look them up?

Regards,

Carlo @ Tutorials Dojo

[Davidcg]

for #27. AWS owned in this context refers to SSE:S3 which does is not rotated every 365 days.
I’d refer to this link here: https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html

for #60. When you allocate additional memory, the compute power is also upgraded on the lambda, more compute power equals less time to run the executable

[Carlo-TutorialsDojo]

Hello David,

Thanks for your feedback.

Yes, AWS-owned keys are not the same as AWS Managed keys. And you cannot enable nor disable key rotation on AWS-owned keys.

It is also true that CPU power increases proportionally to the allocated memory for a Lambda function

Regards,

Carlo @ Tutorials Dojo