To create a secure network connection between Heroku applications running in a Private Space and an AWS VPC, the appropriate feature to use is Private Space Peering. This feature allows for the connection of a Heroku Private Space directly to an AWS VPC, providing a secure and efficient way to link the two environments.
Heroku does not control where add-on providers store data. This is because Heroku operates in various regions but does not manage the physical storage of data for third-party add-ons. Since these add-ons are managed by external providers, they have their own data residency policies and practices, which are outside the control of Heroku. Therefore, the enforcement of data privacy and GDPR compliance will heavily rely on the third-party providers' compliance measures.
Changing the type of dynos to standard-2x is the recommended approach. The issue at hand is that the worker dynos are running out of memory, which means they require more resources for the complex image processing tasks. Upgrading to a higher capacity dyno, such as standard-2x, provides additional memory and CPU, which should address the memory constraints without necessarily needing to refactor the application to run on multiple dynos or move to a different infrastructure.