Contribute in GitHub: |

IBM IoT Connected Vehicle Insights Private deployment guide

Overview

This document describes the procedure for deploying IBM® IoT Connected Vehicle Insights Private into your own environment on Amazon Web Services (AWS). It includes the initial procedure for setting up your own installation server on AWS S3, which you run before you create IBM IoT Connected Vehicle Insights Private instances, and the deployment procedure that runs each time you want to create new IBM IoT Connected Vehicle Insights Private instances.

Prerequisites

You download installation packages from IBM Passport Advantage onto your local computer and set up an S3 bucket so that IBM IoT Connected Vehicle Insights Private components can be deployed to Amazon Elastic Compute Cloud (Amazon EC2) instance in your AWS environment. Your computer must have at least 65 GB free disk space for storing and setting up installation images. AWS Command Line Interface (CLI) also must be installed on your computer. Prepare your AWS account with administrative privileges to be used for installation process. You can optionally enable the AWS Client VPN feature so that you can directly access each IBM IoT Connected Vehicle Insights Private node by establishing VPN connection. If you want to enable AWS Client VPN, prepare server certificate and client certificate, respectively.

Notes

Availability zone in AWS

The number of availability zones in your target region must be 3 or more.
- See Availability Zones

Client VPN in AWS

If you want to set up the Client VPN, you need to choose a region where the Client VPN endpoint is supported.

AWS user's permissions

If necessary, follow the official AWS guide and grant the appropriate permissions from Identity and Access Management (IAM) to the AWS user for the following items:
- Route53
- EC2
- S3
- CodeDeploy
- SSM
- EC2Container
- EKS
- IAM
- CloudFormation
- Lambda
- VPC
- CertificateManager
- EFS