Altostra Docs

›Working with environments

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
  • CI/CD with Altostra CLI and Github Actions
  • Deploying a Project to Multiple Environments

How To

    Working with projects

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

    Working with environments

    • Manage an environment
    • Configure stacks 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

    • account
    • activity-log
    • api-key
    • build
    • config
    • console
    • deploy
    • docs
    • endpoints
    • environments
    • import
    • init
    • invalidate
    • login
    • logout
    • new
    • projects
    • push
    • deploy-cfn
    • deploy-sam
    • deploy-sls
    • stacks
    • sync
    • tasks
    • templates
    • versions
    • whoami

    Options

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

Errors And Solutions

  • Autnentication Required

Technical Reference

  • Environments
  • Stacks
  • Projects
  • Versions Repository
  • Log Shipping
  • Deployment Modes
  • Altostra Cloud Integration

Integrations

    CI/CD

    • CircleCI

    Git

    • Git integration
    • Connect a GitHub account
    • Connect a Bitbucket account

    Messaging

    • Connect a Slack workspace

    Security

    • Connect an Auth0 tenant

Configure stacks expiration for an environment

The Stacks Expiration policy enables you to automatically delete stale stacks that pass an expiration period and keep environments clean. The policy can be enabled per environment and applies to the stacks it contains.

The expiration period count starts from the last update made to the stacks, so as long as you're updating the stack, it keeps living.

Important: When you set an expiration period on an environment, all existing stacks in that environment are evaluated for expiration and deleted if they fit the criteria. Verify your intent and that you are working on the correct environment before you apply this setting.

Enable stacks expiration

  1. Go to Environments and click on the environment you want to enable stacks expiration for.
  2. Click on the Settings tab.
  3. Set the expiration period in Delete Stacks After.
  4. Click Save Changes

Disable stacks expiration

  1. Go to Environments and click on the environment you want to disable stacks expiration for.
  2. Click on the Settings tab.
  3. Set Delete Stacks After period to 0.
  4. Click Save Changes
← Manage an environmentGrant access to vendor services →
  • Enable stacks expiration
  • Disable stacks expiration

Ready to Get Started?

Get Started for Free
© 2022 Altostra, Inc.