The serverless documentation indicates how to share the ids of an API Gateway, but the technique described there seems to work only for a new deployment. (In my case, following this technique created a 2nd empty API Gateway whose ids were shared, which was, unsurprisingly, not fulfilling my needs).
Here is how to do it for an existing deployment.
Continue reading “Serverless: How to share the ids of an existing API Gateway”Last April, I wrote a post about managing boto3 in deployed packages. (See Minimizing the size of lambdas by avoiding having boto3 and its stubs in the deployment package). This approach works when all dependencies can be set in the development section.
But, what about when dependencies are required in production? For example, we recently had to deploy a lambda that depends on awswrangler. So the technique suggested in the previous post did not work. Here I will cover a different approach that allows to remove boto3 from the package to be deployed in the example context. It is however less flexible and based on a specific technology: serverless.
Continue reading “Minimize the size of lambdas by deleting boto3 from the deployment package”If you are having problems with AWS lambdas exceeding the 250MB limit, here is a tip that might help.
Continue reading “Minimizing the size of lambdas by avoiding having boto3 and its stubs in the deployment package”I’ve been trying and trying to launch a Neo4j instance on the marketplace without success. It always gave me the nice “success” message, but when I went to the EC2 console: nothing!
I finally decided to do it the hard way: manually. First step: select an instance type. I immediately try to select the same low cost instance I had picked in the marketplace (m3.medium) and to my surprise that type wasn’t there.
Adding 1 + 1, I went back to the market place and tried with an instance type that still exists: m4.large… success!
So I don’t know who is to blame here, but here are my 2 questions to the internet: