Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
Page 1 of 25
Jupiter on the AWS Cloud Quick Start Reference Deployment
June 2018
Cognizant Technology Solutions
AWS Quick Start Reference Team
Contents
Overview ................................................................................................................................. 2
Jupiter on AWS .................................................................................................................. 3
Jupiter Project Creation ..................................................................................................... 4
Costs and Licenses .............................................................................................................. 5
Jupiter Architecture ............................................................................................................... 5
Infrastructure Architecture .................................................................................................... 6
Prerequisites .......................................................................................................................... 7
Specialized Knowledge ....................................................................................................... 7
Technical Requirements ..................................................................................................... 7
Deployment Options ..............................................................................................................8
Deployment Steps ..................................................................................................................8
Step 1. Prepare Your AWS Account ....................................................................................8
Step 2. Obtain a Jupiter License ........................................................................................8
Step 3. Launch the Quick Start .......................................................................................... 9
Step 4. Retrieve License Key and Login Credentials ....................................................... 15
Step 5. Test the Deployment ............................................................................................ 17
FAQ....................................................................................................................................... 23
Git Repository ...................................................................................................................... 24
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 2 of 25
Additional Resources ........................................................................................................... 24
Document Revisions ............................................................................................................ 24
This Quick Start deployment guide was created by Amazon Web Services (AWS) in
collaboration with Cognizant Technology Solutions, an AWS Premier Consulting Partner.
Quick Starts are automated reference deployments that use AWS CloudFormation
templates to launch, configure, and run the AWS compute, network, storage, and other
services required to deploy a specific workload on AWS.
Overview
This Quick Start reference deployment guide provides step-by-step instructions for
deploying Jupiter on the AWS Cloud.
Jupiter is Cognizant’s continuous data testing accelerator and a component of Cognizant’s
Adaptive Data Foundation offering. Jupiter enables data test automation and quality
engineering at scale by aligning to a DevOps delivery mode. Jupiter uses innovative test
practices for data projects and enables better collaboration among teams through
Acceptance Test-Driven Development (ATDD).
Jupiter is for users who want to run quality-assurance tests on data stored in the AWS
Cloud in Amazon Simple Storage Service (Amazon S3), Amazon Redshift, or Apache Hive
on Amazon EMR, among other options.
Spend less time writing tests with easy-to-use libraries that connect, run queries, and
validate data across heterogeneous systems. You can also integrate Jupiter with defect-
management tools like Jira or HP Application Lifecycle Management (ALM) to enable
traceability.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 3 of 25
Figure 1 gives an overview of Jupiter capabilities.
Figure 1: Jupiter capabilities
Jupiter on AWS
This Quick Start creates an AWS Elastic Beanstalk environment with an Amazon Elastic
Compute Cloud (Amazon EC2) Linux instance and Apache Tomcat. The Jupiter application
is deployed in this environment. Another Amazon EMR instance will be created for data
processing and validation.
This Quick Start automates the design, setup, and configuration of hardware and software
to implement automated data testing in much less time than the traditional approach.
Once you’ve deployed Jupiter on the AWS Cloud, you can:
Create and configure a Jupiter project to provide for continuous data testing on the
AWS Cloud. For example:
– Configure databases and sources that Jupiter will test
– Configure environments to be used to run tests on
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 4 of 25
– Add users to the project, so that they can view and trigger Jupiter jobs
– Configure source code management (SCM) repositories for deploying test
scripts to configured environments.
Run data validation tests on an EMR instance.
View a dashboard that provides information on the most recent run, as well as historical
successes and failures of the specific feature file.
Try out a set of sample template test projects with sample datasets for Amazon S3 and
Apache Hive.
Jupiter Project Creation
Figure 2 summarizes the software development lifecycle of a Jupiter project.
Figure 2: Overview of Jupiter software development lifecycle
Before you upload a Jupiter project to an SCM repository like Git for use in the AWS Cloud,
you have to create the project locally. This process involves writing the feature file. The
feature file contains the testing scenarios and description of the steps in Gherkin, the
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 5 of 25
language that Cucumber uses to define test cases. The Jupiter libraries are then plugged
into the associated Step Definition methods as applicable.
Costs and Licenses
You are responsible for the cost of the AWS services used while running this Quick Start
reference deployment. There is no additional cost for using the Quick Start.
The AWS CloudFormation template for this Quick Start includes configuration parameters
that you can customize. Some of these settings, such as instance type, will affect the cost of
deployment. For cost estimates, see the pricing pages for each AWS service you will be
using. Prices are subject to change.
The Quick Start provides a free, 30-day trial of Jupiter. If you want to implement Jupiter at
enterprise scale, contact Cognizant at [email protected] about
additional service agreements. You are responsible for paying for the AWS services that
Jupiter uses and for any AWS services created for your project.
Jupiter Architecture
Figure 3 shows the Jupiter architecture, and how it interacts with AWS Services.
Figure 3: Jupiter architecture
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 6 of 25
Infrastructure Architecture
Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters
builds the following Jupiter environment in the AWS Cloud.
Figure 4: Quick Start architecture for Jupiter on AWS
The Quick Start sets up the following:
A virtual private cloud (VPC) that spans two Availability Zones. Each Availability
Zone contains two subnets: a public subnet to allow connecting over the internet
and a private subnet for AWS Elastic Beanstalk, Amazon Relational Database
Service (Amazon RDS), and Amazon EMR.
An internet gateway to allow access to the internet. This gateway is used by the
bastion hosts to send and receive traffic.
In the public subnets in both Availability Zones:
– Managed NAT gateways to allow outbound internet access for resources in
the private subnets.*
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 7 of 25
– A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell
(SSH) access to EC2 instances in private subnets.*
In the private subnets of both Availability Zones:
– An Elastic Beanstalk environment to host the Jupiter application server that
launches the Jupiter.war file.
– An Amazon EMR instance for data processing and validation. This instance is
bootstrapped with the emrbootstrap.sh script. The script writes the EMR logs
to the Amazon S3 bucket defined under the EmrLogBucket parameter.
* The template that deploys the Quick Start into an existing VPC skips the tasks marked by
asterisks and prompts you for your existing VPC configuration.
Prerequisites
Specialized Knowledge
Before you deploy this Quick Start, we recommend that you become familiar with the
following AWS services. (If you are new to AWS, see Getting Started with AWS.)
Amazon VPC
Amazon Elastic Beanstalk
Amazon EMR
Amazon RDS
Amazon S3
You may also need to know about the following supporting components of AWS:
AWS Identity and Access Management (IAM)
Amazon CloudWatch
Technical Requirements
Cucumber Java
Jupiter license
For more information about the Jupiter license, see the Costs and Licenses section of this
deployment guide. Once you have launched the stack and the Jupiter web application is
accessible, you can retrieve the license key. To retrieve the license key, see Step 4. Retrieve
License Key and Login Credentials.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 8 of 25
Deployment Options
This Quick Start provides two deployment options:
Deploy Jupiter into a new VPC (end-to-end deployment). This option builds a
new AWS environment consisting of the VPC, subnets, NAT gateways, security
groups, bastion hosts, and other infrastructure components, and then deploys Jupiter
into this new VPC. For information about creating a new VPC environment, see
https://aws.amazon.com/quickstart/architecture/vpc/.
Deploy Jupiter into an existing VPC. This option provisions Jupiter in your
existing AWS infrastructure.
The Quick Start provides separate templates for these options. It also lets you configure
CIDR blocks, instance types, and Jupiter settings, as discussed later in this guide.
Deployment Steps
Step 1. Prepare Your AWS Account
1. If you don’t already have an AWS account, create one at https://aws.amazon.com by
following the on-screen instructions.
2. Use the region selector in the navigation bar to choose the AWS Region where you want
to deploy Jupiter on AWS.
3. Create a key pair in your preferred region.
4. If necessary, request a service limit increase for the Amazon EC2 t2.micro instance type.
You might need to do this if you already have an existing deployment that uses this
instance type, and you think you might exceed the default limit with this deployment.
Step 2. Obtain a Jupiter License
The Quick Start provides a free, 30-day trial of Jupiter. If you want to implement Jupiter at
enterprise scale, contact Cognizant at [email protected] about
additional service agreements. You are responsible for paying for the AWS services that
Jupiter uses and for any AWS services created for your project.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 9 of 25
Step 3. Launch the Quick Start
Note You are responsible for the cost of the AWS services used while running this
Quick Start reference deployment. There is no additional cost for using this Quick
Start. For full details, see the pricing pages for each AWS service you will be using in
this Quick Start. Prices are subject to change.
1. Choose one of the following options to launch the AWS CloudFormation template into
your AWS account. For help choosing an option, see deployment options earlier in this
guide.
Option 1
Deploy Jupiter into a new
VPC on AWS
Option 2
Deploy Jupiter into an
existing VPC on AWS
Important If you’re deploying Jupiter into an existing VPC, make sure that your
VPC has two private subnets in different Availability Zones for the database
instances. These subnets require NAT gateways or NAT instances in their route
tables, to allow the instances to download packages and software without exposing
them to the internet. You will also need the domain name option configured in the
DHCP options as explained in the Amazon VPC documentation. You will be
prompted for your VPC settings when you launch the Quick Start.
Each deployment takes about one hour to complete.
2. Check the region that’s displayed in the upper-right corner of the navigation bar, and
change it if necessary. This is where the network infrastructure for Jupiter will be built.
The template is launched in the US East (N.Virginia) Region by default.
3. On the Select Template page, keep the default setting for the template URL, and then
choose Next.
4. On the Specify Details page, change the stack name if needed. Review the parameters
for the template. Provide values for the parameters that require input. For all other
parameters, review the default settings and customize them as necessary. When you
finish reviewing and customizing the parameters, choose Next.
Launch Launch
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 10 of 25
In the following tables, parameters are listed by category and described separately for
the two deployment options:
– Parameters for deploying Jupiter into a new VPC
– Parameters for deploying Jupiter into an existing VPC
• Option 1: Parameters for deploying Jupiter into a new VPC
View template
Network Configuration:
Parameter label
(name)
Default Description
Availability Zones
(AvailabilityZones)
Requires input The list of Availability Zones to use for the subnets in the
VPC. The Quick Start uses two Availability Zones from
your list and preserves the logical order you specify.
VPC CIDR
(VPCCIDR)
10.0.0.0/16 The Classless Inter-Domain Routing (CIDR) block that
consists of a range of IPv4 addresses for the new VPC.
You can use the default CIDR settings or assign your own
CIDR ranges for the VPC and subnets.
Private Subnet 1 CIDR
(PrivateSubnet1CIDR)
10.0.0.0/19 The CIDR block for the private subnet 1 located in
Availability Zone 1. The CIDR block parameter must be in
the form x.x.x.x/16-28.
Private Subnet 2 CIDR
(PrivateSubnet2CIDR)
10.0.32.0/19 The CIDR block for the private subnet 2 located in
Availability Zone 2. The CIDR block parameter must be
in the form x.x.x.x/16-28.
Public Subnet 1 CIDR
(PublicSubnet1CIDR)
10.0.128.0/20 The CIDR block for the public (DMZ) subnet 1 located in
Availability Zone 1. The CIDR block parameter must be in
the form x.x.x.x/16-28.
Public Subnet 2 CIDR
(PublicSubnet2CIDR)
10.0.144.0/20 The CIDR block for the public (DMZ) subnet 2 located in
Availability Zone 2. The CIDR block parameter must be
in the form x.x.x.x/16-28.
Remote Access CIDR
(RemoteAccessCIDR)
Requires input Provide a single IP address or IP range that you will use
to connect to the AWS Elastic Beanstalk Load balancer.
By default, HTTP and HTTPS access are restricted to the
IP addresses that you provide. We recommend that you
use a constrained CIDR range to reduce the potential of
inbound attacks from unknown IP addresses. For
example, if your IPv4 address is 203.0.113.25, specify
203.0.113.25/32 to list this single IPv4 address in CIDR
notation. If your company allocates addresses from a
range, specify the entire range, such as 203.0.113.0/24.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 11 of 25
For details, see VPCs and Subnets in the AWS
documentation.
AWS Elastic Beanstalk:
Parameter label
(name)
Default Description
AWS Elastic Beanstalk
technology stack
(SolutionStackName)
64bit Amazon
Linux 2018.03
v3.0.0 running
Tomcat 8 Java 8
The AWS Elastic Beanstalk technology stack. This must be a
valid and supported technology stack on AWS Elastic
Beanstalk.
Key Pair Name
(KeyPairName)
Requires input Public/private key pairs allow you to securely connect to your
instance after it launches.
Jupiter SSL Certificate
(JupiterSSLCert)
The Amazon Resource Name (ARN) of the SSL certificate for
terminating HTTPS connections on the load balancer; leave
this blank to disable SSL. However, we strongly recommend
turning on SSL in production environments.
EC2 Instance Type
(JupiterInstanceType)
t2.micro
The Jupiter EC2 instance type.
Database Configuration:
Parameter label
(name)
Default Description
Database Name
(DBName)
jupiterdb The name of the Jupiter database. The name must begin with
a letter and must contain only alphanumeric characters.
Database Engine
(DbEngine)
mysql The type of Amazon RDS instance.
Database Instance Type
(DbClass)
db.t2.micro The instance class of the Amazon RDS instance.
Database Master Username
(MasterDBUser)
jupiter The master user name for the Jupiter database.
Password for Database
Master User
(MasterDBPassword)
Requires input The master user password for the Jupiter database. The
password can only contain alphanumeric characters or the
following special characters !^*-_+
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 12 of 25
Amazon EMR Configuration:
Parameter label
(name)
Default Description
Create Amazon EMR cluster
(CreateEmr)
true Set this to true to create a new Amazon EMR cluster. If you do
not want to use Amazon EMR or want to use an existing
Amazon EMR cluster, set this to false.
Amazon EMR Master
Instance Type
(EmrMasterInstanceType)
m1.medium The instance type for the Amazon EMR master node.
Amazon EMR Core Instance
Type
(EmrCoreInstanceType)
m1.medium The instance type for the Amazon EMR core nodes.
Amazon EMR Core Nodes
(EmrCoreNodes)
1 The number of Amazon EMR core nodes. The minimum
number of nodes is 1, and the maximum is 500.
Amazon EMR Log Bucket
(EmrLogBucket)
Requires input The S3 bucket that is used to store the EMR logs. This bucket is only needed if EMR is used, and must be in the same region where this stack is being deployed. The bucket name can include numbers, lowercase letters, uppercase letters, periods (.), and hyphens (-). It cannot start or end with a hyphen (-) or period (.).
AWS Quick Start Configuration:
Parameter label
(name)
Default Description
Quick Start S3 Bucket
(QSS3BucketName)
aws-quickstart S3 bucket where the Quick Start templates and scripts are
installed. Use this parameter to specify the S3 bucket name
you’ve created for your copy of Quick Start assets, if you decide
to customize or extend the Quick Start for your own use. The
bucket name can include numbers, lowercase letters,
uppercase letters, and hyphens, but should not start or end
with a hyphen.
Quick Start S3 Key Prefix
(QSS3KeyPrefix)
quickstart-
cognizant-jupiter/
The S3 key name prefix used to simulate a folder for your copy
of Quick Start assets, if you decide to customize or extend the
Quick Start for your own use. This prefix can include numbers,
lowercase letters, uppercase letters, hyphens, and forward
slashes.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 13 of 25
Option 2: Parameters for deploying Jupiter into an existing VPC
View template
Network Configuration:
Parameter label
(name)
Default Description
VPC ID
(VpcId)
Requires input The ID of the existing VPC where the AWS resources will be
deployed through the AWS CloudFormation templates.
Public Subnet IDs
(PublicSubnetIds)
Requires input The IDs of the public subnets in the existing VPC; select at
least one subnet.
Private Subnet IDs
(PrivateSubnetIds)
Requires input The IDs of the private subnets in the existing VPC; select at
least two subnets.
Remote Access CIDR
(RemoteAccessCIDR)
Requires input Provide a single IP address or IP range that you will use to
connect to the AWS Elastic Beanstalk load balancer. By
default, HTTP and HTTPS access is restricted to the IP
addresses that you provide.
AWS Elastic Beanstalk:
Parameter label
(name)
Default Description
AWS Elastic Beanstalk
technology stack
(SolutionStackName)
64bit Amazon
Linux 2018.03
v3.0.0 running
Tomcat 8 Java 8
The AWS Elastic Beanstalk technology stack.
Key Pair Name
(KeyPairName)
Requires input Public/private key pairs allow you to securely connect to your
instance after it launches.
Jupiter SSL Certificate
(JupiterSSLCert)
The Amazon Resource Name (ARN) of the SSL certificate for
terminating HTTPS connections on the load balancer; leave
this blank to disable SSL. However, we strongly recommend
turning on SSL in production environments.
EC2 Instance Type
(JupiterInstanceType)
t2.micro
The Jupiter EC2 instance type.
Database Configuration:
Parameter label
(name)
Default Description
Database Name
(DBName)
jupiterdb The name of the Jupiter database.
Database Engine
(DbEngine)
mysql The type of Amazon RDS instance.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 14 of 25
Parameter label
(name)
Default Description
Database Instance Type
(DbClass)
db.t2.micro The instance class of the Amazon RDS instance.
Database Master Username
(MasterDBUser)
jupiter The master user name for the Jupiter database.
Password for Database
Master User
(MasterDBPassword)
Requires input The master user password for the Jupiter database. The
password can only contain alphanumeric characters or the
following special characters !^*-_+
Amazon EMR Configuration:
Parameter label
(name)
Default Description
Create EMR cluster
(CreateEmr)
true Set this to true to create a new EMR instance. If you do not
want to use EMR or want to use an existing EMR, set this to
false.
EMR Master Instance Type
(EmrMasterInstanceType)
m1.medium The instance type for the EMR master node.
EMR Core Instance Type
(EmrCoreInstanceType)
m1.medium The instance type for the EMR core nodes.
EMR Core Nodes
(EmrCoreNodes)
1 The number of EMR core nodes. The minimum number of
nodes is 1.
EMR Log Bucket
(EmrLogBucket)
Requires input The S3 bucket that is used to store the EMR logs. This bucket
is only needed if EMR is used, and must be in the same region
where this stack is being deployed. Bucket name can include
numbers, lowercase letters, uppercase letters, periods (.), and
hyphens (-). It cannot start or end with a hyphen (-) or period
(.).
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 15 of 25
AWS Quick Start Configuration:
Parameter label
(name)
Default Description
Quick Start S3 Bucket
(QSS3BucketName)
aws-quickstart S3 bucket where the Quick Start templates and scripts are
installed. Use this parameter to specify the S3 bucket name
you’ve created for your copy of Quick Start assets, if you decide
to customize or extend the Quick Start for your own use. The
bucket name can include numbers, lowercase letters,
uppercase letters, and hyphens, but should not start or end
with a hyphen.
Quick Start S3 Key Prefix
(QSS3KeyPrefix)
quickstart-
cognizant-jupiter/
The S3 key name prefix used to simulate a folder for your copy
of Quick Start assets, if you decide to customize or extend the
Quick Start for your own use. This prefix can include numbers,
lowercase letters, uppercase letters, hyphens, and forward
slashes.
5. On the Options page, you can specify tags (key-value pairs) for resources in your stack
and set advanced options. When you’re done, choose Next.
6. On the Review page, review and confirm the template settings. Under Capabilities,
select the check box to acknowledge that the template will create IAM resources.
7. Choose Create to deploy the stack.
8. Monitor the status of the stack. When the status is CREATE_COMPLETE, the Jupiter
cluster is ready.
9. Use the URLs displayed in the Outputs tab for the stack to view the resources that were
created.
Step 4. Retrieve License Key and Login Credentials
1. Open the Jupiter web app by clicking the Jupiter App endpoint URL in the Outputs
tab.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 16 of 25
2. Email the access key available in the Jupiter access page along with your name,
company, and email address, as shown in Figure 5, to
Figure 5: Getting the access key
3. After you’ve gotten the license key, enter the key in the License Key field, and then
choose Go, as shown in Figure 6.
Figure 6: Entering the license key
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 17 of 25
4. Use the details that you received as part of the license to sign in to the application, as
shown in Figure 7.
Figure 7: Signing in to the Jupiter application
Step 5. Test the Deployment
To test the deployment, you’ll need information from the Outputs tab of the AWS
CloudFormation console.
1. In the AWS CloudFormation console at
https://console.aws.amazon.com/cloudformation, choose the Outputs tab for the
parent stack.
2. Check the status of all stacks associated with the Quick Start in the
AWS CloudFormation console to make sure they show CREATE_COMPLETE and
display no errors.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 18 of 25
3. After you sign in to the Jupiter application, you will see a landing page similar to Figure
8.
Figure 8: Jupiter landing page
4. Test the deployment of the Jupiter web app:
a. Open the Configuration Wizard page, and create a test project, as shown in Figure 9.
Figure 9: Initiating a test project
b. Create a unique project name, unique project ID, and release ID.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 19 of 25
c. Enter the required details in the Environments tab, shown in Figure 10. Select the
project ID and release ID that you created. Under SERVER DETAILS, enter the
EMR DNS name from the Outputs section of the AWS CloudFormation console. To
establish SSH connectivity from Elastic Beanstalk EC2 to EMR EC2, upload the .ppk
file by using Choose File. If you’re using an existing EMR, under SERVER
DETAILS, provide the EMR DNS name, and run the emrbootstrap.sh script on the
EMR EC2 instance.
Figure 10: Configuring the remote environment
d. Enter the required details in the SCM tab, shown in Figure 11: Again, select the
correct IDs, and then enter the connection details to the SCM repository where the
Jupiter test project resides.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 20 of 25
Figure 11: Configuring Jupiter SCM
e. Enter the required details in the DataBase tab, shown in Figure 12: Select the
proper IDs, and then select the environment you want to configure this database for.
Enter the connection details for the database, either within AWS or a local system.
Figure 12: Configuring the Jupiter database
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 21 of 25
f. Verify that the project details entered are correct in the Summary tab, shown in
Figure 13.
Figure 13: Verifying Jupiter project details
g. Open the Test Execution tab, verify that a feature file is listed, select the file, and
then run it by choosing Execute, as shown in Figure 14.
Figure 14: Running Jupiter test
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 22 of 25
h. In the Test Execution Status tab, verify that the test run has completed
successfully, as shown in Figure 15.
Figure 15: Viewing the status of the Jupiter test run
i. Open the dashboard screen, select the proper information, and then verify that the
dashboard reflects the latest run, as shown in Figure 16.
Figure 16: Verifying the dashboard information
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 23 of 25
FAQ
Q. I encountered a CREATE_FAILED error when I launched the Quick Start.
A. If AWS CloudFormation fails to create the stack, we recommend that you relaunch the
template with Rollback on failure set to No. (This setting is under Advanced in the
AWS CloudFormation console, Options page.) With this setting, the stack’s state will be
retained and the instance will be left running, so you can troubleshoot the issue. (Look at
the log files in %ProgramFiles%\Amazon\EC2ConfigService and C:\cfn\log.)
Important When you set Rollback on failure to No, you will continue to incur
AWS charges for this stack. Please make sure to delete the stack when you finish
troubleshooting.
For additional information, see Troubleshooting AWS CloudFormation on the AWS
website.
Q. I encountered the following CREATE_FAILED error when I launched the Quick Start.
“No Solution Stack named 64bit Amazon Linux 2018.03 v3.0.0 running Tomcat 8 Java 8' found.
(Service: AWSElasticBeanstalk; Status Code: 400; Error Code: InvalidParameterValue;)”
A. If AWS CloudFormation fails to create the stack and you get a “No Solution Stack found”
error, the Java and Tomcat Platform version for AWS Elastic Beanstalk might have been
updated. It is likely that the solution stack in use was deprecated, and you need to update
the platform to the latest version. Refer to the configurations listed at Latest Java and
Tomcat Platform for AWS Elastic Beanstalk in the AWS documentation. Use these version
numbers in the allowed values for the SolutionStackName parameter for the AWS
CloudFormation template (Jupiter.template) in Option 2.
For additional information on Tomcat Platform History, see Tomcat Platform History on
the AWS website.
Q. I encountered a size limitation error when I deployed the AWS CloudFormation
templates.
A. We recommend that you launch the Quick Start templates from the location we’ve
provided or from another S3 bucket. If you deploy the templates from a local copy on your
computer or from a non-S3 location, you might encounter template size limitations when
you create the stack. For more information about AWS CloudFormation limits, see the AWS
documentation.
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 24 of 25
Git Repository
You can visit our GitHub repository to download the templates and scripts for this Quick
Start, to post your comments, and to share your customizations with others.
Additional Resources
AWS services
Amazon EC2
https://aws.amazon.com/documentation/ec2/
Amazon VPC
https://aws.amazon.com/documentation/vpc/
AWS CloudFormation
https://aws.amazon.com/documentation/cloudformation/
AWS EMR
https://aws.amazon.com/documentation/emr/
AWS RDS
https://aws.amazon.com/documentation/rds/
Cucumber documentation
https://cucumber.io/docs/
Quick Start reference deployments
AWS Quick Start home page
https://aws.amazon.com/quickstart/
Document Revisions
Date Change In sections
June 2018 Initial publication —
Amazon Web Services – Jupiter on the AWS Cloud June 2018
Page 25 of 25
© 2018, Amazon Web Services, Inc. or its affiliates, and Cognizant Technology Solutions.
All rights reserved.
Notices
This document is provided for informational purposes only. It represents AWS’s current product offerings
and practices as of the date of issue of this document, which are subject to change without notice. Customers
are responsible for making their own independent assessment of the information in this document and any
use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether
express or implied. This document does not create any warranties, representations, contractual
commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities
and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of,
nor does it modify, any agreement between AWS and its customers.
The software included with this paper is licensed under the Apache License, Version 2.0 (the "License"). You
may not use this file except in compliance with the License. A copy of the License is located at
http://aws.amazon.com/apache2.0/ or in the "license" file accompanying this file. This code is distributed on
an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.