FAQ

What is Acronym IQ for?

Acronym IQ helps you deploy containerized apps to AWS with practical defaults and lower operating cost. It also gives you a clean workflow for resource lifecycle management (create, scale, delete) and cost tracking.

Why should I use this app?

You can keep infrastructure in your own AWS account while avoiding repetitive setup work. The product is free to use for management and tracking, and you only pay when provisioning new resources.

Which AWS service is used for app deployment?

Deployments are built around Amazon ECS on AWS Fargate with ALB-based traffic routing.

Do you support AWS Kubernetes (EKS)?

Not at this time. The current platform path is ECS Fargate.

What programming languages are supported for my application?

This is a container-based solution, so language support is not restricted to a specific stack. If your application can be packaged and run as a Docker image, it should work with this platform.

Which app port is supported?

Current deployment templates support HTTP traffic on port 80.

How do I get started?
  1. An AWS account
  2. A GitHub account
  3. A domain (optional)
  4. An app that you can deploy as a container
What knowledge should I have to use this app?

Acronym IQ is intentionally opinionated around ECS Fargate deployment workflows. You should be comfortable with:

  • Docker container basics (building and running containerized apps)
  • AWS IAM basics (roles, trust policy, and permissions)
  • GitHub repository and GitHub Actions workflow basics
Why use IAM role-based access?

This platform is designed to reduce risk. It avoids storing long-term AWS access keys and instead uses role assumption with short-lived STS credentials.

Use a dedicated IAM role with least-privilege policies and an External ID condition in the trust policy. This helps prevent confused-deputy scenarios and limits blast radius.

In short: role-based access + limited policy + External ID + short TTL in this app = a much smaller blast radius.

I already have a GitHub repository. What should I do with the generated repo?

Treat the generated repository as the deployment-ready target repository because it is wired with the expected CI/CD and AWS access setup. In most cases, the best path is to merge or migrate your existing code into it.