This section of the documentation describes key topics and ideas, and provides an overview of how Resoto works and its components.
📄️ Resource Cleanup
By default, Resoto Worker will not delete resources marked for deletion. Resources marked with | clean will stay this way without getting deleted. To enable cleanup, configure resotoworker.cleanup: true via config edit resoto.worker. See the Cleaning Resources tutorial for details on performing cleanup.
📄️ Resource Protection
Resoto has a concept of resource protection. The idea being that some resources in an account are important and should never be touched by Resoto even if a user, a plugin or an automated job has flagged them for cleanup.
By default all Resoto components communicate with each other via HTTPS using Transport Layer Security (TLS). The trust between components is established using a Pre-Shared-Key (PSK) that is used to derive a key which in turn is used to sign JWT tokens. Resoto Core is running a Public Key Infrastructure (PKI) including a Certificate Authority (CA). Upon start all components will request a certificate from the CA.
Resoto is able to create, update, and delete tags for resources that support tags.