LogoLogo
  • Welcome to Release
  • Getting started
    • Quickstart
    • Create an account
    • Prepare to use Release
    • Create an application
      • Create custom application
      • Create from template
      • Servers vs runnables
    • Create an environment
  • Guides and examples
    • Domains and DNS
      • Manage domains
      • DNS and nameservers
        • Configure GoDaddy
        • Configure Cloudflare
        • Configure Namecheap
        • Other DNS hosts
      • Routing traffic
    • Example applications
      • Full stack voting app
      • Flask and RDS counter app
      • Static site with Gatsby
      • Golang with Postgres and Nginx
      • WordPress with MySQL
      • Spring and PostgreSQL
      • Terraform and Flask
      • OpenTelemetry demo
      • Load balancer with hostname
      • Static JavaScript service
      • SSH bastion access to services
      • ngrok and OAuth for private tunnels
      • Using OAuth Proxy
      • Hybrid Docker and static site
      • App Imports: Connecting two applications
      • Example library
    • Running instances
      • Cron jobs
      • Jobs
      • Using Helm charts
      • Using terminal
      • Viewing logs
      • Troubleshooting
        • ImagePullBackoff error
        • CrashLoopBackoff error
        • Exit codes
        • OOM: out of memory
    • Advanced guides
      • Containers guide
      • Application guide
      • Kubernetes guide
      • Create a cluster
      • Upgrade a cluster
      • Managing node groups
      • Patch node groups
      • Hostnames and rules
      • Serve traffic on multiple ports
      • Configure access to your K8s cluster
      • Designing for multiple environments
      • Microservices architecture
      • Monitoring your clusters
      • Performance tuning
      • Visibility and monitoring
      • Working with data
        • Container-based data
        • Seeding and migration
        • Cloud-provided data
        • Golden images
        • Third party
      • Pausing Instant Datasets
        • Application pausing schedules
        • Pause/resume environments
      • Infrastructure as code
        • Terraform
  • Reference documentation
    • Account settings
      • Account info
      • Managing users
      • Build settings
        • Build arguments
        • Build SSH keys
      • Add integrations
      • View clusters and cloud integrations
      • Add datasets
      • Environment handles
    • Workflows in Release
      • Stages of workflows
      • Serial deployments
      • Parallel deployments
      • Rolling deployments
      • Rainbow deployments
    • Networking
      • Network architecture (AWS)
      • Network architecture (GCP)
      • Ingresses
      • IP addresses
      • Cloud-provided services
      • Third-party services
    • Release environment versioning
    • Application settings
      • Application Template
        • Schema definition
      • Default environment variables
      • GitHub
      • Pull requests
      • GitOps
      • Just-in-time file mounts
      • Primary App Link
      • Create application FAQ
      • App-level build arguments
      • Parameters
      • Workspaces
    • End-to-end testing
    • Environment settings
      • Environment configuration
      • Environment variables
        • Environment variable mappings
        • Secrets vaults
        • Using Secrets with GitOps
        • Kubernetes Secrets as environment variables
        • Managing legacy Release Secrets
    • Environment expiration
    • Environment presets
    • Instant datasets on AWS
    • Instant datasets on GCP
    • Instant dataset tasks
      • Tonic Cloud
      • Tonic On-Premise
    • Cloud resources
    • Static service deployment
    • Helm
      • Getting started
      • Version-controlled Helm charts
      • Open-source charts
      • Building Docker images
      • Ingress and networking
      • Configuration
    • GitOps
    • The .release.yaml file
    • Docker Compose conversion support
    • Reference examples
      • Adding and removing services
      • Managing service resources
      • Adding database containers to the Application Template
      • Stock Off-The-Shelf Examples
    • Release API
      • Account Authentication
      • Environments API
        • Create
        • Get
        • Setup
        • Patch
      • User Authentication
      • Environment Presets API
        • Get Environment Preset List
        • Get Environment Preset
        • Put Environment Preset
  • Background concepts
    • How Release works
  • Frequently asked questions
    • Release FAQ
    • AWS FAQ
    • Docker FAQ
    • JavaScript FAQ
  • Integrations
    • Integrations overview
      • Artifactory integration
      • Cloud integrations (AWS)
        • AWS guides
        • Grant access to AWS resources
        • AWS how to increase EIP quota
        • Control your EKS fleet with systems manager
        • Managing STS access
        • AWS Permissions Boundaries
        • Private ECR Repositories
        • Using an Existing AWS VPC
        • Using an Existing EKS Cluster
      • Docker Hub integration
      • LaunchDarkly integration
      • Private registries
      • Slack integration
      • Cloud integrations (GCP)
        • GCP Permissions Boundary
      • Datadog Agent
      • Doppler Secrets Manager
      • AWS Secrets Management
    • Source control integrations
      • GitHub
        • Pull request comments
        • Pull request labels
        • GitHub deployments
        • GitHub statuses
        • Remove GitHub integration
      • Bitbucket
      • GitLab
    • Monitoring and logging add-ons
      • Datadog
      • New Relic
      • ELK (Elasticsearch, Logstash, and Kibana)
  • Release Delivery
    • Create new customer integration
    • Delivery guide
    • Release to customer account access controls
    • Delivery FAQs
  • Release Instant Datasets
    • Introduction
    • Quickstart
    • Security
      • AWS Instant Dataset security
    • FAQ
    • API
  • CLI
    • Getting started
    • Installation
    • Configuration
    • CLI usage example
    • Remote development environments
    • Command reference
      • release accounts
        • release accounts list
        • release accounts select
      • release ai
        • release ai chat
        • release ai config-delete
        • release ai config-init
        • release ai config-select
        • release ai config-upsert
      • release apps
        • release apps list
        • release apps select
      • release auth
        • release auth login
        • release auth logout
      • release builds
        • release builds create
      • release clusters
        • release clusters exec
        • release clusters kubeconfig
        • release clusters shell
      • release datasets
        • release datasets list
        • release datasets refresh
      • release deploys
        • release deploys create
        • release deploys list
      • release development
        • release development logs
        • release development start
      • release environments
        • release environments config-get
        • release environments config-set
        • release environments create
        • release environments delete
        • release environments get
        • release environments list
        • release environments vars-get
      • release gitops
        • release gitops init
        • release gitops validate
      • release instances
        • release instances exec
        • release instances logs
        • release instances terminal
  • Release.ai
    • Release.ai Introduction
    • Getting Started
    • Release.ai Templates
    • Template Configuration Basics
    • Using GPU Resources
    • Custom Workflows
    • Fine Tuning LlamaX
    • Serving Inference
