1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Using Lambda Layers won't help in this case because all of your code (including the layers) must be under 250 MB uncompressed. The Lambda service is showing that combined size in the error message.
You might consider using a container image instead as they have larger size limits.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Ah appreciate it, I was looking into that too. Do you have an idea of why the size issue is still being triggered or what areas I should check? I did a "Get Info" on an unzipped package straight from the S3 bucket that I upload the artifact to in the pipeline and it was only 213 MB.
From this distance it's impossible to say why the Lambda service is giving that error. The best way to find out is to contact our support team.