Overview

• Relational databases allow you to deploy a fully managed relational (SQL) database to your stack. You can choose from multiple database types, such as PostgreSQL, MySQL, MariaDB, Oracle Database or SQL Server.

• They are easy to set up, operate and scale. Capacity scaling, hardware & VM provisioning, database setup, patching, logging, backups and more are provided out of the box.

Under the hood

Under the hood, Stacktape uses AWS RDS service to provision databases.

3 engine categories, with different topology and scaling behavior are supported:

• Basic RDS engines: default, cheapest, single-node database with optional read replicas for higher performance and Multi AZ standby instances for increased resilience and fault tolerance. Basic engines include PostgreSQL, MySQL, MariaDB, Oracle Database or SQL Server. For more information refer to AWS web.
• Aurora engine: multi-node, highly available database cluster with increased durability and fault tolerance. Database requests are automatically balanced between available nodes resulting in higher performance. Supported engines are PostgreSQL, MySQL. For more information refer to AWS web.
• Aurora serverless engine: similar to Aurora engine, but with support for automatic usage-based scaling. Your database compute capacity can scale up and down(within configured boundaries) depending on the load. The database can be completely paused after configured time of inactivity, saving you the resources and money. Supported engines are PostgreSQL, MySQL. For more information refer to AWS web.

Security

Databases are always deployed within stack's VPC(Virtual Private Cloud) in your private network. You can configure database accessibility, i.e whether the database is accessible from the internet or only available to other resources in VPC.

Basic usage

• Relational databases require an active connection. To establish a connection, you typically need connection string.
• You can use connectTo property on the resource which is connecting to automatically inject required variables.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('database.password')
      engine:
        type: postgres
        properties:
          version: '16.2'
          primaryInstance:
            instanceSize: db.t3.micro

  apiServer:
    type: multi-container-workload
    properties:
      resources:
        cpu: 1
        memory: 1024
      containers:
        - name: api-container
          packaging:
            type: stacktape-image-buildpack
            properties:
              entryfilePath: src/main.ts
      connectTo:
        - myDatabase

Copy
import express from 'express';
import { Pool } from 'pg';

const pgPool = new Pool({
  connectionString: process.env.STP_MY_DATABASE_CONNECTION_STRING // env variable was automatically injected by Stacktape
});

const app = express();

app.get('/time', async (req, res) => {
  const result = await pgPool.query('SELECT NOW()');
  const time = result.rows[0];

  res.send(time);
});

app.listen(3000, () => {
  console.info('Server running on port 3000');
});

Database credentials

• Configures credentials for the database master user.
• You should not input these directly. The recommended way is using a secret.

Copy
resources:
  myRelationalDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserName: $File('.env').DB_USER_NAME # OPTIONAL
        masterUserPassword: $Secret('dbCredentials.password')
      engine:
        type: postgres
        properties:
          version: '16.2'
          port: 5432
          primaryInstance:
            instanceSize: db.t2.micro

Engine

Database engine determines the properties of your database, such as:

• database type (PostgreSQL, MySQL...),
• number of instances,
• high availability capabilities,
• redundancy,
• performance,
• scaling behavior,
• pricing etc.

Depending on the properties they provide, we group engine types into following groups:

• Rds Engine group - single node fully managed databases.
  • Supported engines:
    • postgres
    • mysql
    • mariadb
    • oracle-ee
    • oracle-se2
    • sqlserver-ee
    • sqlserver-ex
    • sqlserver-se
    • sqlserver-web
• Aurora Engine group - multi node highly available cluster with replicated storage.
  • Supported engines:
    • aurora-postgresql
    • aurora-mysql
• Aurora Serverless V2 Engine - serverless engine with replicated storage. Compute resources scale based on actual demand.
  • Supported engines:
    • aurora-postgresql-serverless-v2
    • aurora-mysql-serverless-v2
• Aurora Serverless V1 Engine - old generation serverless engine. We recommend using V2 instead.
  • Supported engines:
    • aurora-postgresql-serverless
    • aurora-mysql-serverless

