Decisions Container Deployment: Environment Variables, File Path Errors, and AWS Logging in ECS

RichterBell

Hello,

I'm deploying Decisions in a containerized AWS ECS environment and running into a few issues:

• What are the required and recommended environment variables for a proper container setup?
• I'm seeing application log errors about invalid file paths, and the web UI loads without proper formatting or styles (missing CSS/icons).
• How should AWS logging be configured? Can I use IAM roles for logging, or do I need IAM user credentials?

Any guidance on resolving these issues and validating my configuration would be appreciated!

MalikBackman_Decisions

Hello,

Here’s some steps to resolve your Decisions container deployment issues in AWS ECS:

1. Environment Variables:

•  Please refer to our documentation for AWS ECS deployment details and YAML template with Environment Variables you can refer to. Deploying Containers on AWS  Decisions Environment Variables

• Remove unnecessary HTTPS-related environment variables if TLS is terminated at the load balancer.

2. File Path & UI Rendering Errors:

• The missing styles/icons are likely due to Decisions searching for CSS files in the wrong directory.
• Set up persistent storage for /opt/decisions/data and ensure environment variables point to the correct file paths.

3. AWS Logging Configuration:

• Decisions currently requires explicit IAM user credentials (Access Key ID and Secret Access Key) for AWS logging. IAM roles attached to containers are not supported.
• As a workaround, inject credentials at runtime using a vault or secret manager.

4. Additional Tip:

• Set both the portal base URL and force base URI to your HTTPS FQDN.

 

These steps should help stabilize your environment and resolve the underlying issues. If you would like to have access the latest Decisions HELM chart, please submit a support ticket, or email support@decisions.com. For critical support requests involving production, please email critical@decisions.com.