My Private API Doesn't Start or I Can't Connect To It

The initial AWS Integration takes time, especially in My VPC mode. Once the integration is done, it should take up to 5 minutes until the Local API is up. If the Local API is still unavailable beyond that time period, it might be the result of one of the following issues:

Elastic IPs Limit Reached
EC2 Spot Instance Not Running
DNS Cache
Security Group Not Open

Elastic IPs Limit Reached

Before deploying a Cluster to your Private VPC, Upsolver allocates Elastic IP addresses to make sure that servers are discoverable.

For API and Query clusters: Elastic IP addresses are mandatory.
For Compute Clusters: This is optional and can be edited from the UI. (Navigate to the Compute Cluster, click the caret next to the Stop button, then click Edit and clear the Elastic IPs checkbox. Note that when the Elastic IPs option is not selected, external resources (e.g., Redshift or Elasticsearch) will not be able to recognize the Compute Cluster servers by their IP addresses.
For Compute or Query Clusters that have Auto Scaling turned on: Upsolver allocates Elastic IP addresses for a cluster according the maximum number of servers.
For Compute clusters that have additional processing units for replay: Upsolver also allocates Elastic IP addresses for those processing units.

The number of Elastic IPs that an account in AWS can allocate is limited per region. You can raise the limit of Elastic IPs by sending a request to Amazon Web Services via this form. In the Limit type, select Elastic IPs and select the relevant region.

If Upsolver is unable to allocate Elastic IPs because the limit is exceeded, a notification pops up containing a link to this page.

EC2 Spot Instance Not Running

A problem starting up an EC2 Spot Instance in your account may be due to AWS Service Limits. See Appendix A for a list of prerequisites for AWS deployment.

To check if Local API is up:

1. Navigate to the EC2 Service in the AWS Console.
2. Click Instances in the navigation pane.
3. Enter upsolver-api in the Search bar and press Enter.

If you see items in the list, the local-api is up. Make sure the region is the same as the one chosen during the integration.

DNS Cache

It is likely that the DNS record for your local API has been cached by your computer. To clear the DNS cache, follow the instructions for your Operating System.

MacOS

Open the terminal and paste the command below:

sudo killall -HUP mDNSResponder;sudo killall mDNSResponderHelper;sudo dscacheutil -flushcache

Microsoft Windows 8 (Or above)

1. Select Win + X to open the WinX menu.
2. Right-click Command Prompt > Run as Administrator.
3. Type ipconfig /flushdns and press Enter.

Microsoft Windows 7

1. Click the Start Menu.
2. Type CMD in the Search Box.
3. Right-click Command Prompt > Run as Administrator.
4. Type ipconfig /flushdns and press Enter.

Microsoft Windows XP, 2000, Or Vista

1. Select Win + R to open the Run... Dialog.
2. Type ipconfig /flushdns and press Enter.

Security Group Not Open

The Security group of the Local-API might not be open to your address. You can look for the Security Group created by the Cloud Formation Stack and open ports 80 and 443 to your IP address.

1. Navigate to the EC2 Service in the AWS Console.
2. Click Security Groups (Under Network & Security) in the navigation pane.
3. Type Upsolver VPC Security Group in the Search bar and click Enter.

The security group created by Upsolver is displayed in the list below the search bar.

4. Right-click the security group and select Edit Inbound Rules.
5. Add two rules and configure them specified in the following table:

Type

Protocol

Port Range

Source

Description

HTTP

TCP

80

My IP

HTTP For (e.g., San Francisco Offices)

HTTPS

TCP

443

My IP

HTTPS For (e.g., San Francisco Offices)

6. Click Save. It may take up to a minute for the local API to be reachable by your network.

If none of the above applies to your situation, contact us via the intercom widget or by mail: support@upsolver.com.