Proxy, Reverse Proxy, SSM, Cloudwatch

𝐏𝐫𝐨𝐱𝐲 𝐒𝐞𝐫𝐯𝐞𝐫 - A middle man server that masks your Ip address and sends the request to the destination server(Internet). For example a user "A" wants to hit the server "B"(Internet) , the request from A reaches a proxy server which sends the request of "A" as if a request is trying to reach "B"(Internet)
In this way "B" doesn't know the Ip address of user "A"
A(internet) - Proxy Server(Masks the Ip address of A) - B(Destination Server)_
𝐑𝐞𝐯𝐞𝐫𝐬𝐞 𝐏𝐫𝐨𝐱𝐲 𝐒𝐞𝐫𝐯𝐞𝐫 - A middle man server which accepts the user's request (C) that comes via the internet to hit the server(D). The response from server (D) to (C) is sent to the user as if the response is coming from middle man server. In this way the IP address of Server D is masked
C(Internet) - Reverse Proxy Server(masks the ip address of D) - D(Destination)
𝐒𝐒𝐌 - Systems Manager in AWS is used to manage the EC2 instances. To manage the EC2 instances via Systems Manager we must create a role "ec2roleforSSM" and attach it to the EC2 instances. We must install SSM agent in EC2 instances. Once this is done in SSM dashboard we can see the EC2 instances under managed instances tab. Using Run command we can execute scripts or any command on the EC2 instances under the managed instances tab. We can perform patching using patchbaseline on Ec2 instances we can choose the patch required and not required via Patch baseline. Using Fleet Manager we can manage the nodes(EC2 instances or onpremise servers). We can manage the nodes access, RDP, SSH, Administrator passwords, user management, performance of the machines, utilization of Disk, CPU etc tasks of the nodes using Fleet Manager.
*𝐂𝐥𝐨𝐮𝐝 𝐖𝐚𝐭𝐜𝐡 *- Cloud Watch is a monitoring agent that has to be installed in your EC2 machine so that you will be able to view the detailed metrics of the EC2 machines such as disk, cpu, read ops, write ops, queue depth, etc.. We can configure Cloudwatch alarms in order for to monitor the performance of our Ec2 machines. For example when CPU utilization of a particular production server reaches 70-90% then an alarm should be triggered and we can also make this alarm to reach the customer or the user via SNS notification service. We can create log groups in Cloud Watch in which the ECS or VPC flow logs can be stored. Using Cloudwatch event rules we can define in a way of automation to trigger an event such as any action to be made on the specified AWS resources.
The detailed way of installing Cloud watch agent can be seen here - https://lnkd.in/gXxzgEET

aws #awscloud #cloudcomputing

(will be writing here about route53 and Kinesis shortly)