Follow the steps below to connect to Amazon RDS or Redshift. For Amazon Elastic MapReduce (EMR) see the Amazon EMR connection page. For non-Amazon data sources see the JDBC/JNDI connections section below.

Prerequisites

JasperReports Server must be running and you must be logged in as superuser.

Get help with these requirements here: Launching Jaspersoft BI for AWS.

Connect to Amazon RDS or Redshift

JasperReports Server can automatically discover and connect to Amazon Relational Database Server (RDS) and Amazon Redshift using the auto-connect feature.

To connect to Amazon RDS or Redshift:

Create > Data Source menu

Add Data Source dialog

JasperReports Server is able to detect your RDS and Redshift data sources. This is possible because the IAM Role associated with the EC2 instance is allowed to execute the actions "rds:Describe*" and "redshift:Describe*". It pre-populates the Database Name, Driver, and URL.

On the New Data Source page, You must enter the database username and password. For security reasons, Amazon does not store these credentials, and Jaspersoft cannot retrieve them.

The default database is automatically populated, but you may manually enter another if your RDS or Redshift instance has multiple databases.

New Data Source dialog

You should always test your connection. This button does much more than just testing:

This is possible because the IAM Role provides the instance with credentials like "rds:CreateDBSecurityGroup" and "redshift:AuthorizeClusterSecurityGroupIngress".

Test Connection dialog

Jaspersoft's metadata layer is called "Data Domains". Choose Create > Domain from the main menu and follow the wizard to build a domain.

Create > Domain menu

Choose Create > Ad Hoc View. Find your newly created domain and use the ad hoc environment to begin analyzing your data.

Create > Ad Hoc View menu

Refer to the Online Learning Portal for lots of details on creating domains, performing ad hoc analysis, and creating reports.

Additional Connection Possibilities

Under normal circumstances it's best to launch Jaspersoft BI on an EC2 instance with an associated IAM Role. This role provides EC2 credentials for your JRS instance.

If this option is not available for some reason, you can use AWS credentials instead. If you already have AWS Credentials, you can enter the Access Key and Secret Key.

If you don't have AWS Credentials, you can run the CloudFormation Template "jrs-create-user" to generate credentials.

http://www.jaspersoft.com/jrs-create-user?region=us-east-1

http://www.jaspersoft.com/jrs-create-user?region=us-west-2

http://www.jaspersoft.com/jrs-create-user?region=us-west-1

http://www.jaspersoft.com/jrs-create-user?region=eu-west-1

http://www.jaspersoft.com/jrs-create-user?region=ap-northeast-1

http://www.jaspersoft.com/jrs-create-user?region=sa-east-1

Entering AWS credentials

NOTE: When using JDBC for data source connections, you're responsible for managing the security groups to allow access from the Jaspersoft server to the data source.

Using JDBC / JNDI connections

When connecting to Amazon RDS or Redshift, it is best to use the AWS Data Source type to make configuration easier. If you prefer, you can use JDBC to connect to Amazon RDS or Redshift. To connect using JDBC, choose the JDBC Data Source type. Enter all connection information and test. Alternatively, you can choose JNDI Data Source and refer to a data source defined in Apache Tomcat.

Benefits of defining your own JDBC connections:

Benefits of using AWS Data Sources:

Connect to Amazon EMR

The JasperReports Server auto-connect feature is not supported for Amazon EMR. Connections to EMR need to be configured manually. Please see the Amazon EMR connection page for details: http://community.jaspersoft.com/jaspersoft-aws/connect-emr

Follow the steps above to connect to Amazon RDS or Redshift. For Amazon EMR see the Amazon EMR connection page. For non-Amazon data sources see the JDBC/JNDI connections section above.