The AWS settings page enables you to change Security Group settings without restarting the server. This page is accessible only if you're logged in as superuser.
To reach the AWS Settings page:
| 1. | Click Manage > Server Settings. The Log Settings page appears. |
| 2. | Click AWS Settings in the left menu. The AWS Settings page appears. |
| AWS Settings Page |
| |
On this page you can enable AWS Security Group changes for the following settings:
| • | Security Group Name |
| • | Security Group Description |
| • | Security Group Ingress Public IP |
| • | Suppress EC2 Credentials Warning |
| | There is one AWS DB Security Group (using IP address) in each RDS region, per JasperReports Server instance. The security group allows connections from the JRS instance to the specified AWS database instance. |
Enable AWS Security Group Changes: This check box is generally left checked to allow JasperReports Server to use the instance credentials it assumes from the IAM role or the AccessSecret keys provided in AWS Datasource to grant itself access to RDS and Redshift data services. For example, let's say you stop your EC2 instance with JasperReports Server on Friday. When you restart it on Monday, 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: JasperReports Server uses this security group name when creating security groups to support AWS data sources. The EC2 instance ID is appended to this name when your JasperReports Server instance is running on EC2. When running outside of EC2, make sure the security group name is unique for each instance of JasperReports Server to ensure that IP addresses are properly granted access to the appropriate database instances.
Security Group Description: This text is the description of the security group or groups in the AWS console.
Security Group Ingress Public IP: Most users on EC2 should leave the this field empty. On EC2, JasperReports Server determines the IP address automatically. If you're running JasperReports Server outside of EC2, determine your IP address and enter it in this field. It is also possible with complex EC2 topology involving Virtual Private Clouds (VPCs) that you'll 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 you'll be warned that no proper role is set. Checking this box suppresses the warning and disables the option.
Recommended Comments
There are no comments to display.