Powered by GitBook
On this page
  • Supported cloud resources
  • How to add tags to AWS ECS tasks for Release environments
  • Using Terraform to add tags to AWS ECS tasks
  • How to configure ECS logs for Release
  • How to configure the terminal access in Release for AWS ECS tasks

Was this helpful?

  1. Reference documentation

Cloud resources

Tag AWS ECS tasks to use them with your Release environments

PreviousTonic On-PremiseNextStatic service deployment

Last updated 10 months ago

Was this helpful?

In this guide, we'll look at how you can create and use cloud-native resources like AWS ECS tasks or Lambdas with your Release environments.

While Release can create complex environments that run services as Docker containers or static files, cloud-native resources required by your Release environments are hosted by your cloud provider outside your Release clusters.

To add cloud resources to a Release environment, you'll add two tags to your resources using your cloud provider's console or API or by using Terraform.

Once tagged, these resources will show up on the environment page, below your instances. Release adds helpful buttons to interact with your cloud resources directly from your environment page.

Supported cloud resources

Release currently supports AWS ECS tasks as the first available cloud resource. If you use other cloud resources that you'd like us to support, .

How to add tags to AWS ECS tasks for Release environments

You can add AWS ECS tasks to your Release environments by adding two tags to your tasks in AWS.

Tag Key
Tag Value
Location in UI
Env variable

releasehub.com/app-name

(the app name)

Top of the environment page. In the screenshot below, the app name is terraform-runner-example.

releasehub.com/env-id

(the environment handle)

In the screenshot below, the environment handle is terraform-example-cloud-resources.

You can add tags to task definitions directly so that task containers inherit tags from the task definition or you can set the tags on running containers as shown below:

Using Terraform to add tags to AWS ECS tasks

When Release executes Terraform, your Terraform plans can access Release-specific environment variables. Use the RELEASE_APP_NAME and RELEASE_ENV_ID environment variables in our Terraform to create your tags.

variable "RELEASE_APP_NAME" {
  type        = string
  description = "Name of the Release application"
}

variable "RELEASE_ENV_ID" {
  type        = string
  description = "Unique identifier for the Release environment"
}

resource "aws_ecs_task_definition" "service" {
  family = "service"
  container_definitions = jsonencode([ ... ])
  tags = {
    "releasehub.com/app-name" = var.RELEASE_APP_NAME
    "releasehub.com/env-id" = var.RELEASE_ENV_ID
    ...
  }
}

How to configure ECS logs for Release

To view your ECS logs using the Release log viewer, configure your ECS tasks to use the awslogs log driver. This log driver sends logs to AWS CloudWatch, which Release then reads and adds to your environment page.

For logs to show up in Release, you need to set logDriver to awslogs, but you can set any values for awslogs-group or awslogs-stream-prefix.

The containerDefinitions section of your task definition should have a logConfiguration similar to the one below:

{
  "containerDefinitions": [
    {
      "logConfiguration": {
        "logDriver": "awslogs",
        "options": {
          "awslogs-group": "firelens-container",
          "awslogs-region": "us-west-2",
          "awslogs-create-group": "true",
          "awslogs-stream-prefix": "firelens"
        }
      }
    }
  ]
}

Click the Logs button next to your AWS ECS task on the environment page in Release to see the logs generated by the task.

When you click the Logs button, a new browser window will pop up showing the most recent logs.

How to configure the terminal access in Release for AWS ECS tasks

To open a terminal to an AWS ECS task, the following requirements must be met:

If your task is configured with ECS Exec and the required IAM permissions, you can click on the Terminal button to open a terminal to your task.

After clicking the Terminal button, a new browser window will open, showing terminal output and a command line.

If terminal access is not available for a task or if the task does not have ECS Exec enabled, the Terminal button will be grayed out in Release.

RELEASE_APP_NAME (see )

RELEASE_ENV_ID (see )

Follow the AWS documentation on to add these tags using the AWS console.

If you use , Terraform can create your AWS ECS tasks and set the required tags and their values when your environment is deployed.

See the AWS guide on . Your task execution IAM role needs the required permissions to create log groups and write to CloudWatch.

ECS Exec must be enabled for the task. See the AWS guide about .

The task's IAM role must have ECS Exec IAM permissions. See the AWS guide about .

We recommend reading the AWS documentation on to make sure you follow AWS recommended best practices.

tagging ECS resources
Terraform with Release's infrastructure runners
using the awslogs log driver for ECS tasks
turning on ECS Exec for your tasks and services
IAM permissions required for ECS Exec
using Amazon ECS Exec for debugging
default Release environment variables
default Release environment variables
let us know
Find the app name and environment ID on the environment page
Editing AWS ECS tags using AWS console
Logs button for an AWS ECS task in Release
Logs generated by an AWS ECS task in Release
Terminal button for an AWS ECS task in Release
Terminal to an AWS ECS task in Release