Guidance Required on Adobe InDesign Server Licensing for New AWS EC2 Deployment

Guidance Required on Adobe InDesign Server Licensing for New AWS EC2 Deployment

Hello Adobe Community,

We are in the process of setting up a new AWS EC2 instance to install and run Adobe InDesign Server, and we would like your guidance to ensure that our licensing approach is fully compliant with Adobe’s recommended and supported practices.

To help us select the correct license model and define our operational process, we would appreciate clarification on the points below.

1. License Type Recommendation

We understand that Adobe InDesign Server licenses can be issued under the following categories:

• Individual licenses
• Site licenses
• Cloud deployment licenses
• Redistribution licenses

Do we have any enterprise licenses as well?

Request:
Could you please advise which license type is most appropriate for the following use case:

• InDesign Server running on a dedicated AWS EC2 instance
• Used for automated document generation
• No end‑user interaction
• Instance is long‑lived (not auto‑scaled)

If multiple options are suitable, we would appreciate guidance on the recommended model for cloud‑hosted server deployments.

2. Machine‑Based / Machine ID Binding Clarification

We understand from Adobe documentation that InDesign Server licenses are specific to a machine ID.

Request:
Could you please clarify:

• What “machine ID” means at a conceptual level (without needing internal implementation details)
• Whether the license is considered bound to:
  • The operating system installation
  • The virtual machine instance
  • Or the underlying host identity as seen by Adobe

3. Re‑installation, Crash, or Recovery Scenarios

We would like to understand the correct and supported procedure for the following scenarios:

• Operating system reinstallation on the same EC2 instance
• EC2 instance crash and recovery
• EC2 instance replacement (new instance created)

Request:
For each of the above cases, could you confirm:

• Whether re‑activation or re‑serialization is required
• The recommended steps to re‑enable the license
• Whether Adobe support involvement is required in any of these scenarios

4. Environment Separation (DEV / SPRINT / UAT / PROD)

Our organization maintains multiple environments:

• Development (DEV)
• Sprint / Integration
• User Acceptance Testing (UAT)
• Production (PROD)

Request:
Could you please clarify:

• Whether a single InDesign Server license can be shared across multiple environments if they run on different machines
• Whether each environment requires a separate license and activation
• Any best practices Adobe recommends for environment separation in server deployments

5. EC2‑Specific Considerations

Since the deployment is on AWS EC2, we would also appreciate guidance on:

• Any known considerations or recommendations from Adobe for cloud VM deployments
• Best practices to avoid unintended license invalidation
• Whether static instances are preferred over frequently re‑created instances

Our goal is to ensure that:

• The license is used only on the intended EC2 instance
• The deployment is fully compliant with Adobe licensing terms
• Operational risks related to re‑activation are minimized

Thank you in advance for your guidance. Please let us know if you require any additional information from my side.

Kind regards,
Girish Jangame
Senior Product Software Engineer
Pune, India