DOCSEARCHbyAlgolia
Submit Docs

Stacktape Documentation

website·Indexed 33 days ago

https://docs.stacktape.com

Documentation for the Stacktape CLI and SDK, providing tools to compile configurations into CloudFormation templates, deploy and manage stacks on AWS, and handle compute resource packaging, logging, and local development.

Tokens
149.9K
Snippets
851
Records
1.1K
Agent score
57%

What's inside Stacktape

  1. Overview of Stacktape Deployment Scripts

    Deployment scripts allow you to execute custom logic as part of your infrastructure provisioning process. They are packaged as AWS Lambda functions and triggered during deployment or deletion. They are not executed during hot-swap deployments. Common use cases include seeding databases, running migrations, or performing smoke tests after a deployment.

  2. Overview of Bastion Servers (Jump Hosts)

    A bastion server (jump host) is a virtual machine that provides secure access to resources isolated within a private network (VPC), such as databases or Redis clusters that lack public endpoints. Stacktape uses AWS SSM Session Manager for connections, leveraging IAM permissions for authentication. This removes the need to expose ports or manage SSH keys.

  3. Overview of Web Application Firewalls (WAF)

    A Web Application Firewall (WAF) protects internet-facing applications from common web exploits, security compromises, and resource exhaustion by filtering and monitoring HTTP traffic based on defined rules. In Stacktape, WAFs can be attached to Application Load Balancers, Web Services, User Pools, and Content Delivery Networks (CDNs).

  4. Overview of Stacktape Private Services

    A private service is a continuously running container accessible only from within your stack. It is designed for backend services, private APIs, or internal applications that should not be exposed to the public internet. It is managed via AWS ECS (Fargate or EC2) and features automatic scaling, zero-downtime deployments, and self-healing capabilities.

  5. Overview of Stacktape Alarms

    Alarms allow you to monitor infrastructure metrics and trigger actions (like notifications) when a predefined threshold is crossed. Stacktape alarms are implemented using AWS CloudWatch Alarms. There are two ways to create them: Global alarms (via the Stacktape Console) and In-config alarms (via stacktape.yml).

  6. Overview of Stacktape deployment platform

    Stacktape is a deployment platform designed to simplify the process of deploying production-grade applications to a user's own AWS account. It abstracts the complexity of cloud infrastructure while allowing users to maintain full control of their AWS account, avoiding vendor lock-in and providing the ability to extend, override, or eject from the platform.

  7. Overview of Stacktape script types

    Stacktape allows you to define custom commands for tasks like building applications or running migrations. Scripts can be executed manually via script:run or automatically through lifecycle hooks (e.g., beforeDeploy). There are three primary script types:

    1. local-script: Executed on the machine running the Stacktape command.
    2. local-script-with-bastion-tunneling: Executed locally, but connections to resources in the connectTo list are tunneled through a bastion host to access VPC-only resources.
    3. bastion-script: Executed remotely on the bastion host itself, with logs streamed back to the local machine.

  8. Overview of Multi-Container workloads

    A multi-container workload is a serverless compute resource that runs one or more containers continuously. Unlike event-driven functions, these are designed for long-running applications and scale based on CPU and memory usage. They run within a VPC and can be exposed to the internet via HTTP API Gateways and Load Balancers. Stacktape uses AWS Elastic Container Service (ECS) for orchestration, supporting both Fargate (serverless) and EC2 instances.

  9. Overview of Stacktape Worker Services

    A worker service is a continuously running container that is not directly accessible from outside your stack. It is designed for background jobs, such as processing items from a message queue or handling asynchronous tasks.

    Key characteristics include:

    • Automatic Scaling: Scales based on CPU or memory usage.
    • Zero-Downtime Deployments: New versions are deployed without interrupting the service.
    • Managed Infrastructure: Runs on AWS ECS (via Fargate or EC2), providing self-healing capabilities where failed containers are automatically replaced.
    • Cost/Performance Trade-off: More cost-effective than Lambda for predictable, steady loads, but cannot scale to zero (minimum cost is approximately $8/month).

  10. Overview of Multi-Container workloads

    A multi-container workload is a serverless compute resource that runs one or more containers continuously. Unlike event-driven functions, these are designed for long-running applications and scale based on CPU and memory usage. They run within a VPC and can be exposed to the internet via HTTP API Gateways or Load Balancers. Stacktape uses AWS ECS (Fargate or EC2) for orchestration, providing self-healing and auto-scaling capabilities.

  11. Overview of Stacktape deployment platform

    Stacktape is a deployment platform designed to simplify the process of deploying production-grade applications to a user's own AWS account. It abstracts the complexity of cloud infrastructure to accelerate shipping speed and reduce costs compared to traditional PaaS solutions, while avoiding vendor lock-in by deploying directly to the user's AWS account.

  12. Overview of Web Application Firewalls (WAF)

    A Web Application Firewall (WAF) protects internet-facing applications from common web exploits, security compromises, and resource exhaustion by filtering and monitoring HTTP traffic based on rules. In Stacktape, WAFs can be used to block malicious traffic via managed rule groups, implement custom rules for specific threats, or use rate-based rules to prevent resource overloading.