Amazon Cloud : AWS Linux Server Tips, Tricks & Tutorials

The Amazon Web Services provides remote computing services. Most important and well-known service is the Amazon S3 and Amazon EC2. I have compiled some of the reasons for the AWS choice as Cloud Server, for big and small users.   Pricing Model : Pay-As-You-Go. I am only pay for that what I use. Let’s take an example to understand this: In AWS infrastructure I am using 13GB, now usually what happens with other cloud service I estimate my usage say 40GB, reserve it, and pay for that 40GB monthly. And with AWS, I am not using the whole 40GB. I just have 13GB of data, so I just pay for that 13GB, and I can always store more as your requirements grow, there is no restriction!     Security. Cloud security at AWS is the highest priority Amazon cloud is a secure, durable technology platform with industry-recognized certifications and audits: PCI DSS Level 1, ISO 27001, FISMA Moderate, FedRAMP, HIPAA, and SOC 1 (formerly referred to as SAS 70 and/or SSAE

Introduction :   A utomatic screen-shots  of Linux system directly import  on your web server with Linux samba server service and scrot command. 1)  Setup web panel UI on your web server :   Get web panel PHP/HTML code from Github URL: https://github.com/raj412/Employee-Monitoring-for-Linux-System It’s work in Linux server LAMP environment(no need database for this configuration ) Defult login username password is admin/1234. You can change username/passwrod from login.php file in line number #6 Login Page : Dashboard : Screenshot Page : 2)  Samba server configuration on web server : I.  Install Samba on your server where you setup Linux screenshot log system web panel. sudo apt-get update sudo apt-get install samba II.  Set a password for your user in Samba sudo smbpasswd -a <user_name> III.  Share gallery-images folder from you web panel. This is my web panel gallery-images p

Start with what is Elastic Load Balancing? Elastic Load Balancing automatically distribute incoming application traffic to multiple destinations, such as Amazon EC2 instances, containers, IP address, and lambda functions. It can handle a variety of application traffic load in a single Availability Zone or multiple Availability Zones. Key points: The following two types  of load balancer: 1.  Internet Facing: has public IP 2.  Internal Load Balancer: routes traffic within a VPC There are three categories of Load Balancer: 1.  Application Load Balancer 2.  Network Load Balancer 3.  Classic Load Balance First Application Load Balancer Operates at Layer 7. Supports WebSockets and Secure WebSockets. Supports SNI. Supports IPv6. Second Network Load Balancer   ( The NLB is the recommended Load Balancer to be used at Layer 4) Operates at Layer 4. Preserves the source IP. Provides reduced latency compared to other Load Balancers

Everyone handle high traffic loads  on Apache server. During down-time they forget to check server memory . Apache not used lot of memory  still server not responding. All time we restart Apache service and all things will start working good. I also faced same issue numerous time and all-time  used same solution : Restart Apache. After lots of research and reading found one solution. In this blog you see step-by-step guide to apache2 performance settings. System environment: Intel(R) Xeon(R) CPU 3.10GHz, 4 cores | 8GB RAM Ubuntu 16.04 Apache2 version using mpm_event PHP FPM (5.6,7.1) First,  Calculate process size : Download : python script file “ps_mem.py” from Github Open this and ps_mem.py file upload on you server :  https://github.com/raj412/ps_mem chmod a+x ps_mem.py sudo python ps_mem.py Output like this:  See here : 12 Apache processes, consuming a total of  35.7MiB, so each Apache process is using roughly 3MiB of RAM. The 42 php-fpm process u