How to make changes in assigning security groups for an existing security groups in EC2

From the EC2 instance launching page --> right click on the instance --> Networking -->Change Security Groups.

Assign or un assign security groups by checkbox &Click on Assign Security Groups.                                        

EC2 placement groups

what is EC2 placement group?

It is just the way of placing EC2 instances.

They are three types of placement groups:

1. Clustered placement group.

2.Spread placement group.

3.partitioned placement group.

1. Clustered placement group: it is a grouping of instances within a single availability zone. This placement groups are recommended for applications that need low network latency, high network throughput, or both.

usually all the EC2 instances in this placement are maintained very close and in the same availability zone.

 2.Spread placement group: This placement groups are recommended for applications that have a small number of critical instances that should be kept separate from each other.

it is basically design to avoid hardware failure.

it is basically opposite to Clustered placement group.  

Each EC2 instance is completely individual in this placement group.

3.partitioned placement group:

Hands on:

from the EC2 console, Navigate to placement Groups option.

Choose Create Placement Group option.

Enter details:                                                                                 
Name:  <description>

Strategy: Cluster or Spread

Finally click on Create option.

if we create one cluster and one spread placement group. the placement group page looks like below.

Result: After the creation of 2 placement groups. while launching EC2 instance. Placement group can be selected

Security Groups

security groups are like virtual firewalls which allows communications from different through desired port numbers.

Few thumb rules in security groups:

1.By default all inbound traffic is blocked.

2.All outbound traffic is allowed based on inbound.

3.You can specify allow rules(0.0.0.0/0),but not deny rules(deny for particular ip address 😊)

4.you cannot block specific ip address using security groups, instead use network access control list.

Practical steps:

1.      1. Login to AWS account.    

 N   2.Navigate to Services àunder compute section àEC2àrunning instance --> security groups(as highlighted below.

3.Resultant screen looks like below screen. Here we can create, delete & edit security groups.                 

4.in the inbound tab, can open new ports or close existing old ports.                                                   

5.Add,delete,edit the port values, can be done here.                                                                      

6.Once after saving need to assign the security group to required EC2 instance.

SAP HANA COCKPIT NOTES 22: Add or Remove Users in Resource Groups

Add or Remove Users in Resource Groups

Add a cockpit user to a resource group or remove a user from a resource group.

Prerequisites

● Your cockpit user has the assigned role Cockpit Resource Administrator. 

● The Cockpit User Administrator has created some cockpit users. See Managing Cockpit Users. 

Procedure

1. Connect to the Cockpit Manager and sign in as a cockpit user with the Cockpit Resource Administrator role. You can reach the Cockpit Manager by entering the Cockpit Manager URL created during cockpit installation, or by following the Manage Cockpit link in the cockpit. The URL takes this form: 

https://<cockpit-host>:<port_number>

2.In the Cockpit Manager, select Resource Groups.

3. In the left pane, select the group you want to modify.

4. (Optional) To add a cockpit user.

               a. If necessary, click Users to display the list of cockpit users in this group. 

               b. Click Add User (far right). 

               c. Select the users to add and click OK. 

The cockpit displays the group, including the newly added cockpit user(s), on the Resource Groups page. 

5. (Optional) To remove a user:

               a. If necessary, click Users to display the list of cockpit users in this group.                                           b. Click the red  to the right of the user to be deleted and confirm the deletion. 

The cockpit displays the group, without the removed user, on the Resource Groups page.  

SAP HANA COCKPIT NOTES 14: configuring cockpit settings,Setting Connection Timeout

Introduction:

In the Cockpit Manager, as a cockpit administrator, you can select Settings to configure data collection, proxy server settings, and the connection timeout period, and to control whether or not SAP HANA Cockpit displays auto-created groups.

TASK 1:DATA COLLECTION

As a cockpit administrator, you can reconfigure the default, pre configured SAP HANA cockpit global settings for collecting monitoring data, such as system status, alert counts, and other data from registered resources.

Navigation

In the Cockpit Manager, select Cockpit Settings, and then Data Collection.

If necessary, you can change the defaults to specify:
● How many worker threads the collection service should use. Increasing threads can improve response time but uses more memory. The default is 5 threads.
● Whether and how often the cockpit collects system status and alert counts. The default is 60 seconds.
● Whether and how often the cockpit collects key performance area monitoring data from each managed resource.The default is 5 minutes.

There may be a brief lag before your changes in values take effect.

Note: 

You can also modify the collection settings for a specific resource by editing the details of that resource. Doing so overrides the global settings for that particular resource. See Override Data Collection for a Resource.

Tip: 

• The cockpit can support 1000s of registered resources.

 If the System Health Monitor displays ‘Not Collected’ for specific resources, you may wish to investigate the collection service log for rejected collections and reconfigure the worker threads accordingly.

Screenshots for the above scenario Task1:

step1: cockpit manager -->cockpit settings-->Data collection

Resultant screen look likes below:

Task 2:setting connection timeout

screenshot for the above timeout scenario:

Task 3: setting proxy server

screenshots for the above TASK 3: SETTING PROXY SERVER

cockpit manager--> cockpit settings--proxy                                                                                           

resultant screen:

TASK 4: Specifying Display of Auto-Generated Groups

As a cockpit administrator, you can choose whether or not SAP HANA cockpit displays resources as part of auto-created resource groups, or solely as part of resource groups that you create.

 A resource group—a named set of one or more registered resources—controls management and monitoring privileges. When you assign a cockpit user to a resource group that you have created, you enable the user to monitor and manage the group's resources through the cockpit. Each registered resource also belongs to a usage type resource group. These auto-created groups of resources (Production, Test, Development) are based on the system usage type of each resource. System usage type is configured during system installation, or later using the global.ini file with the usage parameter in the system_information section.

You can choose to hide one or more of the auto-created groups through the Cockpit Manager by selecting Settings, then Display, and deselecting or selecting each box. Opting to hide the auto-created groups does not affect the system usage type associated with the resource. It simply prevents the cockpit from organizing the display of resources by auto-created group.

screenshots for the above TASK4: scenario