1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
2
Hi
Are you trying to change to the architecture to x86_64
at the same time as enabling SnapStart? Because that could cause your problem as the function has not migrated to x86_64
yet. Have you tried first migrating to x86_64
fully and then turning on SnapStart?
Contenus pertinents
- demandé il y a un an
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 3 mois
- AWS OFFICIELA mis à jour il y a un an
Was looking around for this migration, but from Cloud formation template there wasn't any solutions for doing that as a migration activity. Hence in the snapstart enabled lambda I have given the architecture of x86 and expected it to migrate it from arm while updating. Could you please suggest some ways of doing this without any downtime.
The above answer is working, but still it would require more than one deployment (one with x86 and then one with snapstart) looking for ways to make it in single deployment
Hi AGS I don't think it's possible to do that change in one deployment, not reliable anyway. The architecture must first change before you turn on SnapStart, and there is no way to tell CloudFormation to do the architecture update then the SnapStart update. CloudFormation will try and do the updates at the same time.