Jump to content
Changes to the Jaspersoft community edition download ×

jrey

Members
  • Posts

    3
  • Joined

  • Last visited

jrey's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Thanks. It's worked....kind of. I can now see the RDS instances, but when I'm now receiveing this error Exception occurred during AWS data source recovery: /organizations/xxxxx. Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: 36b1db9e-5801-4d76-92ec-6f8981f23a27, AWS Error Code: InvalidVpcID.NotFound, AWS Error Message: The vpc ID 'vpc-0xxxx' does not exist It's the same error as was posted here: https://community.jaspersoft.com/questions/841370/vpc-does-not-exist-error-when-connecting-aws-source Any idea? Thanks again
  2. Hi, Did you ever get an answer for this issue? I just had the same problem occur. Thanks
  3. Hi, I recently launched an JS reporting instance via Cloudformation. All went well. Issue I hit was: Exception occurred during AWS data source recovery: /organizations/xxxxx. The AWS data source can not be recovered automatically, because your JasperReports Server and database instance are not located in the same VPC The instance launched in the Default VPC, which we don't use. Can I either updated the CF script or manually launch the JS instance into my preferred VPC/subnet? Thanks
×
×
  • Create New...