Releases: aws-samples/aws-scalable-big-blue-button-example
Releases · aws-samples/aws-scalable-big-blue-button-example
3.0.2
3.0.1
3.0.0
Upgrade Notes:
- the Big Blue Button version defaults now to 2.3.0. if you need to stay on 2.2.X please make sure to alter the BBB version parameter to xenial-22 and the Ubuntu version parameter to xenial-16.04.
- the deployment now defaults to "Serverless" deployments for ECS and Aurora. this will optimize costs especially in small/test environments. switching from instanced to serverless will resetup the database means you will have to restore the DB from a backup afterwards or start fresh with testing. to prevent this, ensure you're not just using defaults for your environment.
- now you need to have docker locally installed when planning a scalable deployment. this is due our approach to mirror the needed images to ensure availability when using scaling of the frontend and Scalelite LBs
Fixed
- #75: Serverless Aurora did not deploy due a missing !IF condition for the parametergroup
- #81: Single deployments failed due a missing condition
Changed
- #84: Default Big Blue Button version defaults to 2.3.0 (stable since 7 Days)
- #77: SES automation is now optional and can be overwritten by using the parameter
- #77: an existing ACM Certificate ARN can be added to reuse an existing or imported SSL certificate
- #76: Cloudformation can now validate ACM certificates natively, so we do not need the custom resource anymore.
- #85: we're now utilizing IAM Roles when mounting the Shared Storage. Also the Storage now limits access to the APs utilizing these Roles.
- #86: adding ECR as container registry to prevent failures due dockerhub limitations
- Versions of Greenlight and Scalelite are now current and reflect the new default Big Blue Button Version
- Fargate deployment version of Scalelite was broken, this is now fixed.
2.3.0
Upgrade Notes:
- Upgrading the Amazon Aurora Postgres Engine version via Amazon Cloudformation is not supported. Please refer to the official upgrade documentation if you have a already running environment using an older engine version to proceed with the upgrade before reruning the Cloudformation deployment with default parameters.
Alternatively you can set the parameter 'BBBDBEngineVersion' to the version you're currently using to prevent Amazon Cloudformation to try to upgrade.
Added
- #62: HTTP to HTTPS rewrites implemented
- #66: Added parameters to set the Big Blue Button application server root volume size
Changed
- #63: default Amazon Aurora Postgres engine version updated to 12.4
- Updated Architectural Diagram for Serverless
2.2.0
Fixes
- #38: fixing deployment into Regions with < 3 AZs
Added
- #34: Optional deployment onto Aurora Serverless (Postgresql) for cost optimization especially with smaller deployments of a scalable solution
- #15: Optional deployment into a predefined/existing VPC containing at least Subnets in 2 AZs
- Parameter "BBBNumberOfAZs" to define how many AZs the deployment should utilize (=> also defines how many Subnets are used/created)
Changed
- #44: Added section to prerequisites to ensure users are heads-up for common issues incl. missing service linked roles
- Big Blue Button Version String via parameter to make the version to be adjusted easily for upcoming Big Blue Button releases
- Application and Turn Server Ubuntu Versions are now parameterized. This ensures OS Versions can allign with the Big Blue Button Version used (e.g. for 2.3-dev deployments of BBB)
- Parameter BBBVPCcidr renamed into BBBVPCs
- BBBVPCs and BBB*Subnets parameters now take cidr blocks to create VPCs (and subnets) or IDs to reuse existing VPCs (and its subnets )
- Turn server Instance OS defaults to Ubuntu 20.04 LTS
- Removal of dedicated Contributing.md
- Restructure/Simplification of Conditions
- Cleanup of unused conditions and parameters.
2.1.1
2.1.0
Upgrade Notes:
- Be sure to backup persistent storages if you use the single instance deplyoment mode before running the upgrade via setup.sh. The setup is backward compatible and will only adjust log group namings and streams. If you need or want to keep the already collected logs, export the data to S3 before running the upgrade process.
Changed
- #35: Log groups names are now more dynamic, allowing multble stacks in the same account as well as make it easier to locate related logs in Cloudwatch. Also the LogGroup strucure is simlified for better usability.
- bump cfn-certificate-provider version to 0.2.5
Fixes
- minor adjustments at the readme.md
- #42: Bump cfn-ses-provider version to 0.6.5
1.0.1
2.0.0
Added
- Optional AWS Fargate deployment instead of EC2 based deployment for Greenlight and scalelite #19
- containerized initialization for the EFS storage structure setup via Cloudformation, elimination of EC2 instance mount/mkdir hack #16
Changed
- Default parameter settings for Desired ECS Instances have been lowered to 1. Max ECS Instance default settings have been lowered to 3.
- Default Volume Size for Recordings EBS Storage have been lowered to 50G
- as the Instance Deployment for Turn and Application instances is pretty much settled, we shifted the cfn-signal command to the end of the bootstrap. this should ensure BBB is accessable pretty closely after the cloudformation deployment is done.
- instance sizes for ECS Worker Instances and Application servers have been lowerd to the minimum needed to start a small test deployment to optize cost
- vCPU and memory limits of the ECS tasks have been simplified and are now set only on task level.