<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Emre Çakmak on Medium]]></title>
        <description><![CDATA[Stories by Emre Çakmak on Medium]]></description>
        <link>https://medium.com/@emre.cakmak?source=rss-9e70f2260ca3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4SWoBPyvvVDYekrB9qkT_Q.jpeg</url>
            <title>Stories by Emre Çakmak on Medium</title>
            <link>https://medium.com/@emre.cakmak?source=rss-9e70f2260ca3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:47:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emre.cakmak/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Kubernetes Management: Dashboard Setup in AWS EKS, ELB & Route53]]></title>
            <link>https://aws.plainenglish.io/kubernetes-management-dashboard-setup-in-aws-eks-elb-route-53-integrations-and-user-9fbd29ab7363?source=rss-9e70f2260ca3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fbd29ab7363</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[kubernetes-dashboard]]></category>
            <category><![CDATA[aws-route53]]></category>
            <category><![CDATA[aws-elb]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Emre Çakmak]]></dc:creator>
            <pubDate>Thu, 13 Jul 2023 13:32:56 GMT</pubDate>
            <atom:updated>2023-08-19T14:18:50.924Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Kubernetes</strong> Management: Dashboard Setup in AWS EKS, ELB &amp; Route53 Integrations and User Authentication.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8OdVKs9nKI21J4iAoWTHUw.png" /></figure><h3>Introduction</h3><p>Hello, I’m <a href="https://www.linkedin.com/in/cakmak-emre/">Emre</a>. I work as a Cloud Native Engineer at <a href="https://bestcloudfor.me/">Bestcloudfor.me</a> and I’m part of a team that provides consulting services primarily in the AWS cloud domain to our clients.</p><p>In this article, we will explore the Kubernetes Dashboard. By understanding how to effectively install and utilize Kubernetes Dashboard, integrate AWS ELB and Route 53 services, and implement robust user authentication mechanisms you can elevate your Kubernetes infrastructure to new heights of efficiency and productivity.</p><p>So, let’s dive into this journey of simplifying Kubernetes management.</p><h3><strong>Kubernetes Dashboard</strong></h3><p>Kubernetes Dashboard<strong> </strong>is a web-based Kubernetes user interface. You can use Dashboard to deploy containerized applications to a Kubernetes cluster, troubleshoot your containerized application, and manage the cluster resources. Also you can use Dashboard to get an overview of applications running on your cluster, as well as for creating or modifying individual Kubernetes resources (such as Deployments, Jobs, DaemonSets, etc). For example, you can scale a Deployment, initiate a rolling update, restart a pod or deploy new applications using a deploy wizard.</p><h3>How to install it?</h3><p>There are different ways for installation. I am adding the GitHub link where you can access the documents. For this blog post, I have decided to proceed with the installation using Manifest file.</p><p><a href="https://github.com/kubernetes/dashboard">GitHub - kubernetes/dashboard: General-purpose web UI for Kubernetes clusters</a></p><p>We connect to Kubernetes cluster and enter the following command..</p><pre>kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.7.0/aio/deploy/recommended.yaml</pre><p>Ps: This may not be the latest version, be sure to check the <a href="https://github.com/kubernetes/dashboard/releases/latest">latest releases</a> page from github.</p><p>After that you can check the status of the pods by running the following command in the cluster.</p><pre>kubectl get pods -n kubernetes-dashboard</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*Le4x0z_M-Gh8yd2z27S-WQ.png" /></figure><p>After pods start working, edit the service type and change it to <strong>NodePort.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/462/1*emI8tDLsNVewCnVouogfzw.png" /></figure><pre>kubectl get svc -n kubernetes-dashboard</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*wGwivZWpPWx8vgPG2Y1qfg.png" /></figure><p>After changing the service type, go to AWS EC2 Console and create a target group for kubernetes dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*T4Z7CjhhLovMUR2CIqKKLw.png" /></figure><p>This part is crucial, choose <strong>HTTPS</strong> for both Target and health check protocol and enter your service NodePort.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*t02GmOUTIvDaD8b19t2biQ.png" /></figure><p>Then you can go to an Application load balancer that you have opened before and forward your domain to this target group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*7jH-kDfKKVs-ndNbPNMuYw.png" /></figure><p>If you have an SSL certificate for this domain, you can associate it with your load balancer or you can create new one with AWS ACM. I did it with AWS ACM service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*zdFu5fcwh5DB6Nm46mm_oQ.png" /></figure><p>After redirecting the relevant domain to ALB with A record via Route53, we can access the interface from the link.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lrnH0T9zpsZinLKl-Yfz2g.png" /></figure><h3>User Authentication</h3><p>You can login to the dashboard with kubeconfig or with a token via a service account you will create. You can use the following configurations to create cluster-specific service accounts and roles.</p><p><strong>Admin-user:</strong></p><pre>apiVersion: v1<br>kind: ServiceAccount<br>metadata:<br>  name: admin-user<br>  namespace: kubernetes-dashboard<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: ClusterRoleBinding<br>metadata:<br>  name: admin-user<br>roleRef:<br>  apiGroup: rbac.authorization.k8s.io<br>  kind: ClusterRole<br>  name: cluster-admin<br>subjects:<br>- kind: ServiceAccount<br>  name: admin-user<br>  namespace: kubernetes-dashboard</pre><p><strong>readonly-user:</strong></p><pre>apiVersion: v1<br>kind: ServiceAccount<br>metadata:<br>  name: readonly-user<br>  namespace: kubernetes-dashboard<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: ClusterRole<br>metadata:<br>  name: restricted-clusterrole<br>  annotations:<br>    rbac.authorization.kubernetes.io/autoupdate: &quot;true&quot;<br>  labels:<br>    name: restricted-clusterrole<br>  namespace: default<br>rules:<br>- apiGroups:<br>  - &quot;&quot;<br>  resources: [&quot;*&quot;]<br>  verbs:<br>  - get<br>  - list<br>  - watch<br>- apiGroups:<br>  - extensions<br>  resources: [&quot;*&quot;]<br>  verbs:<br>  - get<br>  - list<br>  - watch<br>- apiGroups:<br>  - apps<br>  resources: [&quot;*&quot;]<br>  verbs:<br>  - get<br>  - list<br>  - watch<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: ClusterRoleBinding<br>metadata:<br>  name: restricted-binding<br>roleRef:<br>  kind: ClusterRole<br>  name: view<br>  apiGroup: rbac.authorization.k8s.io<br>subjects:<br>- kind: ServiceAccount<br>  name: readonly-user<br>  namespace: kubernetes-dashboard</pre><pre>kubectl apply -f admin-user.yaml<br>kubectl apply -f readonly-user.yaml</pre><p>After applying User with the commands above you can create a token and log in to Dashboard with the following command.</p><pre>kubectl -n kubernetes-dashboard create token readonly-user</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/695/1*6J1-Tmn4XlM6x-q4rJUuYA.png" /></figure><p>And happy ending, now we can start using the dashboard :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G7LUmlNmRe4zjqp55spf2g.png" /></figure><p>You can read my other blog posts by clicking the link in the below.</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>PlainEnglish.io</em></strong></a><em>. Sign up for our </em><a href="http://newsletter.plainenglish.io/"><strong><em>free weekly newsletter</em></strong></a><em>. Follow us on </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>Twitter</em></strong></a>, <a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><strong><em>, </em></strong><a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong><em>YouTube</em></strong></a><strong><em>, and</em></strong><em> </em><a href="https://discord.gg/GtDtUAvyhW"><strong><em>Discord</em></strong></a><strong><em>.</em></strong><em> Interested in Growth Hacking? Check out </em><a href="https://circuit.ooo/"><strong><em>Circuit</em></strong></a><strong><em>.</em></strong></p><p><a href="https://medium.com/@emre.cakmak">Emre Çakmak - Medium</a></p><h3>References</h3><ul><li><a href="https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/">Deploy and Access the Kubernetes Dashboard</a></li><li><a href="https://github.com/kubernetes/dashboard">GitHub - kubernetes/dashboard: General-purpose web UI for Kubernetes clusters</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fbd29ab7363" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/kubernetes-management-dashboard-setup-in-aws-eks-elb-route-53-integrations-and-user-9fbd29ab7363">Kubernetes Management: Dashboard Setup in AWS EKS, ELB &amp; Route53</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monitoring Made Easy: The Power of AWS Chatbot and AWS CloudWatch Services]]></title>
            <link>https://aws.plainenglish.io/monitoring-made-easy-the-power-of-aws-chatbot-and-aws-cloudwatch-services-7210174bb4c5?source=rss-9e70f2260ca3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7210174bb4c5</guid>
            <category><![CDATA[aws-chatbot]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloudwatch]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Emre Çakmak]]></dc:creator>
            <pubDate>Thu, 06 Jul 2023 06:00:41 GMT</pubDate>
            <atom:updated>2023-08-15T14:57:02.465Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vN5MtSbUEBK_s3TICa-3KA.png" /></figure><h4>Introduction</h4><p>Hello, I’m <a href="https://www.linkedin.com/in/cakmak-emre/">Emre</a>. I work as a Cloud Native Engineer at <a href="https://bestcloudfor.me/">Bestcloudfor.me</a> and I’m part of a team that provides consulting services primarily in the AWS cloud domain to our clients.</p><p>In this article, we will explore the integration of <strong>Chatbot</strong> and <strong>CloudWatch</strong> for streamlined monitoring of your AWS resources. We’ll discuss how AWS Chatbot sends real-time notifications through popular platforms like Slack, while AWS CloudWatch provides comprehensive metrics and alarms. By combining these services, you can monitor and optimize your infrastructure with ease.</p><h4>AWS Chatbot</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LRVPFQcxvIll0ISK.png" /></figure><p>AWS Chatbot is a service that integrates with popular communication platforms like Slack, Microsoft Teams and AWS Chime, enabling you to receive important notifications about your AWS resources directly in your preferred chat application.</p><p>To set up this seamless integration, we’ll use AWS Simple Notification Service (SNS) topic. Here’s a step-by-step guide to configuring AWS Chatbot to send CPU usage alerts to your Slack channel, ensuring you never miss a critical update.</p><h4>Configuring AWS Chatbot Clients for Message Sending</h4><p>Below are some prerequisites you should have before you begin using AWS Chatbot:</p><ul><li>You have signed up for AWS and created an AWS Identity and Access Management (IAM) administrator user. If this is your first time using AWS, see <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_create-admin-group.html">Creating Your First Admin User and Group</a> in the <em>IAM User Guide</em>.</li><li>You have started using some AWS services. For more information about AWS services you can use with AWS Chatbot, see <a href="https://docs.aws.amazon.com/chatbot/latest/adminguide/related-services.html">Monitoring AWS services using AWS Chatbot</a>.</li><li>You have administrator privileges with your chosen chat client chat room, tenant, or workspace.</li><li>You understand AWS Chatbot’s permission schemes. For more information about AWS Chatbot’s permission schemes, see <a href="https://docs.aws.amazon.com/chatbot/latest/adminguide/understanding-permissions.html">Understanding permissions</a>.</li></ul><p>Once these requirements are met, you can log in to the Chatbot service and start setting up your first client.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mKGMZ5U3NhzIcC1mI51LrA.png" /></figure><p>After selecting the desired client, we will proceed from here, and in this blog post, I will be using Slack.</p><p>Once you choose the client, the Chatbot will redirect you to Slack to obtain the necessary permissions. You can proceed with the installation by clicking the “Allow” button on the screen below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NQfL0HW-wUghxknTlJ8gAg.png" /></figure><p>After successfully obtaining the necessary permissions, you will see the following screen. From this point onward, you need to define at least one channel to proceed with the installation. You can do this by clicking the “Configure new channel” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*syzVsD0o6zVrjqiYHHYeFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V_g9TxXvzjmTmdwJGjv8RQ.png" /></figure><p>Once you have selected the channel, you need to define the necessary IAM roles. If you already have a role, you can use it, or you can create a new role from the provided template.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kmp68nOSKVDLpRSeUX6niA.png" /></figure><p>Once you have defined the role, you need to create an SNS (Simple Notification Service) topic to receive alarms. You can accomplish this by utilizing the AWS SNS service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oym6UYdRDyhdzhHtyaMAKw.png" /></figure><p>You can proceed by selecting the type that suits your needs. I understand that you have chosen the “Standard” type. It’s important to note that selecting the “FIFO” type may lead to increased costs. For detailed information, you can refer to the following link: <a href="https://aws.amazon.com/sns/pricing/">AWS SNS Pricing</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M8hm8BENQ-yIkGSLhlwcFQ.png" /></figure><p>After selecting the topic, you can proceed by clicking “Configure,” and the Chatbot installation will be completed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_EhJ407qSjoTPO6N_-BTcw.png" /></figure><h3>AWS Cloudwatch</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*5S02goL1X8V28Xq8.jpg" /></figure><p>AWS CloudWatch is a comprehensive monitoring and observability service provided by AWS. It allows you to collect and analyze metrics, set alarms, and automatically react to changes in your AWS resources.</p><p>CloudWatch provides a wide range of services and metrics that can be leveraged to generate alarms and proactively respond to potential issues. For instance, when monitoring Amazon EC2 instances, CloudWatch can generate alarms based on key metrics such as CPU utilization, network traffic, and disk usage. This enables users to promptly identify and address instances that may be experiencing performance bottlenecks or resource constraints.</p><p>Moreover, CloudWatch can also monitor Amazon RDS database instances, allowing users to set alarms for crucial metrics such as latency, throughput, and CPU utilization. This capability ensures that database performance remains optimal and any deviations from desired thresholds can be promptly addressed.</p><p>In addition CloudWatch also supports alarms for AWS Lambda functions, enabling users to track metrics like invocation count, error rates, and duration. This helps ensure efficient execution of serverless functions and allows for quick identification and resolution of any potential issues.</p><p>Overall, AWS CloudWatch is a powerful monitoring service that empowers users to gain deep insights into their AWS resources. By leveraging its wide range of supported services and metrics, users can generate alarms and take proactive measures to optimize performance, enhance resource utilization, and ensure the smooth operation of their cloud infrastructure.</p><h4>Creating an AWS CloudWatch Alarm and Sending it to Slack using AWS Chatbot</h4><p>From the Cloudwatch interface we click to create a new alarm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Efr0nHeRIFcEX0KLVlWSEQ.png" /></figure><p>We continue by selecting the EC2 service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpiX5cwbbZH5QoKnj0NNTA.png" /></figure><p>Once you have selected the instance to monitor, you can choose the metric type. In this case, I understand that you have chosen the “CPUUtilization” metric. You can proceed with this selection. Feel free to choose the metric that is most suitable for your own scenario.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EO5u8mFl4NHpXFR4P1rTQQ.png" /></figure><p>After setting the threshold values, you can proceed to the “Actions” section and select the SNS topic that you have configured for the Chatbot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hvYmvahDeTmzx4AI7020tA.png" /></figure><p>I define the relevant triggers to receive notifications both in case of an alarm and when the alarm is resolved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19fdyrQIQ1j2YidX5kSUDA.png" /></figure><p>After setting the alarm name and description, we can create the alarm</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sptspXXqEC-9rx90Fe5PZQ.png" /></figure><p>Once you completed the all steps, you will receive an alarm when the corresponding instance exceeds the defined threshold.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vFM_2__spB6x6ZdHg1LYQg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QdisrqWODr8X00_mZBtPjw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_ERVrnUkhXdV99N5z7Wnw.png" /></figure><h4>Conclusion</h4><p>AWS Chatbot and AWS CloudWatch empower you to stay in control of your AWS resources by providing real-time notifications and robust monitoring capabilities. With AWS Chatbot’s integration with popular chat platforms and AWS CloudWatch’s comprehensive monitoring tools, you can ensure that you’re always aware of your instances’ CPU usage and take immediate action when necessary.</p><p>By combining these services with other AWS offerings, you can build a tailored monitoring solution that meets your unique requirements and simplifies your operations.</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>PlainEnglish.io</em></strong></a><em>. Sign up for our </em><a href="http://newsletter.plainenglish.io/"><strong><em>free weekly newsletter</em></strong></a><em>. Follow us on </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>Twitter</em></strong></a>, <a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><strong><em>, </em></strong><a href="https://www.youtube.com/channel/UCtipWUghju290NWcn8jhyAw"><strong><em>YouTube</em></strong></a><strong><em>, and</em></strong><em> </em><a href="https://discord.gg/GtDtUAvyhW"><strong><em>Discord</em></strong></a><strong><em>.</em></strong><em> Interested in Growth Hacking? Check out </em><a href="https://circuit.ooo/"><strong><em>Circuit</em></strong></a><strong><em>.</em></strong></p><h4>Resources</h4><ul><li><a href="https://aws.amazon.com/cloudwatch/getting-started/">Getting Started with Amazon CloudWatch - Amazon Web Services</a></li><li><a href="https://docs.aws.amazon.com/chatbot/latest/adminguide/what-is.html">What is AWS Chatbot?</a></li><li><a href="https://docs.aws.amazon.com/chatbot/latest/adminguide/getting-started.html">Getting started with AWS Chatbot</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7210174bb4c5" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/monitoring-made-easy-the-power-of-aws-chatbot-and-aws-cloudwatch-services-7210174bb4c5">Monitoring Made Easy: The Power of AWS Chatbot and AWS CloudWatch Services</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplifying EFS Migration: Harnessing the Power of DataSync]]></title>
            <link>https://towardsaws.com/simplifying-efs-migration-harnessing-the-power-of-datasync-15068547129c?source=rss-9e70f2260ca3------2</link>
            <guid isPermaLink="false">https://medium.com/p/15068547129c</guid>
            <category><![CDATA[aws-datasync]]></category>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[elastic-file-system]]></category>
            <dc:creator><![CDATA[Emre Çakmak]]></dc:creator>
            <pubDate>Thu, 06 Jul 2023 05:36:22 GMT</pubDate>
            <atom:updated>2023-08-20T08:15:03.447Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M7YLkCadT36m0094.jpg" /></figure><h4>Introduction</h4><p>Hello, I’m <a href="https://www.linkedin.com/in/cakmak-emre/">Emre</a>. I work as a Cloud Native Engineer at <a href="https://bestcloudfor.me/">Bestcloudfor.me</a> and I’m part of a team that provides consulting services primarily in the AWS cloud domain to our clients.</p><p>In this article, we’ll dive into EFS migration and introduce you to a hassle-free solution using AWS DataSync. If you’re looking for an easy way to move your data between different Amazon Elastic File System (EFS) instances, you’re in the right place. We’ll explore how DataSync can simplify the migration process, provide you with simple step-by-step instructions.</p><h4>AWS DataSync</h4><p>AWS DataSync is a secure, online service that automates and accelerates moving data between on premises and AWS Storage services. DataSync can copy data between Network File System (NFS) shares, Server Message Block (SMB) shares, Hadoop Distributed File Systems (HDFS), self-managed object storage, AWS Snowcone, Amazon Simple Storage Service (Amazon S3) buckets, Amazon Elastic File System (Amazon EFS) file systems, Amazon FSx for Windows File Server file systems, Amazon FSx for Lustre file systems, Amazon FSz for OpenZFS file systems, and Amazon FSx for NetApp ONTAP file systems.</p><p>DataSync service provides an ideal solution for a range of use cases, including data migration to the cloud, content distribution, disaster recovery, data backup, and data syncing for distributed applications. Whether it’s moving large datasets, replicating data for data protection, or ensuring data consistency across multiple locations, DataSync simplifies and optimizes data transfer operations, saving time and resources for businesses of all sizes.</p><h4>AWS EFS</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*ltfjkWfTk3pNuJjx.png" /></figure><p>Amazon EFS is a simple, serverless, elastic, set-and-forget file system that automatically grows and shrinks as you add and remove files with no need for management or provisioning. You can use Amazon EFS with Amazon EC2, AWS Lambda, Amazon ECS, Amazon EKS and other AWS compute instances, or with on-premises servers.</p><h4>Pros of AWS EFS:</h4><ol><li><strong>Scalability</strong>: EFS automatically scales to accommodate growing data storage needs without requiring any manual intervention. It provides virtually unlimited storage capacity.</li><li><strong>Data Persistence</strong>: EFS ensures data durability by automatically replicating files across multiple Availability Zones within a region.</li><li><strong>Compatibility</strong>: EFS is compatible with popular file system interfaces such as Network File System (NFS), allowing existing applications and tools to integrate easily without the need for extensive modifications.</li></ol><h4>Cons of AWS EFS:</h4><ol><li><strong>Performance Limitations</strong>: While EFS offers high scalability and elasticity, it may not provide the same level of performance as other storage options, especially for workloads with high I/O demands. Applications requiring extremely low latency or high throughput may need to consider alternative storage solutions.</li><li><strong>Cost</strong>: EFS can be cost-effective for workloads with moderate storage requirements. However, for applications with high throughput or intense I/O operations, the associated costs may be higher compared to other AWS storage services.</li></ol><p>If you need to move all the data within your EFS to another EFS for some reason, you can easily accomplish this task using the DataSync service. DataSync simplifies the process of transferring data between different storage systems and makes it as easy as a piece of cake.</p><h4>EFS-to-EFS Transfer with AWS DataSync</h4><p>If you have two EFS (Elastic File System), let’s say EFS-1 and EFS-2, and you want to move the data from EFS-1 to EFS-2, you can use the following steps:</p><p>Let’s first take a look at how these two EFS instances currently appear, and then we can proceed to the DataSync section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bXMnYet9VcCtKRW0X4IhcA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bsL25qd5F8AmljkS7_KgWw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_WDEoi-aQOTIvWv2HMrIWA.png" /></figure><p>As you see from the screenshots we have <strong>fancy-loog-file.zip</strong> file in efs-1 and efs-2 looks empty.</p><p>Go to <strong>AWS DataSync</strong> Dashboard and choose Locations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wqYjzq6O1Bq9PKu_QVJ1vw.png" /></figure><p>Once you open Locations you will see something like that. We continue by clicking on the Create location button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SkXNX4oexMNUdJvGElJzSw.png" /></figure><p>Choose EFS file system option and set EFS settings like subnet and security group to DataSync use to access your EFS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ojA_sjL00nbj-6RH7uKPIA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6E2W0TkubRzW-yy44xajCw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UtrawUv7dnsHFOn4fttsyw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EqrcoGWQ4UQdDRzdmn7RVg.png" /></figure><p>If you set your EFS locations successfully, you should see a screen like this, then click on the “Tasks” button on the left.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MjEfnqewLWB-NpxvCPjZZQ.png" /></figure><p>In the Task creation section you will be asked some configurations. Here you need to enter your source and destination. We continue by selecting efs-1 as source and efs-2 as destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7yeFdRGzuLARlMyQK85UrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KXdm71xw_BgM0XiffBopvA.png" /></figure><p>After setting these, we name our task and specify what we want to be moved and how. Here you can exlcude some paths, create a task that will run regularly or enable logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SUsCG9FvQy4rJCNC5ozwag.png" /></figure><p>Once we have created our task, we can start the transfer by pressing “Start” from the top menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNaH29-P3qlqWd_auhIFUQ.png" /></figure><p>You can follow the progress of the task from the task history. Here, it may take a while for the task to launch, if you see success after the data migration and verifty processes it means that you have successfully migrated your EFS data to destination EFS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8-iLkZj9_ZHHj_6Vs7qA8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Knz0cNYxXw0N4z_aMK_4-A.png" /></figure><p>As you can see from the image, our data was successfully moved to efs-2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D__NwS70a8orlrSe0OXzTg.png" /></figure><h4>Conclusion</h4><p>In conclusion, AWS DataSync provides a powerful solution for EFS to EFS migration, enabling seamless and efficient data transfers between Elastic File System (EFS) instances. Throughout this blog post, we explored the key benefits and features of AWS DataSync and discussed its role in simplifying the migration process.</p><p>It’s important to note that AWS DataSync is a fully managed service, eliminating the need for manual configuration and maintenance. This allows organizations to focus on their core business activities rather than managing complex migration processes. AWS handles the underlying infrastructure and ensures the security, scalability, and availability of the DataSync service.</p><h4>Resources</h4><ul><li><a href="https://docs.aws.amazon.com/datasync/latest/userguide/what-is-datasync.html">What is AWS DataSync?</a></li><li><a href="https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html">What is Amazon Elastic File System?</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15068547129c" width="1" height="1" alt=""><hr><p><a href="https://towardsaws.com/simplifying-efs-migration-harnessing-the-power-of-datasync-15068547129c">Simplifying EFS Migration: Harnessing the Power of DataSync</a> was originally published in <a href="https://towardsaws.com/">Towards AWS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking Application Performance with SigNoz: Empower Your Monitoring Game!]]></title>
            <link>https://medium.com/@emre.cakmak/unlocking-application-performance-with-signoz-empower-your-monitoring-game-f5640db009ba?source=rss-9e70f2260ca3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5640db009ba</guid>
            <category><![CDATA[application-performance]]></category>
            <category><![CDATA[new-relic]]></category>
            <category><![CDATA[signoz]]></category>
            <category><![CDATA[apm]]></category>
            <category><![CDATA[datadog]]></category>
            <dc:creator><![CDATA[Emre Çakmak]]></dc:creator>
            <pubDate>Sun, 21 May 2023 13:15:28 GMT</pubDate>
            <atom:updated>2023-05-21T13:15:28.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z_ANVuSPMhpWtH14.png" /></figure><h3>Introduction</h3><p>Hello, I’m <a href="https://www.linkedin.com/in/cakmak-emre/">Emre</a>. I work as a Cloud Native Engineer at <a href="https://bestcloudfor.me/">Bestcloudfor.me</a> and I’m part of a team that provides consulting services primarily in the AWS cloud domain to our clients.</p><p>In this article, we’ll explore <strong>SigNoz</strong>, a powerful open-source tool for Application Performance Monitoring (APM). With the increasing complexity of modern applications, monitoring performance is crucial. SigNoz provides real-time metrics, distributed tracing, and root cause analysis to help developers and operations teams identify bottlenecks, troubleshoot issues, and optimize application performance.</p><p><a href="https://signoz.io/"><strong>SigNoz</strong></a> is an <a href="https://github.com/SigNoz/signoz">open-source</a> Application Performance Monitoring (APM) tool that provides end-to-end observability for modern applications. Designed with a microservices architecture in mind, SigNoz can monitor the performance of your entire stack, from frontend to backend, and all the way down to the database.</p><p>SigNoz provides a range of features that make it an ideal choice for teams that want visibility into their applications’ performance. It has a user-friendly interface that allows you to easily visualize metrics and diagnose issues. The platform is built to scale, so it can handle large volumes of data and support multiple users.</p><p>SigNoz supports a wide range of technologies, including Java, Python, Node.js, and Go. It is compatible with popular frameworks such as Spring Boot, Flask, and Express. The platform integrates with other popular tools such as Grafana, Prometheus, making it easier to get started with observability.</p><p>SigNoz provides three different versions: community, cloud, and enterprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DaA8-9sd0-3jdZi24ybBVA.png" /><figcaption>SigNoz Pricing</figcaption></figure><p>The community version is suitable for small teams and personal projects, while the cloud version is suitable for teams of all sizes and provides more features than the community version.</p><p>The enterprise version is suitable for large enterprises and provides all the features of the cloud version, as well as customization options to fit the specific needs of your organization. Support is provided by SigNoz for both the cloud and enterprise versions.</p><h4>Installation</h4><p>SigNoz supports three different types of installations: Docker standalone, Docker Swarm, and Kubernetes.</p><p>Each installation type has its own benefits and drawbacks, so it’s important to choose the one that best fits your needs.</p><ul><li>Docker standalone installation is the easiest and quickest way to get started with SigNoz. It’s a good choice if you want to quickly set up a local instance of SigNoz for testing and development purposes.</li><li>Docker Swarm installation is a good choice if you need to run SigNoz in a production environment. It allows you to easily manage and scale your SigNoz deployment.</li><li>Kubernetes installation is the most powerful and flexible installation option. It allows you to deploy SigNoz to a Kubernetes cluster and take advantage of Kubernetes’ advanced features for managing and scaling applications.</li></ul><p>Regardless of the installation type you choose, SigNoz provides detailed documentation to help you get started quickly. Check this <a href="https://signoz.io/docs/install/">documentation</a> for detailed informations.</p><p>In this blog post, I chose the Docker standalone installation type to set up SigNoz. To begin, we need an instance to run all environments.</p><h4>Prerequisites</h4><ul><li>A Linux or macOS machine. <strong>Microsoft Windows</strong> is not officially supported.</li><li>On macOS, you must manually install <a href="https://docs.docker.com/engine/install/">Docker Engine</a> before you run the install script. The install script automatically installs Docker Engine on Linux.</li><li>A minimum of <strong>4GB of memory</strong> must be allocated to Docker.</li><li><a href="https://desktop.github.com/">Git client</a></li><li>Ensure that the ports 3301, 4317 and 4318 are open on the machine where you install SigNoz.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MKYXyuFbfbIfY1HxxrPOrg.png" /><figcaption>Ubuntu Instance &amp; Security Settings</figcaption></figure><p>Once the instance is ready, all you need to do to install SigNoz is to run the prepared script with the following command.</p><pre>git clone -b main https://github.com/SigNoz/signoz.git &amp;&amp; cd signoz/deploy/<br><br>./install.sh</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4RyuM3W9xyuaytOXvgfvbA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PSqe8ym5ofoy6TYaOayLLA.png" /></figure><p>To verify the installation of SigNoz, run the following command:</p><pre>docker ps</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QO4eYL0XjL9pgWuXYwWGXg.png" /></figure><p>If you see this output, the installation is complete. After that we can preprare our first application to test SigNoz features.</p><p>Once SigNoz is installed, an admin user can create their user by going <a href="http://server-ip:3301/">http://SERVER-IP:3301</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ml8jtJhTmXxrjnJFhg9BQ.png" /><figcaption>Creating first user</figcaption></figure><p>In addition to providing a range of installation options, SigNoz also offers several example applications that are automatically deployed to help you get started with testing and experimentation.</p><h4>Screenshoots from example applications</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L1h0I32lpGD6niDuBV3C-w.png" /><figcaption>Services</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JPPRCNZ_0wHoWHdMal6tPA.png" /><figcaption>Traces</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aibaiv-z28d6MFh_mUp5sg.png" /><figcaption>Logs</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SnH7OLpr8eVRpaJScDkQug.png" /><figcaption>Dashboards</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d2uoOq72jt34BVMDFMFZbw.png" /><figcaption>Service Map</figcaption></figure><h4>Alert Mechanisim of SigNoz</h4><p>With SigNoz, not only can you gain valuable insights into your application’s performance, but you can also set up performance alerts to proactively detect and address issues.</p><p>SigNoz allows you to configure customized alerts based on specific performance thresholds, such as response time or error rate. One powerful feature is the ability to integrate SigNoz with Slack using webhooks. By setting up a webhook integration, you can automatically receive performance alerts in your Slack workspace, ensuring that your team stays informed and can take immediate action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZrFbcW8iknU-dkXC5GpFaA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mw9DPEjMzRjkKqT18tnt_A.png" /><figcaption>An example slack alert from SigNoz</figcaption></figure><h4>How to integrate SigNoz with your application.</h4><p>SigNoz supports various instrumentation methods depending on your application’s programming language and framework. You’ll need to add SigNoz’s monitoring agent or SDK to your application’s codebase. This will allow SigNoz to collect metrics, traces, and other performance data.</p><p>In this blog post, I will be walking through the process using OpenTelemetry .NET instrumentation.</p><p>First install .NET 6.0 environments</p><ul><li>Add OpenTelemetry package in your .NET application<a href="https://signoz.io/blog/opentelemetry-dotnet/#opentelemetry-net-instrumentation-for-tracing">​</a></li></ul><pre>dotnet new mvc -n Org.MyWebApp --no-https<br><br>dotnet add package OpenTelemetry.Extensions.Hosting --prerelease<br>dotnet add package OpenTelemetry.Instrumentation.AspNetCore --prerelease<br>dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol --prerelease</pre><ul><li>Configure OpenTelemetry to send logs to SigNoz</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvcLzwIjegvDT6xiJWyphw.png" /></figure><p>Run the application.</p><pre>dotnet run</pre><p>If the integration process is successful, you will be able to see your application on the SigNoz dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UCbur3cb4g3wWlKbqpCL2g.png" /></figure><p>After that, it’s up to your needs. You can add as many dashboards as you want and track your application’s metrics in real-time from the SigNoz interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wE-iTwq8NuLy7d5mVq7lfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fPSN5lVMOOLL62xN5DjamA.png" /></figure><h4>Alternatives</h4><p>SigNoz APM has alternatives, and some of the most well-known ones are</p><ol><li><a href="https://www.datadoghq.com/"><strong>Datadog</strong></a>: Datadog is a comprehensive monitoring and analytics platform that provides end-to-end visibility into your applications and infrastructure. It offers a wide range of features, including APM, infrastructure monitoring, log management, and customizable dashboards.</li><li><a href="https://newrelic.com/"><strong>New Relic</strong></a>: New Relic is a leading APM solution that helps monitor and optimize the performance of modern applications. It offers features such as real-time application monitoring, distributed tracing, and advanced analytics, enabling organizations to gain deep insights into their application’s behavior.</li></ol><p>To determine which tool is best suited for your needs, it’s important to consider your requirements, budget, and priorities.</p><h4>Conclusion</h4><p>In conclusion, SigNoz is a powerful open-source APM tool that enables organizations to monitor and optimize application performance. With real-time monitoring, distributed tracing, and root cause analysis, SigNoz offers valuable insights for efficient troubleshooting.</p><p>Its user-friendly interface, scalability, and flexibility make it a valuable asset for developers and operations teams. By leveraging SigNoz, organizations can proactively detect issues, identify bottlenecks, and deliver exceptional user experiences. Consider integrating SigNoz into your application stack to gain deeper visibility and take control of your performance journey.</p><h4>References</h4><ul><li><a href="https://signoz.io/docs/">https://signoz.io/docs/</a></li><li><a href="https://github.com/SigNoz/signoz">https://github.com/SigNoz/signoz</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5640db009ba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Container Security: Exploring Falco’s Features and Threat Detection Capabilities]]></title>
            <link>https://medium.com/@emre.cakmak/container-security-exploring-falcos-features-and-threat-detection-capabilities-ff8bcca8cd6?source=rss-9e70f2260ca3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff8bcca8cd6</guid>
            <category><![CDATA[falco]]></category>
            <category><![CDATA[container-security]]></category>
            <category><![CDATA[runtime-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Emre Çakmak]]></dc:creator>
            <pubDate>Sat, 20 May 2023 18:28:19 GMT</pubDate>
            <atom:updated>2023-05-20T18:28:19.254Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*Ov1w7H-I8CGta8b6B29anQ.png" /><figcaption>Falco illustration from <a href="https://falco.org/about/">Falco’s website</a>.</figcaption></figure><h4>Introduction</h4><p>Hello, I’m <a href="https://www.linkedin.com/in/cakmak-emre/">Emre</a>. I work as a Cloud Native Engineer at <a href="https://bestcloudfor.me/">Bestcloudfor.me</a> and I’m part of a team that provides consulting services primarily in the AWS cloud domain to our clients.</p><p>In this article, I would like to talk to you about <strong>Falco</strong>, an effective tool for container security. With the rapid proliferation of containerized applications, security concerns have also been on the rise. This is where the importance of a runtime security tool like Falco comes into play.</p><p>Kubernetes security is a challenging topic due to the dynamic relationships between different application layers and components. To overcome this difficulty, a runtime security tool called <strong>Falco</strong> has been developed by <a href="https://sysdig.com/opensource/falco/"><strong>Sysdig</strong></a>.</p><p>Falco is an <a href="https://github.com/falcosecurity/falco"><strong>open-source</strong></a> tool designed to provide security for applications running in your Kubernetes cluster. It uses a set of rules to monitor activities and behaviors to detect potential security breaches.</p><p>The key features of Falco include working as a runtime security tool that monitors activities of applications running in your Kubernetes cluster. It comes with customizable rules in YAML format. When any attack or misconfigured application is detected, it records events and sends notifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*49ocZxCbZQJ-kYKBhsnqYA.png" /><figcaption>Features from from <a href="https://sysdig.com/opensource/falco/">Sysdig’s website</a>.</figcaption></figure><h4>Alert mechanism of Falco</h4><p>Falco comes with a set of predefined alarm rules that monitor the activities of applications running in your Kubernetes cluster and send alerts in case of abnormal behavior. Some examples of these alarm rules are:</p><ol><li>Sensitive file access: Sends an alert when access to sensitive files is detected.</li><li>Shell in Kubernetes Pod: Sends an alert when a shell is detected running within Kubernetes pods.</li></ol><p>These alarm rules can be easily customized or expanded by editing Falco’s YAML-based rules. When Falco detects unusual activities, it logs these activities and sends notifications to users. Notifications can be sent to Slack, email, Syslog, or any other specified destination. Check this <a href="https://falco.org/blog/extend-falco-outputs-with-falcosidekick/">link</a> to explore more supported destinations.</p><p>Please note that Falco provides the flexibility to tailor the rules according to specific security requirements, allowing you to adapt the monitoring system to your needs and enhance your overall security posture.</p><p>You can learn more by visiting Falco’s <a href="https://falco.org/docs/rules/">docs</a>.</p><h4>Installing and Receiving Alarms with Falco</h4><p>Falco provides different installation methods and if you refer to the installation <a href="https://falco.org/docs/getting-started/installation/">documentation</a>, you can find detailed information about each option. Falco does recommend the direct installation on the host system as the preferred method.</p><blockquote>The most secure way to run Falco is to install Falco directly on the host system so that Falco is isolated from Kubernetes in the case of compromise. Then the Falco alerts can be consumed through read-only agents running in Kubernetes.</blockquote><p>We will proceed with the installation of Falco as a DaemonSet on a Kubernetes cluster using a third Party method.</p><p>To install Falco, you need a running Kubernetes cluster. Additionally, this document utilizes the <a href="https://helm.sh/docs/intro/install/">Helm</a> package manager for the installation steps. If you wish to receive notifications through Falco, there are various methods available. However, in this document we will use <a href="https://api.slack.com/messaging/webhooks">Slack</a> for demonstration purposes.</p><p>After setting up the environment and installing the necessary tools, here are the steps you need to take:</p><pre>kubectl create ns falco</pre><pre>helm repo add falcosecurity https://falcosecurity.github.io/charts<br><br>helm repo update<br><br>helm install falco -n falco falcosecurity/falco \ <br> --set auditLog.enabled=true \ <br> --set falco.jsonOutput=true \ <br> --set falco.fileOutput.enabled=true \ <br> --set falcosidekick.enabled=true \<br> --set falcosidekick.config.slack.webhookurl=&quot;&lt;YOUR-SLACK-WEBHOOK-ENDPOINT&gt;&quot;</pre><p>To verify the installation of Falco, run the following command:</p><pre>kubectl get pods -n falco</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*II8YDYwULfFnowS-rOwQiA.png" /></figure><p>If you see this output, the installation is complete. After that we can do some risky operations and complete the tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*tpApylKHgNTPNWX-cJcyUA.png" /><figcaption>Example of creating files in /etc directory</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*8W7Fbu4AgMaSJjtyV3Ic0Q.png" /><figcaption>Example of open shell in running pod</figcaption></figure><p><strong>Alternatives</strong></p><p>There are some alternatives to Falco for monitoring runtime malicious activities for Container Security:</p><ol><li><a href="https://sysdig.com/products/secure/">Sysdig Secure</a>: Sysdig Secure provides a range of tools for monitoring security in container environments and detecting threats. Sysdig has a runtime security engine similar to Falco, providing the ability to detect anomalies and threats in the system.</li><li><a href="https://www.paloaltonetworks.com/prisma/cloud">Twistlock</a> (Palo Alto Networks — Prisma Cloud): Twistlock is a popular tool that provides a comprehensive platform for container security. It offers runtime detection of malicious activities, identification of weak configurations, and prevention of breaches.</li></ol><p>These tools are some commonly used alternatives for monitoring and detecting malicious activities in container environments. To determine which tool is best suited for your needs, it’s important to consider your requirements, budget, and priorities.</p><h4>Conclusion</h4><p>To sum up, Falco is an essential tool for securing Kubernetes clusters. It provides us with confidence in the security of our applications within the cluster and alerts us to any abnormal activities.</p><p>Falco acts as a detection tool and sends alerts regarding the detected events, <strong>but it does not actively prevent or block activities.</strong> Therefore Falco can be used in conjunction with other tools to take action in response to the identified security issues.</p><p>Preventing such malicious activities will be the subject of another article :)</p><h4>References</h4><ul><li><a href="https://falco.org/docs/">https://falco.org/docs/</a></li><li><a href="https://falco.org/blog/extend-falco-outputs-with-falcosidekick/">https://falco.org/blog/extend-falco-outputs-with-falcosidekick/</a></li><li><a href="https://sysdig.com/opensource/falco/">https://sysdig.com/opensource/falco/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff8bcca8cd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>