Skip to content
LMA

Stack Updates & Upgrades

Stack Updates & Upgrades

Section titled “Stack Updates & Upgrades”

Table of Contents

Section titled “Table of Contents”

Overview

Section titled “Overview”

This guide covers how to update an existing LMA stack to a new version or change its configuration. Stack updates allow you to adopt new features, apply bug fixes, and adjust parameters without deleting and recreating the stack.

Update Steps

Section titled “Update Steps”
Section titled “Using LMA CLI (Recommended)”

The simplest way to update your stack:

Terminal window
# Update from the latest published template for your region
lma-cli deploy --stack-name LMA --wait


# Or update from local code changes
lma-cli deploy --stack-name LMA --from-code . --wait

The CLI auto-selects the correct template for your region and streams deployment events in real-time.

Using AWS Console

Section titled “Using AWS Console”
  1. Log into the AWS Console.
  2. Navigate to CloudFormation and select your LMA stack.
  3. Choose Update and then Replace current template.
  4. Enter the template URL for your region (see table below).
  5. Review and adjust parameters as needed.
  6. Click Next twice, check the IAM acknowledgement boxes, and click Update stack.

Template URLs by Region

Section titled “Template URLs by Region”
RegionTemplate URL
US East (N. Virginia)https://s3.us-east-1.amazonaws.com/aws-ml-blog-us-east-1/artifacts/lma/lma-main.yaml
US West (Oregon)https://s3.us-west-2.amazonaws.com/aws-ml-blog-us-west-2/artifacts/lma/lma-main.yaml
AP Southeast (Sydney)https://s3.ap-southeast-2.amazonaws.com/aws-bigdata-blog-replica-ap-southeast-2/artifacts/lma/lma-main.yaml

Building from Source

Section titled “Building from Source”

If you are building from source, use lma-cli deploy --from-code . to build and deploy in one step, or use lma-cli publish to build first and then deploy with the resulting template URL.

Terminal window
# Build and deploy in one step
lma-cli deploy --stack-name LMA --from-code . --wait


# Or publish first, then deploy separately
lma-cli publish --source-dir . --region us-east-1
lma-cli deploy --stack-name LMA --template-url <url-from-publish-output> --wait

The legacy publish.sh script is also still available — use its template URL output with lma-cli deploy --template-url <url>.

What Is Preserved Across Updates

Section titled “What Is Preserved Across Updates”

The following data and configuration are preserved when you update or upgrade your stack:

  • Custom prompt templates stored in DynamoDB
  • User data including meetings, transcripts, and recordings
  • Cognito user accounts (v0.2.0 and later)
  • Installed MCP servers

What May Change

Section titled “What May Change”

The following may be modified during an update:

  • Default prompt templates
  • Infrastructure resources (Lambda functions, ECS tasks, etc.)
  • Lambda function code

Version Migration Notes

Section titled “Version Migration Notes”

v0.3.0

Section titled “v0.3.0”

This is a major consolidation release. The following features and integrations have been removed:

  • QnABot
  • Amazon Lex
  • Bedrock Agent
  • Amazon Q Business
  • OpenSearch
  • Chrome browser extension
  • Healthcare domain support
  • Claude 3.x models (Claude 4+ only)

Only the Strands Bedrock agent remains as the meeting assistant service. If you relied on any of the removed features, they will no longer be available after upgrading to v0.3.0.

v0.2.0

Section titled “v0.2.0”

Breaking change: The Cognito user pool is deleted and recreated during this upgrade. All existing users must re-register after the update completes. See User-Based Access Control for details on user management.

Section titled “Related Documentation”