You'll need a few things before you can install and run Jaspersoft Business Intelligence on Amazon Web Services.
These prerequisites include:
| • | If you plan to use Jaspersoft for AWS BYOL, you'll need an annual subscription license. To purchase licenses for BYOL contact Jaspersoft Sales |
| The procedures in this section work for both Professional and Enterprise AMIs. |
Amazon Web Services Account
Before you can use Jaspersoft on Amazon Web Services, you need an AWS account.
| 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 separate from your personal account. |
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 |
| • | Grant access to RDS, Redshift, and EC2 |
AWS permissions required to launch the template to create a new JasperReports Server role include:
| • | Grant access to RDS, Redshift, and EC2 |
AWS permissions required to launch the template to create a new JasperReports Server 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). For more information on how to connect Jaspersoft for AWS to EMR, please see: http://community.jaspersoft.com/jaspersoft-aws/connect-emr.
Recommended Comments
There are no comments to display.