You should really be updating to a later version to be getting support. This version is almost 5 years old. Is there a specific reason it has not been updated? Can we assist in upgrading perhaps?
We also confirmed that we have not retired any of the older AMIs recently. Can you confirm the last time that you were using this successfully. Please feel free to reach out by email as well to pdutka@gatling.io.
From our end we haven’t changed anything since then. It’s possible that the older images that were working were automatically removed by AWS for security reasons.
I would say the best option would be an update but definitely with everything backed up and a strong review of the changelog as there are likely many breaking changes between Gatling 1.13.1 and 1.19.1 (current). Would you be open to a quick call so we can go over options and see how we can support?
We’ve just applied the solution you suggested: updating version.
Our instance has now been upgraded to Gatling Frontline Entreprise 1.19.2 version with JDK 11.
The corresponding AMIs have been found (now OpenJDK 11, among suggested available 11, 17, 21 versions), and injections via the AWS pool are OK.
Next steps: upgrade our code from Gatling 3.5 to latest 3.10, and Cassandra to v4.
Great to hear! Please let us know if there’s anything else you need. I can also connect you to the Enterprise support portal if you like for anything you may need in the future.