Hi, I am currently in the process of migrating our server from an existing Bitnami based deployment (quite an old version) to the officially supported install in AWS using the latest Discourse release. This new install has an external Elasticache and RDS instance and also will use S3 for backups an…

Maybe I am missing something but, why are you establishing new buckets? A new backup bucket with appropriate lifecycle rules seems ok to do but if your existing Discourse instance is using S3 upload bucket you will have some problems.

2 reasons we need new buckets: I am not 100% sure the migration from Bitnami will work without a hitch so we don’t want to impact any existing data incase we need to abort the migration We changed our bucket naming so thought it easier to have 2 brand new buckets for this Point 1 is the one that …

I missed that you were going to copy over the data from the old buckets. Took a look at AWS, looks to be straight forward. If it were me I would not muck with changing buckets before moving to AWS or a new server elsewhere. [imagem] stevejr: to the officially supported install in AWS using the …

[imagem] stevejr: I am not 100% sure the migration from Bitnami will work without a hitch This is something you can easily test without affecting production. Personally I would do everything I could to avoid doing these two things at the same moment. see if you can avoid moving buckets at …

[imagem] stevejr: This new install has an external Elasticache and RDS instance and I am very curious about how doing this type of install is a value added proposition. From the numerous posts around unsupported installs it seems more trouble than benefit unless folks are doing them for lear…

[imagem] philh: am very curious about how doing this type of install is a value added proposition. From the numerous posts around unsupported installs Such a setup might be an unsupported install from a Discourse point of view, but from the perspective of an enterprise IT organisation, RDS a…

Thanks for that. So familiarity and perhaps existing infrastructure.

Thanks for the input on this question. As mentioned by @RGJ , our enterprise infra uses external services for things like cache, database etc hence the Elasticache and RDS. It means we can have full backup and redundancy for these services and also help with security controls. This is an official/s…

[imagem] stevejr: sounds like we should first update our bucket names for the existing install and then perform the move to the new server I wouldn’t do that [imagem] RGJ: do it after the migration from Bitnami Since if you do it prior to the migration and things go south, you’ll have…

Ah sorry Richard, misread you bullet point on the S3 name changes :+1: So, better plan is to backup the existing buckets, do the migration, make the bucket name change. Thanks for all your help with this so far. And yes, the “B” word does make people clam up so good to be moving away from it …

Migrando para um novo servidor com um novo DB e novos buckets S3 para backup e uploads

Suporte Instalação

supermathie (Michael Brown) 19 Fevereiro , 2026 21:47 19

esclarecimento: se a versão principal corresponder ao que estamos enviando

Tópico		Respostas	Vistas
Migration to a Self-Hosted solution from Kubernetes Self-hosting install , migrations-tooling	2	354	16 Outubro , 2025
How to migrate Discourse from one server to another with the same DNS name Self-hosting	11	3545	12 Abril , 2024
Transfer from bitnami to normal discourse Self-hosting	7	2869	7 Junho , 2019
Help restoring - system hung at midnight Self-hosting	26	2583	13 Junho , 2022
Error upgrading 2.3.5 to 2.4.2 Self-hosting unsupported-install	16	1111	4 Maio , 2020

Migrando para um novo servidor com um novo DB e novos buckets S3 para backup e uploads

Related topics