Specifications

20 | CHAPTER 1: RUNNING COMSOL MULTIPHYSICS® WITH AMAZON ELASTIC COMPUTE CLOUD™
once (warning: this will also DELETE ALL DATA on the Amazon-based machines).
To be able to delete the license manager stack automatically, you will need to remove
all files from the login bucket, if you chose to create one when creating the license
server. To do this, follow the steps described below:
1 Open the Amazon S3™ bucket created with the license server by navigating to
https://console.aws.amazon.com/ and click the Amazon S3™ icon.
2 Click the Amazon S3™ bucket created with your license server.
3 Delete all files in the bucket.
You can now continue to the process of removing the servers. The steps described
below need to be made for both the COMSOL Multiphysics server stack and the
COMSOL license server stack.
1 Go to https://console.aws.amazon.com/ and click the AWS CloudFormation™
icon.
2 Select the stack you want to delete and click the button Delete Stack.
3 Confirm the deletion of the stack by clicking Yes, Delete.
4 The deletion process will start and your stack will be removed.
Troubleshooting
• Problem 1: Error message “The key 'My_KeyPair' does not exist” when creating a
COMSOL License server or COMSOL Multiphysics server.
The reason for this error is that AWS™ did not find any key with the name
My_KeyPair. There are three probable causes of this:
- No key pair has been created yet. For instructions on how to create a key pair,
please refer to Step 1 of this guide.
- The name given in the KeyName file does not correspond to the name you have
given to your key pair. Make sure that the name of the key pair is the same as the
value given in the KeyName field and retry the step that failed.
- You are trying to start a COMSOL license server or COMSOL Multiphysics
server in another availability zone than where you have created your key pair.
Make sure that you are using the same availability zone as you used when creating
your key pair. You can change the availability zone with the help of the menu in
the upper right corner of the AWS™ console.
• Problem 2: Error message “The specified instance type can only be used in a VPC.
A subnet ID or network interface ID is required to carry out the request” when