You can - for example - use Humanitec to deploy Apps to your own Kubernetes clusters with a database provisioned in your own cloud instance and made accessible via your own DNS name.
Each of these individual elements is based on a Resource Definition in Humanitec. We are differentiating between two types of Resource Definitions: Dynamic Resources Definitions and Static Resource Definitions.
Dynamic Resource Definitions enable Humanitec to manage the full lifecycle of an External Resource. The External Resource can be created when needed and destroyed when no longer needed. A good example of a Dynamic Resource Definition is a database you use in one of your development or QA environments. Whenever a new development or QA environment is added, a new database is created and seeded as needed. The database can be removed when the Environment is deleted (i.e., no longer needed).
To work with Dynamic Resource Definitions, you firstly need to add a Resource Account (e.g., a GCP account, an AWS account).
You can add Dynamic Resources to your organization in Humanitec from the Organization Settings.
You first need to add the Resource Account and then the Dynamic Resource. You can also define for which Environment Type the specific Static Resource should be used.
Static Resource Definitions provide a way of using External Resources that are not managed by Humanitec. A good example of a Static Resource Definition is a production database that you are managing yourself. You can connect this database to your production environment using Environment Types and make sure that it is not used in any other environment than production.
You can add Static Resources to your organization in Humanitec from the Organization Settings.
You can define for which Environment Type the specific Static Resource should be used.