Datastores
In Nullstone, a Datastore is any infrastructure used to store and interact with data or files in a central location. It includes traditional databases such as Postgresql, MySQL, Redis, Elasticsearch, and Redshift. It also includes things like S3 buckets for file storage, TLS Authority for certificates, or Datadog for centralized logging and metrics. Check out the Datastores docs for more details and a list of datastores supported out of the box.
Connect to Datastore
From the application's Datastores tab, click to connect to a datastore.
From the dialog, select the datastore you want to connect to followed by the Capability used to make the connection. After creating the connection, make sure to re-launch your application for each environment to apply the change.
Capability
When a datastore is connected to an application, the Capability is the glue that wires them together. The Capability in the example is named Postgres Access. This capability will:
Establish secure network access
Your application is granted network access over the network firewalls to access the datastore over the correct port(s).
Inject Connection Information
The connection information is automatically injected into your application via environment variables so that your application can connect and interact with the datastore.
Create Database Credentials
For some datastores such as a Postgres cluster, your application will need a database in the cluster as well as a user to access it. Nullstone will create the database, create a username/password, and inject this info into your application.
TIP
Both datastore connection information and credentials are stored in a secrets manager and never leave your cloud account. This provides maximum security and prevents the mishandling of credentials; malicious or accidental.
Visit the Nullstone Registry to learn more about the specifics of each datastore.
Using the Datastore
To begin using your datastore in your application, utilize the environment variables that have been injected. If you look at the Configuration tab for your application, you will see a list of injected environment variables like the following:
Refer to documentation for your specific language or framework for how to read environment variables.