Money-saving tips for the frugal serverless developer

Presented at AWS Community Day Turkey 2024

Transcript

1. Money saving tips for the frugal serverless developer Yan Cui @theburningmonk
2. Yan Cui http://theburningmonk.com @theburningmonk AWS user since 2010
3. Developer Advocate @ Yan Cui http://theburningmonk.com @theburningmonk
4. Yan Cui http://theburningmonk.com @theburningmonk Independent Consultant
6. Billing alarms
7. Everyone should use billing alarms.
8. They are not perfect. But they can still save your a$$.
12. Keeping logging cost under control
13. CloudWatch often costs much more than your core application.
14. As cost goes up, value goes down.
15. How to keep CloudWatch Logs cost under control 1. Do structured logging.
16. How to keep CloudWatch Logs cost under control 1. Do structured logging. DEBUG INFO WARN ERROR Detailed events for debugging application. General information that highlights progress of application. Potential problems, but doesn’t stop application from working. Issues that require immediate attention.
17. How to keep CloudWatch Logs cost under control 1. Do structured logging. Log at INFO or above in production. DEBUG INFO WARN ERROR Detailed events for debugging application. General information that highlights progress of application. Potential problems, but doesn’t stop application from working. Issues that require immediate attention.
18. How to keep CloudWatch Logs cost under control 1. Do structured logging. Log at INFO or above in production. 2. Sample DEBUG logs in production. e.g. 5% of invocations.
19. How to keep CloudWatch Logs cost under control 1. Do structured logging. Log at INFO or above in production. 2. Sample DEBUG logs in production. e.g. 5% of invocations. 3. Set log retention to 30 days.
21. CloudWatch Logs AWS Lambda AWS Lambda stdout asynchronously invokes any log aggregation service
23. CloudWatch Logs AWS Lambda AWS Lambda stdout asynchronously invokes any log aggregation service double paying for logs
24. Lambda Extensions + Telemetry API
25. https://docs.aws.amazon.com/lambda/latest/dg/telemetry-api.html
27. CloudWatch Logs AWS Lambda
28. https://lumigo.io/blog/lumigo-launches-log-management
34. DEBUG INFO WARN platform.initStart platform.start platform.initRuntimeDone platform.initReport platform.runtimeDone platform.report unhandled exception
35. DEBUG INFO WARN platform.initStart platform.start platform.initRuntimeDone platform.initReport platform.runtimeDone platform.report unhandled exception
36. Right-sizing Lambda memory
37. More memory = more CPU = more network bandwidth
39. Easy to be wrong by an order of magnitude.
42. Right-sizing Lambda functions
43. https://github.com/alexcasalboni/aws-lambda-power-tuning
44. Use ARM architecture
45. 25% cheaper
46. Performance may vary…
47. Best for functions with a lot IO wait time.
48. Caching
49. Caching is a cheat code for building performant & scalable applications.
50. Route53 CloudFront API Gateway Lambda DynamoDB
51. Route53 CloudFront API Gateway Lambda DynamoDB client-side caching
52. Route53 CloudFront API Gateway Lambda DynamoDB client-side caching edge caching
53. Route53 CloudFront API Gateway Lambda DynamoDB client-side caching edge caching application-level caching
54. Route53 CloudFront API Gateway Lambda DynamoDB client-side caching edge caching application-level caching ElastiCache
55. Route53 CloudFront API Gateway Lambda DynamoDB client-side caching edge caching application-level caching Momento
56. Route53 TTL
58. Use longer TTL for stable domains
59. Avoid CORS
60. Enabling CORS for API Gateway is easy
61. Enabling CORS for API Gateway is easy But you still pay for those CORS requests!
63. You might be double paying for every user request to your API…
65. Choose the right service
66. Every architectural decision is a buying decision.
67. Using the wrong service can be very costly.
70. Assuming 1KB per request
71. Assuming 1KB per request
72. Services that charge by uptime are order(s) of magnitude cheaper at scale.
73. Assuming 1MB per request 😂 $53,837.87 $68.99
74. www.thefrugalarchitect.com
75. Law I. Make Cost a Non-functional Requirement. Law II. Systems that Last Align Cost to Business. Law III. Architecting is a Series of Trade-offs. Law IV. Unobserved Systems Lead to Unknown Costs. Law V. Cost Aware Architectures Implement Cost Controls. Law VI. Cost Optimization is Incremental. Law VII. Unchallenged Success Leads to Assumptions.
76. Law I. Make Cost a Non-functional Requirement. Law II. Systems that Last Align Cost to Business. Law III. Architecting is a Series of Trade-offs. Law IV. Unobserved Systems Lead to Unknown Costs. Law V. Cost Aware Architectures Implement Cost Controls. Law VI. Cost Optimization is Incremental. Law VII. Unchallenged Success Leads to Assumptions.
77. IOT core AppSync API Gateway Messages Connection Time $2 per million $0.08 per million mins $0.25 per million mins $1 per million $0.08 per million mins $1 per million
78. Users Connection Time
79. Users Connection Time Revenue
80. Users Connection Time Revenue Engagement
81. Users Connection Time Revenue Engagement
82. www.gomomento.com/services/topics
84. IOT core AppSync API Gateway Messages Connection Time $2 per million $0.08 per million mins $0.25 per million mins $1 per million $0.08 per million mins $1 per million Momento - - Data Transfer $0.5 / GB EC2 rates EC2 rates EC2 rates
85. Simplify your architecture
86. Avoid unnecessary moving parts to your architecture.
87. ? ? Synchronous
88. ? ? Asynchronous
89. Every component in your architecture should serve a purpose and provide a ROI.
90. The most dangerous phrase in the language is "we've always done it this way". - Grace Hopper
91. Function URLs
92. Function URL
93. If you’re not using API Gateway features (e.g. Cognito authoriser, request models, direct integration)
94. Or, if you’re facing API Gateway limits (e.g. 29s timeout, no response streaming)
95. Have to write Lambdaliths
96. Have to write Lambdaliths (No per-endpoint metrics & alerts, no fi ne-grained access control, no per-endpoint auth)
97. Have to write Lambdaliths (No per-endpoint metrics & alerts, no fi ne-grained access control, no per-endpoint auth) (Large frameworks a ff ect cold start performance)
98. Best for public or internal APIs
100. Functionless
102. No Lambda = no cold starts
103. No Lambda = no Lambda costs
104. EventBridge Pipes
105. EventBridge Pipes
106. EventBridge Pipes Transform
107. Use Lambda functions to transform data, NOT transport data
108. OpenSearch
109. No-Code ETL OpenSearch
110. AppSync EventBridge OpenSearch
111. Step Functions EventBridge OpenSearch
112. Every component in your architecture should serve a purpose and provide a ROI.
113. Direct client access to AWS
117. Only allow access if hash key matches cognito sub
118. Not for the feint hearted…
119. When not to use this:
120. https://theburningmonk.com/2023/12/direct-access-for-frontend-apps-to-aws-services
121. 1. Billing alarms 2. Keeping logging cost under control 3. Right-sizing Lambda functions 4. Caching 5. Route53 TTL 6. Avoid CORS 7. Choosing the right service 8. Simplify your architecture 9. Function URLs 10. Functionless 11. Direct client access to AWS
122. productionreadyserverless.com Join 20+ AWS Heroes & Community Builders and 1000+ happy students in levelling up your serverless game.
123. Questions?