Lead Discovery Premium: Deploying the Spotfire BioTech Bundle may create AWS objects; however, errors exist or there is no Spotfire software

Details:

When you deploy the Revvity Signals BioTech Bundle you may experience any of the following issues:

a) The yaml file will create the AWS resources (EC2 instance and RDS database), but they will not include the Revvity Signals Software, Inc. or Spotfire software products.

b) A message that the EC2 instance is unreachable.

c) Resource handler returned message: "The image ID '' is not valid. The expected format is ami-xxxxxxxx or ami-xxxxxxxxxxxxxxxxx. (Service: AmazonEC2; Status Code: 400; Error Code: InvalidAMIID.Malformed; Request ID: <guid>; Proxy: null)" (RequestToken: <guid>1, HandlerErrorCode: GeneralServiceException)

The AWS resources (EC2 instance and RDS database) will be created, but they will not include the
Revvity Signals Software, Inc. or Spotfire software products.

Problem:

Each BioTech Bundle release includes a document titled similar to Revvity Signals Spotfire Lead Discovery Premium Biotech Bundle v1.5.1 Quick Start Guide.pdf (see attached below). The planning steps in this document are not always clear to all customers. For example, the document states to “contact Revvity Signals Software, Inc. via BiotechBundle@revvity.com”, but it does not state what to communicate about.

Solution:

Per the Quick Start Guide, before deploying you have to work with the team that monitors emails sent to BiotechBundle@revvity.com. This team needs to receive from you the ID of your AWS account and an identify of the AWS Region in which you plan to work. Then they will "whitelist" the AMI template, so that your execution of the yaml file will be able to access it and create an instance of your AWS resources (EC2 and database).

You should not proceed with a BioTech Bundle deployment until Revvity has let you know that a specific AMI ID and AMI Name are available to your AWS account in the region in which you plan to create AWS resources.