You need a few things before you can install and run Jaspersoft Business Intelligence on Amazon Web Services:
|
•
|
An Amazon Web Services (AWS) account. |
If you already have an account, log into AWS.
To create an AWS account, go to the Amazon Web Services sign up page, select My Account > AWS Management Console, then click Create a new AWS account and follow the instructions.
|
|
If you have a personal Amazon.com account stored in your browser, AWS uses that account by default. You need to sign out of Amazon or, preferably, use a different browser to set up an AWS account separate from your personal account.
|
|
•
|
If you plan to use Jaspersoft for AWS BYOL, you'll need an annual subscription license. To purchase licenses for BYOL contact TIBCO Jaspersoft Sales |
|
|
The procedures in this section work for both TIBCO Jaspersoft Reporting and Analytics for AWS (Hourly and BYOL) for AWS and TIBCO Jaspersoft for AWS with MultiTenancy.
|
Required Permissions
Depending on how you use Jaspersoft for AWS, you'll need various permission sets.
Using our CloudFormation (CF) templates:
Using our CF templates typically requires some admin permissions. AWS permissions required to launch a new JasperReports Server instance include:
|
•
|
CloudFormation create stack and events |
|
•
|
Create and run EC2 instances |
|
•
|
Create EC2 security groups |
AWS permissions required to launch the template to create a new JasperReports Server role or user include:
|
•
|
Grant access to RDS, Redshift, and EC2 |
Connecting to the data source:
Permissions required to connect to the data source include:
|
•
|
Access to RDS and/or Redshift |
|
•
|
Permissions to create and modify the database security groups in each |
|
•
|
Permissions to create and modify EC2 security groups |
Please note that this document does not address connectivity to Amazon Elastic MapReduce (EMR).