Engine Version

Depending on the engine type, you must choose one of the available engine versions. Here is the list of available versions.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: postgres
        properties:
          version: '16.2'
          port: 5432
          primaryInstance:
            instanceSize: db.t3.micro

Available versions

Rds Engine

• To use the RDS engine, set the engine.type property to postgres, mysql, mariadb, oracle-ee, oracle-se2, sqlserver-ee, sqlserver-ex, sqlserver-se or sqlserver-web.
• RDS engine is the default, cheapest, single-node, fully managed database engine.
• RdsEngine is not highly available or fault-tolerant by default. However, Stacktape allows you to configure a standby instance in a different AZ (Availability zone) to increase resilience or add read replicas to increase read performance.

Instance size

• Instance size can be configured for both primary instance and read replicas.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: postgres
        properties:
          version: '16.2'
          port: 5432
          primaryInstance:
            instanceSize: db.t3.micro

MultiAz mode

• Multi AZ (Availability zone) mode can be configured for both primary instances and read replicas.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: postgres
        properties:
          version: '16.2'
          port: 5432
          primaryInstance:
            instanceSize: db.t2.micro
            multiAz: true

Read replicas

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: postgres
        properties:
          version: '16.2'
          port: 5432
          primaryInstance:
            instanceSize: db.t3.micro
          readReplicas:
            - instanceSize: db.t3.micro
            - instanceSize: db.t3.micro

Storage

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: postgres
        properties:
          version: '16.2'
          port: 5432
          primaryInstance:
            instanceSize: db.t3.micro
          storage:
            initialSize: 40
            maxSize: 400

Aurora Engine

• To use the Aurora engine, set the engine.type property to aurora-postgresql or aurora-mysql.
• Fully-managed, AWS-developed engine with clustering support, high-availability, increased durability & performance.
• Compute instances (nodes) run across multiple Availability Zones. Storage is automatically replicated 6-ways across 3 availability zones.
• Automatically load-balances read operations between nodes.
• Automatic failover - if a primary instance fails, one of the read replicas is elected as a new primary instance.
• To learn more about the AuroraEngine, refer to AWS Docs

Copy
resources:
  auroraSlsPostgres:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbSecret.password')
      engine:
        type: aurora-postgresql
        properties:
          version: '16.2'
          instances:
            - instanceSize: db.t3.medium
          port: 5432

Aurora Serverless V2 Engine

