Cloudwatch Metric Configuration JSON

Deploying Configuration .json to Instance To deploy this configuration file and make the Cloudwatch Agent read it which we installed via Ansible by this post, you need to be sure that you installed Cloudwatch Agent to your instance properly. After installing the agent, you need to put this configuration file under /opt/aws/amazon-cloudwatch-agent/etc directory and make sure you name it amazon-cloudwatch-agent.json. When you start the agent after putting your configuration file, Cloudwatch service will automatically turn it into a .toml file under the same directory and reads that file. If your agent refuse to start when you run this: [crayon-5e49939064fd3596713718/] Make sure…

Continue Reading

Cloudwatch Agent Installation to EC2 Instances with Ansible

Prerequisites In this post, I will be explaining how to install Cloudwatch Agent using an Ansible Controller Host machine which is used for initializing and provisioning other machines. You will need: Basic knowledge of Ansible A Controller machine to run the playbook remotely A Controller machine with Ansible installed A Remote machine with SSH Daemon and Python interpreter installed A Remote machine with proper Policy attached (Allowance for PutMetricData) Make sure you have a proper configuration .json file, check here Playbook Using a Controller EC2 instance makes it easier to manage other instances since in this way, you don't need…

Continue Reading

Classful Addressing/FLSM/VLSM/CIDR

Classful Addressing This addressing strategy is the oldest one used back in the days. Nowadays, we don't work with it but lecturers are still teaching it to help students understand and analyse the addressing strategies. Main idea of classful addressing is dividing IPs by certain subnet masks and create classes from them. There are five classes extracted by classful addressing and each of them has their own usages and attributes. This is an old addressing and there was a lot of wastage of IPs. The idea was, if you were a company that needed 200 IP addresses, a class C assignment…

Continue Reading

HTTPS and TLS (SSL 3+)

TLS is Next Generation SSL When people talk about SSL(Secure Socket Layers) protocol, what they actually mean is TLS(Transport Layer Security). TLS is the successor and the new name of SSL. SSL 3.1 is actually TLS 1.0. TLS 1.1 is SSL 3.2 and TLS 1.2 is SSL 3.3. TLS 1.3 is the latest version proposed on 21 March 2018. Now that you know these, let's get into TLS. What is TLS? TLS is a protocol operating directly on top of TCP layer. Although, there are implementations of it for Datagram Based Protocols like UDP. By working on TCP layer, protocols…

Continue Reading
Close Menu