Thanks for your reply!
Since the CloudFormation templates were written by Bitnami and not AWS, and since the behavior I described takes place in any deployment of the stack, even without making any changes to it, I believe I will have better chances figuring this out with Bitnami.
It is true that Bitnami does provide a template for its deployment in AWS CloudFormation, and indeed the deployment of the different resources seems to work correctly. Once the resources have been deployed, AWS offers the possibility to use Change Sets to manage updates on those deployed resources.
The computation of what changes are required to be applied is performed by the platform itself, and as such, AWS should be able to determine if you are experiencing an incorrect behaviour and the underlying issue. Should AWS point that the error is inherent from the template provided by Bitnami, we will be more than happy to initiate the process for reviewing this solution.
Do you know of any other Bitnami support resources I can refer to or, perhaps, if it is possible to escalate this to someone at Bitnami?
This is the right place to raise questions related to the majority of our different types of stacks (Installers, VMs, Cloud Images & MultiTier deployments). If necessary, we will escalate the corresponding thread.
Jose Antonio Carmona
Was my answer helpful? Click on