• To use the Aurora engine, set the engine.type property to aurora-postgresql-serverless-v2 or aurora-mysql-serverless-v2.
• Fully-managed AWS-developed engines (based on and compatible with either PostgreSQL or MySQL) with high-availability, increased durability & performance.
• Similar to Aurora Engines, but automatically scales based on usage. In comparison with Serverless V1, it is more responsive, more granular, and less disruptive when scaling.
• Scaling is done using ACUs (Aurora Compute units). Each ACU has ~2GB of RAM and 1 virtual CPU.
• Can scale to 0 ACUs (database is paused, and you don't pay anything).
• To learn more about Aurora Engines, refer to AWS Docs

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbSecret.password')
      engine:
        type: aurora-postgresql-serverless-v2
        properties:
          version: '16.4'
          maxCapacity: 8

Aurora Serverless Engine

• To use the Aurora engine, set the engine.type property to aurora-postgresql-serverless or aurora-mysql-serverless.
• Fully-managed AWS-developed engines (based on and compatible with either PostgreSQL or MySQL) with high-availability, increased durability performance.
• Similar to Aurora Engines, but automatically scales based on usage.
• Scaling is done using ACUs (Aurora Compute units). Each ACU has ~2GB of RAM and 1 virtual CPU.
• Can scale to 0 ACUs (database is paused, and you don't pay anything).
• To learn more about Aurora Engines, refer to AWS Docs

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbSecret.password')
      engine:
        type: aurora-postgresql-serverless
        properties:
          version: '13.12'
          minCapacity: 4
          maxCapacity: 8
          pauseAfterSeconds: 600

Backups

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: my_secret_password
      engine:
        type: postgres
        properties:
          version: '16.2'
          primaryInstance:
            instanceSize: db.t3.micro
      automatedBackupRetentionDays: 5

Logging

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: my_secret_password
      engine:
        type: postgres
        properties:
          version: '16.2'
          primaryInstance:
            instanceSize: db.t3.micro
      logging:
        retentionDays: 30
        engineSpecificOptions:
          log_connections: true

Forwarding logs

It is possible to forward logs to the third party services/databases. See page Forwarding logs for more information and examples.

Closing zombie connections

• Connections initiated by resources that are no longer running (for example stopped containers) can result in so called "zombie" connections.
• Modern, cloud-native architectures usually include horizontally scalable, ephemeral (short-lived) resources. When using these resources, you should have a strategy of dealing with zombie connections.

From container workloads

• For connections initiated from container workloads, you shouldn't forget to close the connection before your container exits. For example, ou can hook to a sigterm signal.

Copy
const connectionPool = createConnectionPool();

// remember to close the connection even on errors
process
  .on('uncaughtException', () => {
    connectionPool.close();
    process.exit(1);
  })
  .on('unhandledRejection', () => {
    connectionPool.close();
    process.exit(1);
  });

process.on('SIGTERM', () => {
  connectionPool.close();
  process.exit(0);
});

From batch jobs

• For connections initiated from batch jobs, you shouldn't forget to close the connection before your batch job finishes its job and your container exits.

Copy
const connectionPool = createConnectionPool();

connectionPool.connect();

// remember to close the connection even on errors
process
  .on('uncaughtException', () => {
    connectionPool.close();
    process.exit(1);
  })
  .on('unhandledRejection', () => {
    connectionPool.close();
    process.exit(1);
  });

doSomethingWithYourConnection();

connectionPool.close();

From lambda functions

• For connections initiated from lambda functions, you have 2 options:

Initialize and close the connection INSIDE the function handler.

• This way you can avoid having a zombie connection.
• This approach is not optimal, because creating a database connection can be slow (can take 10s to 100s of milliseconds).

  Copy
  import { Client } from 'pg';
  
  const handler = async (event, context) => {
    const pgClient = new Client({
      user: process.env.DB_USER,
      host: process.env.DB_HOST,
      database: process.env.DB_NAME,
      password: process.env.DB_PASSWORD,
      port: process.env.DB_PORT
    });
  
    await pgClient.connect();
  
    const result = await pgClient.query('SELECT NOW()');
    const time = result.rows[0];
  
    await pgClient.end();
  
    return { result: time };
  };
  
  export default handler;

Initialize connections OUTSIDE the function handler

• reuse it in every function invocation.

• This WILL result in zombie connections, when the container running your function stops (you can't hook to a lambda container SIGTERM signal to close it). In this case, you should do 2 things:

  • lower your database connection timeout (using a database parameter based on the database used):

    • for Postgres, set idle_in_transaction_session_timeout to something like 30min, tcp_keepalives_idle to 30min and tcp_keepalives_interval to 1min). This means inactive connections will be closed by the database.

  • if a database request fails because of a closed connection, you should re-create it within your application code.

    Copy
    import { Client } from 'pg';
    
    const pgClient = new Client({
      user: process.env.DB_USER,
      host: process.env.DB_HOST,
      database: process.env.DB_NAME,
      password: process.env.DB_PASSWORD,
      port: process.env.DB_PORT
    });
    
    (async () => {
      await pgClient.connect();
    })();
    
    const handler = async (event, context) => {
      const result = await pgClient.query('SELECT NOW()');
      const time = result.rows[0];
    
      return { result: time };
    };
    
    export default handler;

Accessibility

• You can configure which resources and hosts can access your cluster.
• To access your database, you always need to use your database user credentials.
• On top of that, Stacktape allows your to restrict the accessibility of your database to only certain resources or hosts.

Internet mode

• Default mode.
• Least restrictive. The database can be accessed from anywhere on the internet.

VPC mode

• The database can be accessed only from resources within the default VPC.
• Any function (provided it has joinDefaultVpc set to true), batch job or container workload or services within your stack can access the database.
• Additionally, IP addresses configured in whitelistedIps can also access the database (even from the internet). To disable this behavior, and enforce database isolation ONLY to the VPC, you can set the forceDisablePublicIp property.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: aurora-postgresql
        properties:
          version: '16.2'
          instances:
            - instanceSize: db.t3.medium
          port: 5432
      accessibility:
        accessibilityMode: vpc

  myFunction:
    type: function
    properties:
      packaging:
        type: stacktape-lambda-buildpack
        properties:
          entryfilePath: path/to/my/function.ts
      joinDefaultVpc: true

Scoping workloads in VPC mode

• Similar to vpc mode, but even more restrictive. In addition to resource being in the VPC, any host or resource trying to access your cluster must explicitly include the database in its connectTo list.
• Additionally, IP addresses configured in whitelistedIps can also access the database (even from the internet). To disable this behavior, and enforce database isolation, you can set the forceDisablePublicIp property.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: aurora-postgresql
        properties:
          version: '16.2'
          instances:
            - instanceSize: db.t3.medium
          port: 5432
      accessibility:
        accessibilityMode: scoping-workloads-in-vpc
  myFunction:
    type: function
    properties:
      packaging:
        type: stacktape-lambda-buildpack
        properties:
          entryfilePath: path/to/my/function.ts
      joinDefaultVpc: true
      connectTo:
        - myDatabase

Whitelisted IPs only mode

• The database can only be accessed from an IP addresses and CIDR blocks listed in the whitelistedIps list.

Copy
resources:
  myDatabase:
    type: relational-database
    properties:
      credentials:
        masterUserPassword: $Secret('dbPassword')
      engine:
        type: aurora-postgresql
        properties:
          version: '16.2'
          instances:
            - instanceSize: db.t3.medium
          port: 5432
      accessibility:
        accessibilityMode: whitelisted-ips-only
        whitelistedIps:
          - '147.25.33.12'

Referenceable parameters

Pricing

Pricing heavily depends on the engine used.

RDS engines:

• Database server instance
  • Price depends on the instance size and region. Allowed instances depend on the database type. Postgres instancesMySQL instances, Maria db instances, Oracle db, SQL server.
• Storage
  • $0.115 - $0.238 per GB-month
• Backups:
  • For automated backups with default retention setting (where you never store more than 100% of your total database storage), there is no additional charge.
  • Additional backup storage is $0.095 per GB-month.

Aurora engines:

• Database server instance
  • Price depends on the instance sizes and region. To see exact prices, refer to AWS pricing page
  • Price starts at $0.073 / hour.
• Storage
  • $0.10 - $0.19 per GB-month
• I/O Rate
  • $0.20 - $0.28 per 1 million read/write operations
• Backups
  • For automated backups with default retention setting (where you never store more than 100% of your total database storage), there is no additional charge.
  • Additional backup storage is $0.021 - $0.037 per GB-month.

Aurora serverless:

• ACUs (Aurora capacity units)
  • Each capacity unit has ~2GB of memory, ~1 Virtual CPU and corresponding network capabilities
  • 1 ACU costs $0.06 - $0.10 (depending on region)
  • Aurora Serverless databases can scale to 0 ACUs (with no costs)
• Storage, I/O Rate and Backups cost the same amount as Aurora non-serverless.

Data transfer charges (same for all engines).

• IN transfer: free
• OUT to VPC (subnet in the same Availability zone): free
• OUT to VPC (subnet in different Availability zone): $0.01 per GB ($0.02, because you are paying on both sides)
• OUT to Internet: first 1 GB free, then $0.09 -$0.15 per GB

FREE TIER (eligible for first 12 months)

• 750 Hours per month of db.t2.micro database usage (applicable DB engines)
• 20 GB of General Purpose (SSD) database storage \
• 20 GB of storage for database backups and DB Snapshots

API reference