Frequently Asked Questions

Gitmoxi is a unified continuous deployment (CD) product designed to simplify and enhance deployment processes on AWS, particularly for ECS and Lambda. With Gitmoxi, you can track, manage, and optimize deployments across various AWS regions using strategies like blue-green, rolling, and canary deployments.

Gitmoxi enhances deployment management across AWS ECS and Lambda by providing teams with powerful features to track, control, and optimize their deployment workflows:

• Version-Controlled Deployment Artifacts: Gitmoxi versions every deployment artifact at each change, creating a reliable history of modifications and ensuring rollbacks are straightforward and accurate. By making Git the single source of truth, Gitmoxi empowers teams with complete traceability of all changes, helping them maintain deployment consistency and prevent accidental drift.
• Support for Various Deployment Strategies: With built-in support for Canary, Blue/Green, and Rolling deployments, Gitmoxi makes it easy to manage both simple and complex deployment needs across AWS regions. Whether fine-tuning a gradual rollout or executing a quick environment switch, teams can adopt the best deployment strategy for each situation without additional complexity or manual steps.
• Detailed Error Logging and Actionable Insights: Gitmoxi offers comprehensive error logs that go beyond basic data to provide actionable insights, helping teams diagnose issues quickly. These logs include timestamps, error contexts, and metadata to support faster issue resolution, reducing both response times and downtime impact.
• Active Alarm Monitoring and Auto-Rollback Mechanisms: Gitmoxi actively monitors critical alarms throughout deployments, ensuring that any detected issues can trigger an immediate rollback to the last stable state. This proactive approach allows teams to mitigate problems before they affect users, maintaining stability and confidence in the deployment process.

Gitmoxi supports multiple deployment strategies, including blue-green, rolling, and canary deployments. These options provide flexible control over release processes, making it easier to minimize downtime and safely deploy changes across environments.

• Blue-Green Deployments: In a blue-green deployment, two identical environments (blue and green) are maintained. At any time, one environment (e.g., blue) serves live traffic while the other (green) is idle. When a new version is ready, it is deployed to the idle environment. Once validated, traffic is switched over to the new version, allowing for quick rollbacks if issues arise.
• Rolling Deployments: Rolling deployments gradually replace instances of the previous version of an application with the new version. This strategy updates a few instances at a time, which helps ensure that some parts of the application are always available. It minimizes downtime and allows for real-time monitoring of the new version as it is rolled out.
• Canary Deployments: Canary deployments involve gradually releasing a new version of an application to a small percentage of total traffic or users, rather than rolling it out to the entire user base at once. This strategy allows teams to monitor the performance of the new version and gather feedback from a limited set of requests, reducing the risk associated with a full-scale release.

Yes, Gitmoxi is built to efficiently manage deployments for both ECS (Elastic Container Service) and AWS Lambda, making it possible to deploy containerized applications and serverless functions from a unified platform. Gitmoxi has a deep understanding of AWS ECS and Lambda configurations, including critical components like Task Definitions, Service Definitions, and Event Source Mappings, which are integral to each deployment’s success. This insight into AWS’s architecture allows Gitmoxi to streamline deployments across complex, multi-service environments.

Absolutely! Gitmoxi integrates seamlessly with popular Infrastructure as Code (IaC) tools like Terraform and AWS CDK, enabling smooth integration into existing workflows and ensuring consistent, repeatable infrastructure provisioning alongside deployments. Gitmoxi goes a step further by directly absorbing configurations from the output files generated by these IaC tools. For instance, when you create a security group using Terraform, you can provide the Terraform output that includes the new security group’s ARN. Gitmoxi will parse this output automatically and update the security group ARN within the ECS Service definition. This capability helps maintain accurate, synchronized configurations across your infrastructure and deployment processes, reducing manual intervention and potential configuration errors.

Yes, Gitmoxi is designed to simplify multi-region deployments, making it easy to deploy applications simultaneously across multiple AWS regions. This feature is especially valuable for enhancing application availability and ensuring low-latency performance for users in different geographic areas. Gitmoxi allows you to manage region-specific configurations and dependencies directly within its interface, giving you control over how deployments are synchronized across regions.

Absolutely, Gitmoxi is equipped with comprehensive real-time tracking features that keep your team fully informed at every stage of the deployment process. With clear visibility into deployment statuses across services and regions, you can monitor successes and failures, receiving immediate alerts for any issues that arise. This continuous visibility helps teams stay informed throughout each deployment, making it easier to address potential problems on the spot.

