YaK User Documentation
YaK Landing PageVisit dbi-services.comContact us
YaK Release 2.1
YaK Release 2.1
  • Welcome
  • Introduction
    • YaK Core
    • YaK Components
    • Terms and definitions
  • User interface
    • Dashboard
    • Infrastructures
    • Servers
    • Components
    • Jobs
    • Configuration
    • Administration
  • YaK Demo
  • Versioning & Compatibility matrix
  • Release Notes
    • YaK components types
      • PostgreSQL
      • Oracle
  • Installation
    • System requirements
    • Install YaK Core
      • Install YaK on your own K8S cluster
      • Install YaK on Rancher Desktop
      • Uninstall Yak
  • YaK step-by-step usage
  • Configuration
    • Secrets
    • Templates
    • Provider shapes
    • Provider images
    • Artifact providers
  • Manage infrastructures
    • Declare infrastructures
    • Attach Secrets
    • Detach Secrets
  • Manage Servers
    • Declare servers
      • Basics
      • Storage
      • Attach secrets
    • Edit server configuration
    • Deploy servers
    • Destroy servers
    • Delete servers
    • Start / Stop servers
  • Manage Components
    • Artifacts requirements
    • Component types
      • PostgreSQL
        • Description
        • Pre-requisites
        • Component references
          • PostgreSQL 2.0.0
            • Standalone deployment variables
            • HA deployment variables
      • Oracle
        • Description
        • Pre-requisites
        • Component references
          • Oracle 2.0.0
            • Standalone variables
  • Use cases
    • On-Premises
    • AWS
    • Azure
    • OCI
  • Appendix
    • Create SSH Keys with PuTTYgen
    • Roles
Powered by GitBook
On this page
  1. Configuration

Provider shapes

PreviousTemplatesNextProvider images

Last updated 2 months ago

The menu allows you to define the instance types that you want to be made available to the YaK for your future deployments.

Provider shapes are types of instance available on the provider side; they are defined by cloud service providers and offer a wide variety of combinations depending on customer requirements (performance, availability, cost, etc.) and server capacity (CPU, memory, storage and networking).

Operating costs and performance can vary considerably from one shape to another and from one cloud provider to another. Make sure you carefully select the shapes that best meet your needs and budget.

Examples of shapes per provider:

  • AWS "t3.xlarge"

    • Low-cost burstable general purpose instance

    • 4vCPUS, 16GiB of memory, 5Gbps of Network burst bandwidth

  • Azure "Standard_B2ms"

    • General purpose instance

    • 2vCPUS, 8GiB of memory

  • OCI "VM.Standard3.Flex"

    • 2 OCPUS, 8GiB of memory

See Cloud providers documentation for more details:

  • AWS:

  • Azure:

  • OCI:

Add shapes

YaK already comes with a predefined list of the most common provider shapes, it's up to the user to add more shapes if needed

To do so:

  • Navigate to Configuration -> Provider shapes in the menu

  • Select the cloud provider you want to declare a new shape to, by selecting the appropriate tab

  • Click "Declare"

  • Fill-out the form with the requested information

The shape definition must exist at your cloud provider and the shape name must match your provider's shape name.

https://aws.amazon.com/ec2/instance-types/
List of VM size families by type
https://azure.microsoft.com/en-us/pricing/details/virtual-machines/series/#pricing
https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm
provider shapes