AWS Native deploymet docs update: instance types params

docs/md/installation/native/aws/terraform/README.md

@@ -165,6 +165,7 @@ output "instance_role" {
 | `deployment_env`                    | Environment name for the deployment. Will be used as resource name prefix of the created resources (security groups, IAM roles etc.) |
 | `vpc_id`                            | Id of the VCP to be used for deployment of the bastion instance.                                                                     |
 | `subnet_id`                         | Id of the VCP subnet to be used to launch an instance                                                                                |
+| `instance_type`                     | (Optional) AWS EC2 Instance type to be used for Jump server deployment. Default t3.small                                             |
 | `ami_id`                            | (Optional) AMI to be used for bastion ec2 instance. If empty - eks-optimized will be used.                                           |
 | `iam_role_permissions_boundary_arn` | (Optional) Account specific role boundaries which will be applied during jump-server instance profile creation                       |
 
@@ -350,6 +351,7 @@ To configure `cluster-infrastructure` deployment, there is a list of variables t
 | `cp_edge_host`                           | (Required) EDGE service domain name address.                                                                                                                                                                                                                                          |
 | `cp_gitlab_host`                         | (Required) GITLAB service domain name address.                                                                                                                                                                                                                                        |                                                                                                                     
 | `cp_idp_host`                            | (Optional) Self hosted IDP service domain name address. WARNING: Using self hosted IDP service in production environment strongly not recommended!                                                                                                                                    |                      
+| `eks_system_node_group_instance_type`    | (Optional) AWS EC2 Instance type to be used for System node (Where all application pods will be deployed). Default m5.xlarge                                                                                                                                                          |
 | `external_access_security_group_ids`     | (Optional) Ids of the SGs to be attached to the ELB to allow traffic from users to the platform. Created as prerequisites by administrator who is deploying the system, with regard to organisational network policies and best practices.                                            |
 | `deploy_filesystem_type`                 | (Optional) Option to create EFS or FSx Lustre filesystem: must be set efs or fsx. If empty, no FS will be created. Default efs.                                                                                                                                                       |
 | `cloud_pipeline_db_configuration`        | (Optional) Username with password and database, which will be created. Username will be owner of the database. Additional settings with Postgresql provider and versions.tf file must be set. For example see [main.tf](#cluster-infrastructure-deployment) of the cluster deployment |