Versions Compared

Old Version 6

changes.mady.by.user Sarabjeet Kaur

Saved on

compared with

New Version 7

changes.mady.by.user Sarabjeet Kaur

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Log in to your AWS Portal, with the user having sufficient permissions and information as mentioned in the prerequisites.

  2. On the Home page, use the search box to search for AWS Marketplace Subscriptions. <>

    Image Added

  3. In the AWS Marketplace section, click Discover Products. <>

    Image Added

  4. In the AWS Marketplace Products section, type Kyvos in the search box. The Kyvos offer is displayed.  <>

    Image Added

  5. Click the Kyvos offer. This will take you to the Kyvos page, which contains information about the Product overview, Plans and Pricing, Usage Information, Support, as well as Ratings and Reviews. You can also click on each tab to read the respective information. <>

    Image Added

  6. In the Pricing Information section, select the Region in which you want to deploy Kyvos. You will also view the Kyvos pricing details for each Kyvos resources. Now, click Continue to Subscribe.<>

  7. Now, click Continue to Subscribe. This will take you to the Kyvos Terms and Conditions page. In the Action column, click Show Details to expand and view the pricing details of Kyvos resources. Similarly, you click Hide details to collapse the pricing details. <>

    Image Added

  8. Now, click Continue to Configuration. This will take you to the Configure this Software page. <>

    Image Added

  9. Select one of the following from the Fulfillment option:

    1. Kyvos (with existing VPC): Select this option if you want to deploy Kyvos using existing VPC.

    2. Kyvos (with VPC creation): Select this option if you want Kyvos to create VPC.
      <>

  10. Click Continue to Launch. This will take you to the Launch this Software page. On the page, you can do the following:

    1. Click the Usage instructions link and the following message is displayed. <>

      Image Added

    2. In the Choose Action list, the Launch CloudFormation option is displayed by default.

    3. Click Launch. This will take you to the Create stack (Step 1) page.
      <>

Step 1: Specify template

  1. In the Prerequisite - Prepare template, select the Template is ready option.

  2. In the Specify template,  select the Upload a template file option to upload your CloudFormation template using the Choose File button.

  3. Click NEXT.

...

  1. The Parameters area displays the configurations defined in your template. It also allows you to enter custom values to create or update a stack.

  2. Enter details as:

Configuration 

Parameter 

Description/Remarks 

Security Configurations

Select the name of the Key Pair to be used with EC2 instances

A key pair consisting of a public key (stored by AWS), and a private key file (stored by the user). Together, they allow you to connect to your instance securely.

Enter the SSH Private Key text

Provide the text of your SSH key. To get this, open your .pem file in edit mode, and copy the complete text.

Select the name of the Key Pair to be used with Bastion Host

A key pair consisting of a public key (stored by AWS), and a private key file (stored by user). Together, they allow you to connect to your instance securely.

For example, select AWS::EC2::KeyPair::KeyName

VPC Configurations

Specify an IPv4 CIDR block of existing VPC.

Please enter the IP range (CIDR notation) for this VPC

Select the VPC in which EC2 instances will be launched

Select the VPC from the list.

Select the Private Subnets to be attached to EC2 instances

Select 2 private subnets, each from a different availability zone.

Select the Public Subnets to be attached to EC2 instances

Select 2 public subnets, each from a different availability zone.

EMR Configurations

Enter the number of Core EC2 Instances to be launched with EMR 

The number of Core EC2 Instances to be launched with EMR.

Recommended value: 2

Enter the minimum number of Core EC2 instances that should be kept running

The minimum number of core nodes that will keep running during scale-in operation.

Recommended value: 2

Enter the maximum number of Core EC2 instances that should be kept running

The maximum number of core nodes that can be used by the EMR during scale-out operation. Recommended value: 10

Enable In-transit encryption for EMR cluster 

Set the value of this parameter to true if you need in-transit encryption with TLS for the EMR cluster.

Enter the S3Object ARN where PEM based certificate is located 

Enter the S3Object Amazon Resource Name (ARN) of the KMS certificate.

NOTE: This is required only if you have enabled in-transit encryption for the EMR cluster.

RDS Configurations 

Postgres Password Kyvos

Specifies the value of the password used for Kyvos Repository. NOTE

The password can include any printable ASCII character except "/", """, "@" and single quote

Advanced Configurations

Select Instance Type which will be used for Query Engines.

Select the required instance type that will be used for Query Engines.

Select Instance Type which will be used for BI Server.

Select the required instance type that will be used for BI Server.

Name of IAM User to give permissions on KMS key

Specify the name of IAM User to give permissions on KMS key.

Enable Environment validation

By default, the False value is selected to enable the environment validation.

Allowed IP Range

Provide the range of IP addresses allowed to access Kyvos Instances. Use 0.0.0.0/0 to allow all users access.

Email ID

You will receive Kyvos Application URLs and Cloudwatch Alarm Notifications on this email address.

Cloudwatch Alarms

Select true to receive Cloudwatch Alarm Notifications on the above email address if provided.

Password for Kyvos and Kyvos Manager.

Enter the Admin password for Kyvos and Kyvos Manager Web portal. Keep this admin username and password safe for future reference.

  1. Click NEXT.

Step 3: Configure stack options

...

  1. Permissions: Choose an IAM role to explicitly define how CloudFormation can create, modify, or delete resources in the stack. If you don't choose a role, CloudFormation uses permissions based on your user credentials.

  2. Stack failure options: You can specify roll back behavior for a stack failure. For more information, see AWS documentation.

  3. Advanced options: Optionally, you can set additional options for your stack, like notification options and a stack policy. 
    Enter details as:

Parameter 

Description/Remarks 

Stack policy

Defines the resources that you want to protect from unintentional updates during a stack update. Kyvos does not allow any updates in the stack, so you can leave this blank.

Rollback configuration

Specify alarms for CloudFormation to monitor when creating and updating the stack. If the operation breaches an alarm threshold, CloudFormation rolls it back.

Monitoring time (optional): The number of minutes after the operation completes that CloudFormation should continue monitoring the specified alarms.

CloudWatch alarm (optional): Amazon Resource Name (ARN) of the alarm to monitor.

Notification options

Specify SNS topic ARN (optional).

Stack creation options

Rollback on failure: Specifies whether the stack should be rolled back if stack creation fails.

Timeout: The number of minutes before a stack creation times out.

Termination protection: Prevents the stack from being accidentally deleted. Once created, you can update this through stack actions.

  1. Click NEXT.

Step 4: Review

...