
Michal Salanci
Senior DevOps Engineer in Deutsche Telekom Systems Solutions, Slovakia
Košice, Slovakia
Actions
My name is Michal Salanci, and I am a Senior Cloud Engineer from Slovakia. For many years, I worked as a Data Center network engineer, handling various networking equipment such as routers, switches, firewalls, load balancers, and more. In 2021, I made a career shift towards AWS, where I primarily focus on networking, security, serverless and containers. I am AWS Community Builder in category Containers and also Leader of AWS User Group Kosice Slovakia and Reykjavik Iceland.
https://michal-salanci.s3.eu-central-1.amazonaws.com/index.html
Area of Expertise
Topics
Instance Store in Fargate: Efficient Main-Sidecar container communication?
Let's explore the practicality of using instance store for communication between main and sidecar containers in AWS Fargate tasks. This presentation will demonstrate how instance store not only facilitates efficient data exchange but also enhances performance without being an overkill and still cost effective. We will cover the architectural setup, benefits, and real-world application scenarios where instance store proves to be a robust solution.
More Network Security: Forward Proxy on AWS Network Firewall & Fargate
We've crafted a robust, scalable forward proxy solution integrating AWS Network Firewall, Squid Proxy, Fluentbit, Dnsmasq, and Telegraf - all components in containers.
🌐 The AWS Network Firewall serves as a transparent proxy, applying stateful and stateless whitelist blocking rules.
🦑 Squid Proxy, operating as an explicit proxy, is deployed in an ECS container alongside Fluentbit, which forwards logs to AWS CloudWatch.
🔧 Dnsmasq, also in an ECS container, resolves DNS issues related to Let's Encrypt, ensuring smooth SSL/TLS certificate management.
📈 Telegraf monitors both proxy types, sending real-time performance metrics to Grafana and triggering AWS CloudWatch alarms for proactive issue resolution.
All in containers, and managed entirely by Amazon Fargate, simplifies container orchestration. The entire system is further streamlined through automation via a CI/CD pipeline, enhancing security, efficiency, and cost-effectiveness while maintaining excellent visibility and control.
Monitor AWS network resources with Telegraf, managed by Fargate
Let's explore the robust capabilities of Telegraf by InfluxData, for monitoring network resources within AWS. This presentation will detail the deployment of Telegraf within a Fargate container, illustrating the seamless integration of data into CloudWatch metrics. I will also demonstrate how to effectively transition from metrics to CloudWatch alarms and conclude with the visualization of these elements in Grafana. It's a real live example how to combine Telegraf as a 3rd party solution running in Fargate, with CloudWatch.
Goodbye server: Going serverless with AWS
Refactoring to serverless doesn't have to be just a thousands of lines of code, or heavy duty lambda functions. You can leverage on resources that AWS already offers. This is a real project example of going serverless the robust and upgrade-unfriendly application running on EC2 and S3 - to a modern, serverless, containerized, CICD automated and ops ready using AWS Network Firewall, ECS/Fargate and instance store.

Michal Salanci
Senior DevOps Engineer in Deutsche Telekom Systems Solutions, Slovakia
Košice, Slovakia
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top