Skip to content

Service Resources#

All data applications on Ametnes Cloud are generally referred to as a service resource. They share some commonalities.

  1. Any service resource can be reached by a secure endpoint. The endpoint is secured by tls.
  2. Every service resource will be accessible via some kind of authentication challenge.
  3. Each service has a set of configuration parameters that you can use to tailor your service deployment to your needs. An example of this is SSO authentication.
  4. Each service resource has system capacity requirements. These include memory, cpu, storage and the number of replicas.


A complete endpoint consists of a hostname and a port. Each service type has different endpoint requirements. For example, a HarperDB instance requires three endpoints, while a Postgres instance requires only one endpoint.


Username and Password#

All services created using Ametnes Cloud will be protected by some form of authentication. This will either be a basic username and password challenge or an API key.


Some services have integrations into authentication gateways such as Okta or AzureAD. Where these are available, you are able to configure the servie to provide integration into the authentication gateways.


Before you create a data service, you need to establish the capacity requirements for your service. Each service has different resource requirements so be sure to specify capaciry requirements for your data service.


All services can be configured to suit your needs. Each service has a set of configuration parameters that can be used to customise that specific resource.


All data services created using Ametnes Cloud will have tls encryption enabled by default. Some data services allow you to disable tls encryption. However, it is recommended that you do not do this. When mTls is enabled, you'll be supplied with the certificates which you must download and save on your computer in order to use to connect to your data service.