Lambda Alias don't use "General configuration"
When running the general lambda functions with a query, it works fine. However, the signal gets killed when running the same query with an alias version of the lambda functions. The "General configuration" isn't used for the alias, and the default time and memory are used. Is there a way to make the alias use the "General configuration", or is there a way to allocate more memory and time for the alias?
best regards, Markus Ekvall
I am not sure what you mean by:
- running function with a query
- signal gets killed
- general configuration
However, I will try to answer what I think you mean. An alias is just a pointer to a specific function version. Each function version has its own code and configuration. Once a version is created, it is immutable, i.e., it can't be changed. If you need different configuration for a version, make the configuration changes and then publish the new version. Then you can point the alias to the new version and the new config will be used.
Creating/using an alias for an S3 Object Lambda Access Point?asked a month ago
HTTP API - Invoke lambda aliasAccepted Answerasked 3 months ago
Random errors on lambda alias [INVALID_LAMBDA_CONFIGURATION]asked 4 years ago
is it possible that SQS Triggers to a Lambda Function Alias?Accepted Answerasked 3 months ago
ApiGateway REST not respecting Lambda aliasAccepted Answerasked 5 months ago
Lambda Alias with DynamoDB StreamsAccepted Answerasked 6 years ago
Make API Gateway resource point to Lambda AliasAccepted Answerasked 5 months ago
ApiGateway has 500 error when Lambda is updatingAccepted Answerasked 4 months ago
Lambda Alias don't use "General configuration"asked 9 days ago
How to assign a lambda function alias to LexV2asked 4 months ago