I am currently using amazon RDS for a postgres instance to store immich's data. With the upcoming breaking changes after 1.90, is it possible to still be using RDS and if so, what changes will I need to make?
#Support for Amazon RDS (pgvecto-rs)
surreal thunder
daring parcelBOT
:wave: Hey @surreal thunder,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich 
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Typesense: You can't fix this. Just wait until we get rid of it. Sorry.
Checklist
- :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :blue_square: I have read applicable release notes.
- :blue_square: I have reviewed the FAQs for known issues.
- :blue_square: I have reviewed Github for known issues.
- :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :blue_square: I have tried an incognito window, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
uncut helm
I'm using my own local Postgres instance ( I'm a DB guy and have other projects and things happening in Pg and other databases ). I've never had any issues with Immich due to using my own instance ... with the exception that I had to run some "create extension" commands manually, but this was easy enough to do. I wouldn't expect any issues with using RDS Postgres.
However ... I'm curious: why? RDS has got to be the most expensive way of running Postgres around.
frosty hearth
RDS only supports specific extensions, which does not include the one we are using, so unfortunately I don't think there is any way to continue running it there.