Amazon Web Services (AWS) provide computation and data storage on demand in the cloud. We partner with Amazon to deliver business intelligence solutions based on AWS.
JasperReports Server supports two of the AWS database services as data sources for reporting:
| • | Amazon Relational Database Service (RDS) |
| • | Amazon Redshift data warehouse |
JasperReports Server can access either of these services when you define a data source with the correct configuration information and credentials. The AWS data source wizard uses the AWS credentials you provide to discover RDS and Redshift data sources. Then it uses those credentials to properly configure security groups to maintain the connection between JasperReports Server and the AWS data source, even when the IP address changes. You can access AWS data sources from both stand-alone server instances that you maintain on your own computers and virtual server instances that you run on Amazon’s Elastic Compute Cloud (EC2). For more information, see https://www.jaspersoft.com/cloud.
To create an AWS Data Source:
| 1. | Log into JasperReports Server as an administrator. |
| 2. | Click View > Repository, expand the folder tree, and right-click a folder to select Add Resource > Data Source from the context menu. Alternatively, you can select Create > Data Source from the main menu on any page and specify a folder location later. If you installed the sample data, the suggested folder is Data Sources. The New Data Source page appears. |
| 3. | In the Type field, select AWS Data Source. The information on the page changes to reflect what’s needed to define an AWS data source. |
| Selecting AWS Credentials |
|  |
| 4. | Under AWS Settings, specify your Amazon credentials in one of the following ways: |
| • | If your JasperReports Server is running in Amazon’s EC2 service, and it has the proper instance role assigned, the server will detect this and automatically use your EC2 credentials. Using the EC2 instance credentials requires that the role was properly set up and assigned when the instance was created. If you're using the EC2 service, we strongly recommend that you use the EC2 credentials. |
| • | If your JasperReports Server is not running on Amazon’s EC2, enter the AWS credentials associated with the RDS or Redshift service. If you don’t have AWS keys, click Generate credentials, then look for them on the Outputs tab for your Stack on the Amazon console: |
| AWS Access and Secret Keys |
| |
| 5. | Under Select an AWS Data Source, specify the connection details of the AWS data source that you want to connect to: |
| a. | Select your AWS Region from the drop-down. |
| b. | Click the Find My AWS Data Sources button. |
The AWS data source queries your environment and displays your available data sources, as shown in the figure below.
| c. | Select your data source. |
| d. | Enter your user name, password, and database name. |
The AWS data source queries your environment and adds the appropriate driver and URL.
| Select an AWS Data Source Section |
| |
| 6. | When you’ve entered all the information, click Test Connection. |
If your connection is successful, a message appears at the top of the screen. Sometimes the process takes a few minutes. In that case you'll see an alert. Try the test again after one or two minutes. The test performs the following actions:
| • | Validate the user name and password. |
| • | Create a database security group. |
| • | Add the IP address of your JasperReports Server instance to the security group to authorize ingress to the data service (RDS or Redshift). |
If you want to control details of the security group name or specify the IP address manually because you have a complex VPC Topology, see Configuring Amazon Web Services. You can also change the default JDBC driver through the configuration.
| 7. | Click Save. The new data source appears in the repository. |
Recommended Comments
There are no comments to display.