Step 2 : Deploy the MCM9000 from AMI

On EC2

  1. Select the region you request TAG V.S to share the AMI.

  2. In the left pane select AMI.

  3. Select Private Images

  4. Select 'MCM9000 V_xx Official' AMI

  5. Action → Launch

The AMI ID provided in the license email

 

  1. Select an Instance type from the following MCM9000 certified selection:

 

Please Note:

  • The minimum required specification for the MCM9000 instance type is the c7i.4xlarge

  • All instances tested on a shared Tenancy

         Read more information about the Ec2 instances :

 Amazon EC2 C5 Instances

Amazon EC2 M6i instance

Amazon EC2 C6I instances

Amazon EC2 C7I instances

Amazon EC2 C6a instances

Amazon EC2 C7a instances

  • Monitoring of each SD channel requires 1 SD unit

  • Monitoring of each HD channel requires 5 SD units

  • Monitoring of each Contribution HD channel requires 10 SD units

  • Monitoring of each HEVC channel requires double the points above

  • Creation of each **Different**

                    H.264 or Uncompressed mosaic requires 20 SD units for HD and 40 SD units for UHD

2. On the 'Configure Instance' page select the following:

  • Number of instances – You wish to launch from the MCM9000 AMI

  • Network - Select the VPC you wish to locate the MCM9000

  • Subnet - Select the Subnet and the AZ you wish to locate the MCM9000

  • Auto-assign Public IP – Enable this option only in case the MCM9000 is located in Public subnet and you need to access the MCM9000 from the public internet

Disable this option only in case the MCM9000 is located in Private subnet and you plan to access the MCM9000 from a bastion

  • Enable termination protection – enable this option as a best practice to protect the MCM9000 from termination by mistake

  • Tenancy - Leave the Default option as 'Shared – Run a shared hardware instance'

For more details about Instance purchasing options read the following: Instance purchasing options

  1. Add Storage – The MCM9000 AMI is shared with 8Gib EBS Volume. The MCM9000 uses only this volume size and there is no need to add additional EBS volume.

  2. Add Tags – Add Tag name for better tracking.

  3. Configure Security Group – Select the 'MCM9000_SG' security group you have created in previous deployment step; Step 1- 'Prepare Your AWS Account'.

  4. Review the instance details and then press Launch.

  5. Select an existing key pair or create a new key pair- Download a new one or use an existing one from your account.

Please Note: The MCM9000 AMI is blocked for security reasons. Any attempt to enter the system is forbidden and can be done only by TAG V.S engineers.