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.
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:
Why do we get the success message even though it doesn’t work?
Why are unsupported instance types offered in the market place?