Use case description
The first deployment of TIBCO JasperReports® Server on AWS instance for the account using a cloud formation template failed for no clear reason (for the reference, a full list of pre-configured instances of JasperReports® Server on AWS can be found on this page). No AWS instance was successfully deployed for this account previously.
Probable cause and solution
The most common reason for a pre-configured cloud formation instance to fail is that the Sofrware Terms were not accepted for the account. The Software Terms are found on a separate page than the actual templates, which is why this step is easy to overlook. To accept the Software Terms, log into your AWS account and follow this link:
Select the type of an instance you need (Hourly or BYOL) and follow the corresponding link. On the next page you should see an option to accept the terms if you have not done so yet.
WARNING: once accepted DO NOT launch directly using 1-Click or the EC2 Console, but use a link to one of the cloud formation templates from this page instead.
The Software Terms tab should look something (except for you it should be active if not accepted yet):
Recommended Comments
There are no comments to display.