Skip to content

fix: update ElastiCache configuration in midaz - #28

Merged
guimoreirar merged 1 commit into
mainfrom
fix/helm-config
Mar 25, 2026
Merged

fix: update ElastiCache configuration in midaz#28
guimoreirar merged 1 commit into
mainfrom
fix/helm-config

Conversation

@guimoreirar

Copy link
Copy Markdown
Member
  • Bumped Midaz Helm chart version to 5.7.0 across application.yaml, full-stack.yaml, and helm.yaml.
  • Added ElastiCacheSecretArn and ElastiCacheKMSKeyArn parameters to helm.yaml for enhanced secret management.
  • Updated resource outputs in infrastructure.yaml and templates to include ElastiCache KMS Key ARN and Secret ARN.
  • Improved secret handling in the application by fetching ElastiCache auth token from Secrets Manager.

- Bumped Midaz Helm chart version to 5.7.0 across application.yaml, full-stack.yaml, and helm.yaml.
- Added ElastiCacheSecretArn and ElastiCacheKMSKeyArn parameters to helm.yaml for enhanced secret management.
- Updated resource outputs in infrastructure.yaml and templates to include ElastiCache KMS Key ARN and Secret ARN.
- Improved secret handling in the application by fetching ElastiCache auth token from Secrets Manager.
@guimoreirar guimoreirar self-assigned this Mar 25, 2026
@coderabbitai

coderabbitai Bot commented Mar 25, 2026

Copy link
Copy Markdown

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

This change upgrades the Midaz application version from 5.5.1 to 5.7.0 across multiple CloudFormation templates and adds support for ElastiCache authentication through Secrets Manager and KMS encryption. The infrastructure now exports ElastiCache secret and KMS key ARNs, which are passed through the Helm deployment stack. A Lambda deployer function is extended with IAM permissions to retrieve the ElastiCache password from Secrets Manager and decrypt it using the KMS key, then passes the credentials to the Kubernetes cluster. MongoDB connection parameters are added to the Helm values, and Redis TLS is enabled.

Sequence Diagram

sequenceDiagram
    participant CF as CloudFormation<br/>Infrastructure Stack
    participant SM as AWS Secrets<br/>Manager
    participant KMS as AWS KMS
    participant Lambda as Lambda<br/>Deployer
    participant K8s as Kubernetes<br/>Cluster
    participant Redis as Redis/<br/>ElastiCache

    CF->>CF: Output ElastiCacheSecretArn<br/>and ElastiCacheKMSKeyArn
    CF->>Lambda: Pass secret/KMS ARNs<br/>as env vars
    Lambda->>SM: get_elasticache_password()<br/>Fetch secret by ARN
    SM-->>Lambda: Return encrypted secret
    Lambda->>KMS: Decrypt using<br/>ElastiCacheKMSKeyArn
    KMS-->>Lambda: Return decrypted<br/>password
    Lambda->>K8s: Create secret with<br/>REDIS_PASSWORD
    K8s->>Redis: Connect using<br/>decrypted credentials
    Redis-->>K8s: Authentication successful
Loading
🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main changes: updating ElastiCache configuration and bumping the Midaz version to 5.7.0.
Description check ✅ Passed The description clearly relates to the changeset, detailing the version bump, new parameters added, updated outputs, and improved secret handling.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@lerian-studio

Copy link
Copy Markdown

Consider updating CHANGELOG.md to document this change. If this change doesn't need a changelog entry, add the skip-changelog label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants