Origami_Wiki - User contributions [en]

Backup setup to s3

2021-04-27T10:36:05Z

137.97.105.157:

[[Category:It-support|Backup setup to s3]]

1) Firstly create bucket and grant permission for a user to it by following the steps mentioned in the below documents

S3 bucket creation

S3 bucket access user creation

2) Login to the server in which we want to configure backup to s3 bucket

3) Then install awscli

yum install awscli

4) Then we need to configure the user with permission to the corresponding bucket in the server. For that run the command " aws configure"

5) It will ask for "Access key ID" and "Secret access key", which was obtained when we create the user with programmatic access. Please give it without any mistake.

6) Then configure the cronjob for moving the backup to the corresponding s3 bucket to which the user has access.

7) For setup the cron you can use below steps

*) Create a shell script using the below command

#!/bin/bash
aws s3 mv <Source directory> s3://<bucketname> --recursive

*) Give execution permission to the script

chmod +x <filename.sh>

*) To open cron tab use the command >> crontab -e

*) Then configure cron job by the general syntax. One example is given below.

30 20 * * * /home/user/filebackupmove.sh ( it will execute at server time 8:30 pm every day )

Backup setup to s3

2021-04-27T10:35:44Z

137.97.105.157:

[[Category:It-support|Backup setup to s3]]

dsd
1) Firstly create bucket and grant permission for a user to it by following the steps mentioned in the below documents

S3 bucket creation

S3 bucket access user creation

2) Login to the server in which we want to configure backup to s3 bucket

3) Then install awscli

yum install awscli

4) Then we need to configure the user with permission to the corresponding bucket in the server. For that run the command " aws configure"

5) It will ask for "Access key ID" and "Secret access key", which was obtained when we create the user with programmatic access. Please give it without any mistake.

6) Then configure the cronjob for moving the backup to the corresponding s3 bucket to which the user has access.

7) For setup the cron you can use below steps

*) Create a shell script using the below command

#!/bin/bash
aws s3 mv <Source directory> s3://<bucketname> --recursive

*) Give execution permission to the script

chmod +x <filename.sh>

*) To open cron tab use the command >> crontab -e

*) Then configure cron job by the general syntax. One example is given below.

30 20 * * * /home/user/filebackupmove.sh ( it will execute at server time 8:30 pm every day )

Automate backup using AWS Backup

2021-04-27T10:22:19Z

137.97.105.157: Automate backup using AWS Backup

[[Category:It-support|Automate backup using AWS Backup]]

1) Login to AWS console and go to AWS Backup service

2) Click on Backup plans (or Manage Backup plans), and then Create Backup plan. There, you have a couple of options.

3) Then select "Build a new plan" and give the details like plan name, backup retention period, backup window start time etc

4) After you’re done and your plan is created, it is time to assign resources to it.

5) Click on "Assign Resource" and the resources can be assigned by using tags or by adding them based on the Resource ID.

6) With the plan created and the resources assigned, your AWS Backup is ready.

S3 bucket creation

2021-04-27T06:51:05Z

137.97.105.157:

[[Category:It-support|S3 bucket creation]]

1) Login to AWS console.

2) Then go to s3 section by click on s3 in services list.

3) In s3 click the "create bucket" and give the details like bucket name, region etc they are asking and create it.

For creating folder in it

*) Open the bucket

*) Create folder by clicking "create folder" and give name for it.

For configuring retention period for the objects in bucket

*) Open Bucket >> Management

*) Then create Lifecycle policy according to your retention need.

Backup setup to s3

2021-04-27T06:47:50Z

137.97.105.157: Backup setup to s3

S3 bucket access user creation

2021-04-27T06:19:27Z

137.97.105.157: S3 bucket access user creation

[[Category:It-support|S3 bucket access user creation]]

1) Login to AWS console and open IAM section in the services.

2) In IAM click "Users" >> "Add user"

3) Then enter the user name and select "programmatic access"

4) Add permission by click on "permissions"

5) Then select "copy permissions from existing user"

6) Select any s3 access IAM user already created it it and click create user button

S3 bucket creation

2021-04-27T05:53:26Z

137.97.105.157: S3 bucket creation

Postgresql slow query

2021-04-27T05:32:42Z

137.97.105.157: Postgresql slow query

[[Category:It-support|Postgresql slow query]]

1) To enable slow query log in postgresql, firstly you have to open the postgres configuration file "/etc/postgresql/9.1/main/postgresql.conf"

2) Then find the following line

#log_min_duration_statement = -1

Uncomment it and replace -1 with a query runtime threshold in milliseconds.

eg: log_min_duration_statement = 1000

3) Make sure logging_collector is set to on.

4) Then save the configuration and restart the service

sudo systemctl restart postgresql

5) The go to the postgreSQL log collecting directory "/var/lib/pgsql/data/pg_log/" and find the log file in it.

SDC cohosting procedure

2021-04-27T05:21:42Z

137.97.105.157: SDC co-hosting procedure

[[Category:It-support|SDC co-hosting procedure]]

Please note that for moving a application to SDC we have to perform some step by step process from our end. Kindly find a brief explanation regarding what the full process includes given below.

1) First and foremost, we need to send a co-hosting request to SDC by filling the official co-hosting application given by SDC. The mail should be send from the department mail under kerala.gov.in domain.
You can download the co-hosting form from the link given below.

https://itmission.kerala.gov.in/sites/default/files/Application_forms/Appication%20for%20Co-Hosting%20in%20State%20Data%20Centres.pdf

2) After reviewing our request, they would allocate a staging server space in SDC DC, where we need to deploy our application first.

3) Once we have completed our application deployment in the staging server, then the department should take a quotation from any CERT-IN empaneled agencies and share the application details with them for performing security audit.

4) Then the department should produce a Safe to Host certificate of the application given by the security auditing CERT-IN empaneled agency after successful completion of STQC audit and fixes to SDC for move it to the production environment.

5) Finally, they will review it and allocate a production environment in SDC for making our application live in SDC DC. Then we need to migrate the application to the SDC production server.

Kindly note that, as I have mentioned in the above mail for the whole process, communication can be made from a mail ID under the kerala.gov.in domain only.

Password and access log sheet for digital assets

2021-04-27T05:03:35Z

137.97.105.157: Password and access log sheet for digital assets

[[Category:It-support|Password and access log sheet for digital assets]]

Kindly note that you have to update the "Password and access log of digital assets" sheet when create new logins, share it to anyone and password changed. Please follow the below steps for it.

1) Open the "SysAdmin Works" folder in drive and open the sheet "Password and access log of digital assets".

2)You have to update the sheet in the below given stages.

a) When new logins created
b) When shared the login details
c) When changed the password

a) When new logins created
==================================

*) when new logins are created add it to the "Items" section of the sheet under respective items.

b) When shared the login details
===================================

*) You should add new employees to the "Users with access" section

*) Whenever you/anyone shared any of the login credentials with others, you should change the access to that digital assets to "yes" under the corresponding user.

*) Also when an employee is resigned you should revoke all of his/her accesses and update the sheet accordingly.

c) When changed the password
===================================

*) Please note that there are 2 columns in the sheet "Scheduled password change" and "Last changed".

*) You must change the passwords according to the scheduled time and update the password changed date in "Last changed" column.

*) Also don't forget to update the lastpass entries with the new password.

Server and domain list

2021-04-27T04:39:40Z

137.97.105.157: Server and domain list

[[Category:It-support|Server and domain list]]

When there is a new server or domain has been setup, you should update the Google sheet accordingly. Please follow the below steps for it.

1) Login to Google drive and open the folder "SysAdmin Works".

2) There you can find the sheet "Servers bill update and domain lists".

3) Open the sheet and update the server details and domain lists corresponding to each server in sheet1 and sheet2 in it.