Gitmoxi also provides detailed, actionable error logs that capture essential context, including timestamps and metadata, for swift issue diagnosis. These insights enable teams to respond proactively, quickly mitigate disruptions, and ensure a seamless experience for end users.

Gitmoxi offers both a user-friendly UI and a powerful CLI, allowing users to choose their preferred method for tracking deployments. The UI provides an overview of all active deployments, displaying real-time status updates and timestamps for any errors encountered. Each deployment is directly linked to its corresponding Git commit, making it simple to trace changes back to specific code updates. This dual approach ensures that users have flexible options for monitoring their deployments, whether they prefer visual interfaces or command-line tools.

Gitmoxi is designed to manage deployment errors with advanced diagnostics and quick recovery mechanisms. It offers detailed error logging and actionable insights that go beyond basic error messages, providing in-depth information like timestamps, error contexts, and relevant metadata. This helps teams pinpoint the root cause of issues swiftly, reducing response time and downtime impact.

Gitmoxi also includes active alarm monitoring and automatic rollback mechanisms to ensure stability. It actively monitors critical alarms during each deployment, and if an issue arises, Gitmoxi can immediately trigger a rollback to the last stable version. This proactive approach minimizes user impact by addressing problems before they escalate, empowering teams to deploy with confidence and maintain a seamless user experience.

Gitmoxi integrates seamlessly with CI/CD workflows and the GitOps model to streamline deployments:

• Push-Based Deployment: Gitmoxi allows for a push-based deployment approach, where the CI/CD pipeline triggers Gitmoxi to initiate a deployment using deployment artifacts stored in a specific Git repository. This ensures that deployments are based on the most recent code changes, enhancing deployment efficiency.
• GitOps Support: When enabled, Gitmoxi actively monitors the designated Git repository for updates. Upon detecting any changes, it automatically triggers a new deployment. This GitOps model fosters a more automated and responsive deployment process, allowing teams to maintain continuous integration and delivery seamlessly.

GitMoxi is not just another deployment tool — it’s a product designed to optimize and enhance deployment workflows through intelligent service-specific deployments, improve deployment consistency, and ensure rapid iteration. While traditional CI/CD pipelines focus on the end-to-end software delivery lifecycle, GitMoxi specializes in deployment automation, complementing your pipeline by making the deployment stage smarter and more efficient.

Key Differences and Benefits:

• Intelligent Service-Specific Deployments: GitMoxi intelligently handles deployments for the specific AWS service, ensuring precise updates tailored to your application needs.
• Detailed Logs for Troubleshooting: GitMoxi provides comprehensive, step-by-step logs to simplify debugging and give you unparalleled visibility into deployment processes.
• Centralized Configuration Management: By utilizing a single source of truth for configuration, GitMoxi ensures consistency across environments without additional manual effort.
• IaC Integration: GitMoxi easily incorporates outputs from your Infrastructure-as-Code (IaC) tools, streamlining deployments by automatically injecting these configurations into the pipeline.
• Flexible and Scalable: Adapts to diverse deployment strategies and scales effortlessly across environments and services.

Gitmoxi supports both pull and push-based event sources for AWS Lambda.

• Push-based sources are event sources that trigger AWS Lambda functions directly in response to specific events, typically involving HTTP requests. Gitmoxi supports Application Load Balancer (ALB) and API Gateway push based event sources.
• Pull-based sources refer to event sources that trigger AWS Lambda functions in response to new data or events, where Lambda polls the source for events rather than being directly invoked by them. These encompass all event sources listed in the Event Source Mapping documentation, including services like Amazon SQS, DynamoDB Streams, and Kinesis Data Streams. This variety allows for flexible and scalable event-driven architectures.

Gitmoxi supports both EC2 and Fargate compute type on Amazon ECS, offering a seamless deployment experience for containerized applications. While Fargate simplifies management by abstracting infrastructure, it does not support advanced deployment strategies like blue-green and canary deployments, which are essential for minimizing downtime. Additionally, rollbacks in Fargate can be slow, and its error logs often lack the detailed, actionable insights necessary for effective troubleshooting.

Gitmoxi overcomes these challenges by enabling support for all deployment strategies and providing comprehensive error logging, ensuring a smoother deployment process and rapid issue resolution. This empowers teams to maintain high application reliability and improve user satisfaction.

Please visit the pricing page to learn more about the various pricing tiers for Gitmoxi.