Connecting to Amazon RDS/Redshift from TIBCO JasperReports® Server deployed on AWS

Use case

In this scenario, both TIBCO JasperReports^® Server and the database (either Redshift or one of database types available as Amazon RDS) are deployed in cloud using the same account and/or in the same VPC. For example, this will be the case if you deploy Jaspersoft^® for AWS BYOL Cluster and select the Automatic deployment:

The steps 

In this use case connecting to AWS data source connection is relatively simple. When selecting to create a new AWS data source, you should see the 'Use EC2 instance credentials option selected (if JasperReports Server was deployed using one of the CloudFormation templates). When both JasperReports Server and the database are deployed on AWS, the AWS data source in JasperReports Server is able to automatically discover and list the databases you are able to connect to:

In addition to discovering the database(s), AWS data source has a built in logic which will in most cases automatically configure the security rules on the database side to allow your JasperReports Server instance to connect to the selected database.

In the example above, you would use the database credentials which were picked when creating the Jaspersoft for AWS BYOL Cluster from a cloud formation template:

Also, if you are interested in using a non-default JDBC driver for AWS data source connection, please see the 'Changing the Default JDBC Driver for AWS Data Sources' section of the following chapter of TIBCO JasperReports Server Admin Guide:

See also: Connecting to Amazon RDS/Redshift from JasperReports Server deployed on premises