AWS FreePBX® Change Log
Check your current version by running | smartupgrade show-versions | via SSH.
You can update your instance anytime by running | smartupgrade --auto | BUT TO BE SURE TO CREATE A MACHINE IMAGE BACKUP BEFOREHAND!
Release Icon Key: [!]=Patches/Bug Fixes | [!!!]=Security Patches/Breaking Changes
- Debian OS v12.13
- FreePBX® Framework v17.0.28
- Asterisk v21.12.1
- Patch tmux-on-login to fix a looping bug when attempting to sudo su a second time within tmux
- Patch cloud-init and all of SmartUpgrade for IMDSv2
- Note: While IMDSv2 support has been added, IMDSv2-only mode has not yet been explicitly set as the launch default in our AMI. You must manually select IMDSv2-only mode at Instance launch to enable it. By the end of 2026, we will enable IMDSv2-only mode by default. If you are using IMDS in your deployment stack, you will need to update those scripts and applications to use IMDSv2 by that time. In the meantime, Instances will continue to launch with both v1 and v2 support. If you don’t know what any of this means, it likely doesn’t apply to you, as the Instance Meta Data Service is used internally to programmatically retrieve important information about the instance and AWS environment. We use it for things like setting the default GUI admin password to the Instance ID at launch.
- Debian OS v12.12
- FreePBX® Framework v17.0.24
- Asterisk v21.11.0
- Patch to fix automatic partition enlargement on EC2 Volume Resize
- Debian OS v12.8
- FreePBX® Framework v17.0.19.21
- Asterisk v21.5.0
- https://twm.tips/v17announcement
- AWS FREEPBX NOW RUNS ON DEBIAN!
- CHAN_SIP IS NO LONGER AVAILABLE AT ALL!
- THIS VERSION IS END OF LIFE AND ALL CUSTOMERS SHOULD MIGRATE TO v17 AS SOON AS POSSIBLE!
- CentOS v7.8.2003
- FreePBX® Framework v16.0.40.4
- Asterisk v16.30.0
- https://twm.tips/v17announcement