If you access data stored in Amazon Web Services (AWS) data sources, the following settings control how JasperReports Server interacts with your Amazon environment:
|•||The AWS settings page enables you to change Security Group settings without restarting the server.|
|•||The AWS configuration file allows you to change the JDBC driver used with AWS data sources.|
For more information about AWS data sources, see AWS Data Sources.
To change AWS Security Group settings:
|1.||Log in as system administrator (superuser by default).|
|2.||Click Manage > Server Settings.|
The Log Settings page appears.
|3.||Click AWS Settings in the left-hand menu.|
The AWS Settings panel appears:
AWS Settings Page
|4.||Modify the following settings:|
We set up one AWS DB Security Group (using IP address) in each RDS region, per JasperReports Server instance. The security group allows connections from the specific JRS instance to the specified AWS database instance.
|•||Enable AWS Security Group Changes: This checkbox is generally left checked. When checked the JasperReports Server will use the instance credentials which it assumes from the IAM role to grant itself access to RDS and Redshift data services. For example, you stop your EC2 instance with JasperReports Server on Friday. You restart it on Monday, and the instance gets a new IP address. JasperReports Server then re-grants itself access to RDS. If you want to manage the security groups manually, un-check this box.|
|•||Security Group Name: When JasperReports Server creates security groups to support AWS data sources on this instance, it will use this name as the basis of the security group name. When the JasperReports Server instance is running on EC2, the EC2 instance ID will be appended. When running outside of EC2, you must make sure that name is unique between JasperReports Server instances (i.e. each one should have its own name), so that the IP addresses are properly granted access to the appropriate database instances.|
|•||Security Group Description: This text will be used for the description field next to security group or groups in the AWS console.|
|•||Security Group Ingress Public IP: Most users on EC2 should leave the this field empty. JasperReports Server determines the IP address automatically. If you are running JasperReports Server outside of EC2, then you must determine your IP address manually and enter it in this field. It is also possible with complex EC2 topology involving Virtual Private Clouds (VPCs) that you need to provide your IP address manually.|
|•||Suppress EC2 Credentials Warning: If your JasperReports Server instance was created with no IAM role, when you go to the data source wizard to add a data source with EC2 credentials there will be a warning message saying there is no proper role set. Checking this box suppresses the warning and disables the option.|
|5.||Click Change after each modification. The changes are effective immediately on the server.|
To change the JDBC driver used with AWS data sources:
|1.||Open the file …\WEB-INF\applicationContext-webapp.xml for editing.|
|2.||Locate the jdbcConnectionMapbean and the key of your AWS database type within it. Modify this key to specify a different JDBC driver. For example, the default driver for MySQL databases is set to the MariaDB driver:|
<entry key="mysql"> <util:map> ... <entry key="jdbcUrl" value="jdbc:mysql://$[dbHost]:$[dbPort]/$[dbName]"/> <entry key="jdbcDriverClass" value="org.mariadb.jdbc.Driver"/> ... </util:map>
|3.||Save the file and restart JasperReports Server.|