Altostra Docs

    ›Technical Reference

    Getting Started

    • Welcome to Altostra
    • Connect your accounts
    • Install the developer tools
    • Log in from the CLI

    Tutorials

    • Create a Static Website
    • Create a Scalable Webhook
    • Create a Simple API Project
    • Try Altostra without connecting cloud accounts
    • CI/CD with Altostra CLI and Github Actions

    How To

      Working with projects

      • Create a new project
      • Deploy a project
      • Manage a project

      Working with environments

      • Manage an environment
      • Configure instances expiration for an environment

      Working with the Editor

      • Grant access to vendor services
      • Use the Parameter Store
      • Use a custom CloudFormation resource
      • Attach a custom policy to a Function
      • Connect a Function to VPC
      • Add filter policy to SNS subscription

      Organization account settings

      • Set General Settings
      • Connect a Git account
      • Connect Cloud Accounts
      • Manage log aggregation accounts

    CLI

    • Altostra CLI
    • Commands

      • templates
      • new
      • init
      • push
      • deploy
      • sls-deploy
      • sync
      • invalidate
      • domains
      • console
      • environments
      • images
      • instances
      • build
      • config
      • import
      • projects
      • tasks
      • activity-log
      • login
      • logout
      • account
      • whoami
      • api-key
      • docs

      Options

      • --debug
      • --verbose
      • Scripting options
    • Configuration files

    Errors And Solutions

    • Autnentication Required

    Technical Reference

    • Environments
    • Playground Environment
    • Instances
    • Project image
    • Image Repository
    • Log Shipping
    • Deployment Modes
    • Altostra Cloud Integration

    Integrations

      CI/CD

      • CircleCI

    Environments

    In Altostra, environments are targets for deployments. Any time you create a new instance for a project, you must specify the environment to which you wish to deploy it.

    The environment itself consists of the following attributes:

    • A name, for easy of use.
    • A location, the specifies the account and region to deploy to.
    • Zero or more configuration sets, that provide the configuration values for instances.
    • Optional policies that determine certain aspects and additional capabilities that extend each instance.

    Environments provide an easy way for users to regard the collection of attributes above by name, freeing the users from having to remember these details for every deployment.

    Configuration values

    Configuration values are sets of key-value pairs that allow you to provide configuration to instances, that may required it, in each environment.

    By using configuration sets, you can share and reuse configuration values between instances. You can provide different configuration values in each environment to the separate instances of the same project.

    ← Autnentication RequiredPlayground Environment →
    • Configuration values
    © 2021 Altostra, Inc.