🚧AWS Lambda Module #260
timburke-hackit
started this conversation in
Firebreak April 24
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🌵What is the problem or issue we're trying to address?
There are a number of different approaches to terraforming Lambda functions in the repository, none of which are particularly elegant or user friendly.
🎯How is this affecting producers, consumers or platform engineers?
Producers
Need significant support from platform engineers to deploy lambda functions to platform, particularly around permissions but there are other ways this could be made a lot simpler
Platform Engineers
Have to manage multiple different implementations. Provide a lot of support when users want to create new lambda functions. Don't have an easy way of managing all of the lambdas deployed in a sensible way - if we wanted to move to containers, or rely more heavily on layers, change the default run time across platform; all of this would involve making changes in multiple places
📝What is the proposed task?
Develop or reuse an opinionated terraform module for deploying AWS Lambda functions to platform and migrate as many existing functions as possible to this module - or at least to make them child modules of this implementation
🤔How might this work be carried out?
Agree on an implementation - I have thought about abstracting the creation to a yaml which might be easier from producers to use for example?
Do the thing.
⌛How urgent is this work?
Pretty urgent, there's quite a lot of overhead maintaining the status quo
💪How much effort do you think this will take?
M
🛠️What skills are needed?
Terraform
AWS
📃Additional Info:
No response
Beta Was this translation helpful? Give feedback.
All reactions