EC2Deploy and the Cloud Tools Maven Plugin: Architecture, Goals, and Deployment Workflow

Originally published on 2010-03-10; fully revised and updated.

EC2Deploy and the Cloud Tools Maven plugin were introduced as an early automation path for deploying Java web applications to Amazon EC2. If you are reviewing older deployment approaches, this guide clarifies what was announced, how the parts work together, and what each Maven goal was designed to do.

The original announcement described EC2Deploy as a Groovy-based framework for deploying Java EE applications to EC2, made available through the Cloud Tools open source project.

What the release included

• The EC2Deploy framework
• Amazon Machine Images (AMIs) configured for Tomcat and EC2Deploy
• A Maven plugin that uses EC2Deploy to deploy a web application to EC2

How the Cloud Tools components fit together

Maven goals and when to use each one

The original post highlighted four plugin goals. They are shown below exactly as announced, with practical usage context.

mvn cloudtools:deploy
mvn cloudtools:redeploy
mvn cloudtools:jmeter
mvn cloudtools:stopCode language: CSS (css)

Typical workflow from deploy to teardown

flowchart TD
    A[Configure Maven plugin for app] --> B[Run mvn cloudtools:deploy]
    B --> C[EC2 instances are launched]
    C --> D[Application deployed to Tomcat]
    D --> E{Code changes needed}
    E -- yes --> F[Run mvn cloudtools:redeploy]
    E -- no --> G[Run mvn cloudtools:jmeter]
    F --> G
    G --> H[Run mvn cloudtools:stop]

Example change cycle commands

# First-time launch and deploy
mvn cloudtools:deploy

# Apply application updates
mvn cloudtools:redeploy

# Execute load test stage
mvn cloudtools:jmeter

# Stop compute resources when finished
mvn cloudtools:stopCode language: CSS (css)

Compatibility checks before using this approach today

• Confirm whether the project artifacts and source repositories are still accessible.
• Validate compatibility with your current Maven, JDK, and AWS account security model.
• Verify AMI availability and whether those images still meet your baseline hardening requirements.
• Review how credentials are handled before running deployment goals in CI/CD.
• Test in a non-production account first, especially instance lifecycle actions.

Best practices for evaluating legacy deployment tooling

• Treat historical plugin goals as a capability map, then verify each behavior in a controlled environment.
• Document a rollback and shutdown procedure before first use to avoid orphaned infrastructure.
• Prefer reproducible infrastructure definitions and modern CI/CD controls if rebuilding this pattern today.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.