<?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 Alexander Ilves on Medium]]></title>
        <description><![CDATA[Stories by Alexander Ilves on Medium]]></description>
        <link>https://medium.com/@alexanderilves?source=rss-1e687b795e7b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AfUZ8Ls8QB6DBNWYvDUcvw.png</url>
            <title>Stories by Alexander Ilves on Medium</title>
            <link>https://medium.com/@alexanderilves?source=rss-1e687b795e7b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:45:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexanderilves/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[API Gateway vs Caddy/Nginx: Security and Reliability in Modern Web Application Development]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://awstip.com/api-gateway-vs-caddy-security-and-reliability-in-modern-web-application-development-7652847cd43b?source=rss-1e687b795e7b------2"><img src="https://cdn-images-1.medium.com/max/680/0*q2796iInI8c0Rr3I.png" width="680"></a></p><p class="medium-feed-snippet">My Series &#x201C;Golden pipeline&#x201D;&#x200A;&#x2014;&#x200A;Each POC represents my vision of a modern enterprise platform, exploring a different platform engineering&#x2026;</p><p class="medium-feed-link"><a href="https://awstip.com/api-gateway-vs-caddy-security-and-reliability-in-modern-web-application-development-7652847cd43b?source=rss-1e687b795e7b------2">Continue reading on AWS Tip »</a></p></div>]]></description>
            <link>https://awstip.com/api-gateway-vs-caddy-security-and-reliability-in-modern-web-application-development-7652847cd43b?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7652847cd43b</guid>
            <category><![CDATA[aws-cloudfront]]></category>
            <category><![CDATA[aws-api-gateway]]></category>
            <category><![CDATA[security-audit]]></category>
            <category><![CDATA[api-gateway]]></category>
            <category><![CDATA[web-security]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 20:54:23 GMT</pubDate>
            <atom:updated>2026-11-16T13:30:32.408Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Development and Operations Have Different Goals — and Why Mixing Them Hurts Both]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alexanderilves.medium.com/why-development-and-operations-have-different-goals-and-why-mixing-them-hurts-both-96a9b60d7d6d?source=rss-1e687b795e7b------2"><img src="https://cdn-images-1.medium.com/max/700/1*9LlpKb_rRTF87K7sEoaRxQ.jpeg" width="700"></a></p><p class="medium-feed-snippet">&#x201C;Why One Person Can&#x2019;t Optimize for Speed and Stability at the Same Time&#x201D;</p><p class="medium-feed-link"><a href="https://alexanderilves.medium.com/why-development-and-operations-have-different-goals-and-why-mixing-them-hurts-both-96a9b60d7d6d?source=rss-1e687b795e7b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alexanderilves.medium.com/why-development-and-operations-have-different-goals-and-why-mixing-them-hurts-both-96a9b60d7d6d?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/96a9b60d7d6d</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[itsm]]></category>
            <category><![CDATA[security-audit]]></category>
            <category><![CDATA[cmmi]]></category>
            <category><![CDATA[devops-practice]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Thu, 01 Jan 2026 19:06:06 GMT</pubDate>
            <atom:updated>2026-01-01T19:06:06.139Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Управление рисками: SWOT анализ]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alexanderilves.medium.com/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%80%D0%B8%D1%81%D0%BA%D0%B0%D0%BC%D0%B8-swot-%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8%D0%B7-63c16f91b86a?source=rss-1e687b795e7b------2"><img src="https://cdn-images-1.medium.com/max/1024/0*hxpuBRisJoLP5ENP.jpg" width="1024"></a></p><p class="medium-feed-snippet">&#x412; &#x43F;&#x440;&#x435;&#x434;&#x44B;&#x434;&#x443;&#x449;&#x435;&#x439; &#x438;&#x441;&#x442;&#x43E;&#x440;&#x438;&#x438; &#x43C;&#x44B; &#x440;&#x430;&#x441;&#x441;&#x43C;&#x43E;&#x442;&#x440;&#x435;&#x43B;&#x438; &#x43E;&#x431;&#x449;&#x443;&#x44E; &#x442;&#x435;&#x43E;&#x440;&#x438;&#x44E; &#x443;&#x43F;&#x440;&#x430;&#x432;&#x43B;&#x435;&#x43D;&#x438;&#x44F; &#x440;&#x438;&#x441;&#x43A;&#x430;&#x43C;&#x438;, &#x438; &#x43C;&#x435;&#x442;&#x43E;&#x434;&#x44B; &#x430;&#x43D;&#x430;&#x43B;&#x438;&#x437;&#x430; &#x438; &#x443;&#x43F;&#x440;&#x430;&#x432;&#x43B;&#x435;&#x43D;&#x438;&#x44F; &#x440;&#x438;&#x441;&#x43A;&#x430;&#x43C;&#x438;.</p><p class="medium-feed-link"><a href="https://alexanderilves.medium.com/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%80%D0%B8%D1%81%D0%BA%D0%B0%D0%BC%D0%B8-swot-%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8%D0%B7-63c16f91b86a?source=rss-1e687b795e7b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alexanderilves.medium.com/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%80%D0%B8%D1%81%D0%BA%D0%B0%D0%BC%D0%B8-swot-%D0%B0%D0%BD%D0%B0%D0%BB%D0%B8%D0%B7-63c16f91b86a?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/63c16f91b86a</guid>
            <category><![CDATA[управление-рисками]]></category>
            <category><![CDATA[risks-and-benefits]]></category>
            <category><![CDATA[swot-analysis]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Sun, 27 Apr 2025 19:13:04 GMT</pubDate>
            <atom:updated>2025-04-27T20:45:50.089Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Управление рисками]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alexanderilves.medium.com/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%80%D0%B8%D1%81%D0%BA%D0%B0%D0%BC%D0%B8-44aa3b07b302?source=rss-1e687b795e7b------2"><img src="https://cdn-images-1.medium.com/max/660/0*LqpqJwZzYsjKHkBN.png" width="660"></a></p><p class="medium-feed-snippet">&#x412; &#x441;&#x43E;&#x432;&#x440;&#x435;&#x43C;&#x435;&#x43D;&#x43D;&#x43E;&#x43C; &#x43C;&#x438;&#x440;&#x435; &#x43D;&#x435;&#x43E;&#x43F;&#x440;&#x435;&#x434;&#x435;&#x43B;&#x451;&#x43D;&#x43D;&#x43E;&#x441;&#x442;&#x44C; &#x441;&#x442;&#x430;&#x43B;&#x430; &#x43F;&#x43E;&#x441;&#x442;&#x43E;&#x44F;&#x43D;&#x43D;&#x44B;&#x43C; &#x441;&#x43F;&#x443;&#x442;&#x43D;&#x438;&#x43A;&#x43E;&#x43C; &#x431;&#x438;&#x437;&#x43D;&#x435;&#x441;&#x430;, &#x442;&#x435;&#x445;&#x43D;&#x43E;&#x43B;&#x43E;&#x433;&#x438;&#x439;, &#x444;&#x438;&#x43D;&#x430;&#x43D;&#x441;&#x43E;&#x432;&#xA0;..</p><p class="medium-feed-link"><a href="https://alexanderilves.medium.com/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%80%D0%B8%D1%81%D0%BA%D0%B0%D0%BC%D0%B8-44aa3b07b302?source=rss-1e687b795e7b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alexanderilves.medium.com/%D1%83%D0%BF%D1%80%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D1%80%D0%B8%D1%81%D0%BA%D0%B0%D0%BC%D0%B8-44aa3b07b302?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/44aa3b07b302</guid>
            <category><![CDATA[качественный-анализ]]></category>
            <category><![CDATA[количественный-анализ]]></category>
            <category><![CDATA[риски]]></category>
            <category><![CDATA[управление-рисками]]></category>
            <category><![CDATA[управление-проектами]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Fri, 25 Apr 2025 14:05:17 GMT</pubDate>
            <atom:updated>2025-04-27T20:47:37.726Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Cilium: High-Performance Networking and Security for Kubernetes]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alexanderilves.medium.com/cilium-high-performance-networking-and-security-for-kubernetes-d6ffcdd14ea4?source=rss-1e687b795e7b------2"><img src="https://cdn-images-1.medium.com/max/1600/0*qGMGvvCdiLh87Cif.png" width="1600"></a></p><p class="medium-feed-snippet">Cilium is a powerful networking plugin that leverages eBPF to manage networking, security, and observability&#xA0;&#x2026;</p><p class="medium-feed-link"><a href="https://alexanderilves.medium.com/cilium-high-performance-networking-and-security-for-kubernetes-d6ffcdd14ea4?source=rss-1e687b795e7b------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alexanderilves.medium.com/cilium-high-performance-networking-and-security-for-kubernetes-d6ffcdd14ea4?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6ffcdd14ea4</guid>
            <category><![CDATA[k8s-cluster-management]]></category>
            <category><![CDATA[k8s-networking]]></category>
            <category><![CDATA[k8s-security]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cilium]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Tue, 01 Apr 2025 12:54:11 GMT</pubDate>
            <atom:updated>2025-04-27T20:49:50.461Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Azure Name Resolving]]></title>
            <link>https://alexanderilves.medium.com/azure-name-resolving-fdf0d25e1a1a?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdf0d25e1a1a</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[container-registry]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Wed, 01 May 2024 14:23:09 GMT</pubDate>
            <atom:updated>2024-06-07T07:54:53.419Z</atom:updated>
            <content:encoded><![CDATA[<h3>DNS Name Resolving</h3><p>Name resolution problem in private and public DNS zones (applies not only to the Azure cloud)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*qEI8qO51UL_DhnLb" /><figcaption>Azure Name Resolving</figcaption></figure><p><strong>Problem Description:</strong></p><p>When you add a new Azure service (such as Azure Container Registry) with a private access type, all nodes in your cloud network either stop resolving other private DNS zones (if they exist) or are unable to resolve names in the newly created private DNS zone and cannot connect. to a newly added service (for example, Azure Container Registry).</p><p><strong>In more detail the problem looks like this:</strong><br>When adding a new Azure Service (for example Azure Container registry), we must specify the network access type for the service:<br>- <strong>Public Access</strong>. In this case, access to the service will be performed through the Public IP address and Public network. Of course, we can limit access to our repository by specifying the allowed IP addresses of clients and their accounts, but the traffic will pass through all public networks, and this is not always permissible for security reasons;<br><strong>- Private Access</strong>. In this case, access to the service will be performed only through the internal Microsoft network, which is more secure for our network. In this case, we must create a Private Endpoint for our service and publish its Private IP address in the Private DNS zone.</p><p>Then the last part of the task remains: connecting this Private DNS zone to the client’s network settings so that it can resolve both public and private DNS names.</p><p><strong>Connecting Private DNS zones to the client’s network settings</strong></p><p>To add another DNS resolver to the client’s settings, we can add it to the Virtual Network/DNS Servers settings where our client is hosted. When adding a new server to the existing list of DNS servers, we must remember that in this case the order of the servers matters. And this is a very important issue for our discussion — <em>the name resolving procedure on the client side</em>.</p><p><strong>The procedure for performing Name Resolving on the client side:</strong></p><ol><li>The client sends a domain name resolution request to the first DNS-resolver server in its DNS-resolvers list.</li><li>The first DNS server checks its local cache to see if it has a current entry for that domain.</li><li>If there is no current entry in the cache, the server contacts authoritative DNS servers for this domain zone.</li><li>An authoritative DNS server checks its database. If the domain name is not found, the server returns an NXDOMAIN (non-existent domain) response.</li><li>The primary DNS server receives a response with the address of the requested name, or NXDOMAIN (non-existent domain), and passes it back to the client.</li><li>If the first DNS server in the list does not respond within the specified time (usually about 50 ms), the request is sent to the next DNS server in the list and the process is repeated from points 1–5.</li><li>If none of the servers responded to the request, the local resolver will re-query them in the same order, but with an increased timeout. However, it is important to note that if one of the DNS servers returns a response that the requested domain name does not exist (NXDOMAIN), then the local resolver will not check the remaining servers and will immediately return that response.</li></ol><p>If there are both private and public DNS resolver servers listed, and the public ones come first, when a client asks for a private domain name, the first public server won’t find it and will tell the client it doesn’t exist. So, the request will be denied.</p><p><strong>Possible solutions to the problem:</strong></p><ol><li><strong>Specify Private DNS server first in the list of DNS resolvers</strong>. To ensure quick and accurate responses, put the Private DNS server at the top of the resolver list. This way, it will handle requests first. If it’s a private request, it’ll respond authoritatively. But if it’s a public request, it’ll say it’s not found, and the client will move on to the next server.<br>However, if there are multiple Private DNS zones, like an MS AD Private DNS zone, things get trickier. You’ll need to add multiple Private DNS Resolvers to the client’s resolver list, making the resolution process more complex.<br>Also, if you’re using “systemd-resolved” for example on Ubuntu Servers, it might not respond with an error for unfamiliar public domain names. Instead, it might say the domain doesn’t exist, and the client won’t check other servers. This can lead to issues.</li><li><strong>One DNS server knows about all zones</strong>: Install a single DNS Resolver on the network, which will process all client requests and forward requests to Private DNS zones to specific authoritative Private DSN servers. This is the best solution also in terms of security, because we will be able to control the entire flow of DNS requests on our network and send requests to the Internet from only one host. By having a local cache on this server, we will get better performance and reduce response time to requests.</li><li><strong>Split DNS Client: </strong>On some clients, you can configure conditional resolution based on the domain name. For example, requests to *.domain1.com are directed to DNS server A, and requests to *.domain2.com are directed to DNS server B. However, not all client systems support this configuration.</li></ol><p>Useful commands for working with DNS resolvers:<br>1. dig<br># dig @8.8.8.8 <a href="http://www.azure.com/">www.azure.com</a> и ее короткая версия:<br>#dig <a href="http://www.azure.com/">www.azure.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cM-SzgTAm9jPZwfckPY5-w.png" /></figure><p>2. nslookup<br>set type=soa (ns, a, cname, ptr, ..)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmnuKfEkdaZKHB-_wkKg-Q.png" /></figure><p>3. resolvectl commands<br># service systemd-resolved restart<br># resolvectl flush-caches<br># resolvectl status</p><p>4. cat /etc/systemd/resolved.conf<br>View the list of installed DNS resolvers</p><p>4. vim /etc/systemd/resolved.conf.d/mydns.conf <br>Add a temporary DNS resolver to the DNS resolvers list<br>[Resolve]<br>DNS=168.63.129.16</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdf0d25e1a1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EC2 Instance connect troubleshooting]]></title>
            <link>https://awstip.com/ec2-instance-connect-troubleshooting-a1128adaaee6?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1128adaaee6</guid>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Thu, 07 Mar 2024 14:25:20 GMT</pubDate>
            <atom:updated>2024-03-21T10:27:45.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to connect to EC2 via EC2 Instance connect" src="https://cdn-images-1.medium.com/max/278/0*Z7bYQ4-BIKbv8PWW" /></figure><p>Amazon EC2 Instance Connect provides a simple and secure way to connect to your Linux instances using Secure Shell (SSH). EC2 Instance Connect allows you to connect to cloud-hosted instances without even opening a terminal window. More details can be found in the <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-eic.html">documentation</a>. <br>However, when connecting, we may encounter an error: “Failed to connect to your instance. EC2 Instance Connect is unable to connect to your instance. Ensure your instance network settings are configured correctly for EC2 Instance Connect. For more information, see EC2 Instance Connect Prerequisites at <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-prerequisites.html.">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-prerequisites.html.</a>&quot;</p><p>Let’s try to figure out the reason for the error.<br>After creating, we can connect to our EC2 instance in different ways:</p><ul><li>EC2 Instance Connect</li><li>Session Manager</li><li>SSH Client</li><li>EC2 Serial Console</li></ul><p>We can connect from:</p><ul><li>Local Computer</li><li>Other EC2 instances</li><li>Bastion host</li></ul><p>To use any connection type, we first need to fulfil the following <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-prerequisites.html">requirements</a>:</p><ul><li>Point to the right Key pair</li><li>Use Security Group with opened 22 port</li><li>Use Public IP address on EC2 network interface</li></ul><p><strong>SSH Client</strong></p><p>This is the first way we can try to connect. For that we need:</p><ul><li>open 22 port in Security Group to our source MyIP address.</li><li>create Key Pair in that particular AWS region.</li></ul><p><strong>EC2 Instance Connect option:</strong></p><p>In case we would like to connect to our instance through <strong>EC2 Instance Connect </strong>we must:</p><ul><li>have EC2 instance Connect installed. We can check it by connecting to EC2 instance via SSH and inside it do:</li></ul><pre># sudo yum install ec2-instance-connect (Amazon Linux)<br>or <br># sudo apt-get install ec2-instance-connect (Ubuntu)</pre><ul><li>open 22 port in Security Group to our source IP address. But there we have to notice that, <strong>EC2 Instance Connect</strong> use AWS API to send SSH-keys into EC2 instance, and than initiate SSH-connection. This process uses specific AWS IP address ranges for browser-based SSH connections to our instance and these ranges can be differ from our MyIP address. If we haven’t opened 22 port we will get error like that:</li></ul><pre>Failed to connect to your instance<br>EC2 Instance Connect is unable to connect to your instance. Ensure your instance network settings are configured correctly for EC2 Instance Connect. For more information, see EC2 Instance Connect Prerequisites at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-connect-prerequisites.html.</pre><p>This leads us to two options:</p><ol><li>Open 22 port to the whole world and create SG rule to 0.0.0.0/0 <br>which is not securefor our instance.</li><li>Open 22 port to the whole world and create SG rule to AWS IP address, which it uses for connecting to our instance. We can get this address by downloading official <a href="https://ip-ranges.amazonaws.com/ip-ranges.json">ip_ranges.json</a> and filter using EC2_INSTANCE_CONNECT as the service value:</li></ol><pre># jq &#39;.prefixes[] | select(.region==&quot;us-east-2&quot; and .service==&quot;EC2_INSTANCE_CONNECT&quot;)&#39; &lt; ip-ranges.json<br><br>{<br>  &quot;ip_prefix&quot;: &quot;3.16.146.0/29&quot;,<br>  &quot;region&quot;: &quot;us-east-2&quot;,<br>  &quot;service&quot;: &quot;EC2_INSTANCE_CONNECT&quot;,<br>  &quot;network_border_group&quot;: &quot;us-east-2&quot;<br>}</pre><p><strong>Connection troubleshooting:</strong></p><p>We have recommended <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html">list</a> to check our connection, but briefly we have to:</p><ul><li>check Key Pair</li><li>check Security Group</li><li>check DNS resolving<br>Try to do: dig ibm.com</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1128adaaee6" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/ec2-instance-connect-troubleshooting-a1128adaaee6">EC2 Instance connect troubleshooting</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On-Premise Veeam Backup to Azure]]></title>
            <link>https://alexanderilves.medium.com/on-premise-veeam-backup-to-azure-312875fa9218?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/312875fa9218</guid>
            <category><![CDATA[azure-cloud]]></category>
            <category><![CDATA[legacy-app-modernization]]></category>
            <category><![CDATA[veeam-agent-for-linux]]></category>
            <category><![CDATA[veeam]]></category>
            <category><![CDATA[disaster-recovery]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Sat, 10 Feb 2024 19:04:38 GMT</pubDate>
            <atom:updated>2024-02-10T19:04:38.899Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/888/0*YzakO4CvvSKjTgAc.png" /><figcaption>How to back up on-premise legacy applications to the Сloud in order to restore them in case of an emergency</figcaption></figure><p>The task is typical for many modern companies: there are legacy applications that cannot be re-engineered into the cloud and for which local servers are used in data centers. Additionally, backups of these servers and applications are not always created, posing a risk of their failure. The idea emerged to back up these servers in Azure Cloud and restore them in the cloud in case of failure. If successful, we can continue to operate on-premises applications, and in case of a disaster, restore them in Azure Cloud. The task is quite interesting and has several pitfalls that are poorly described in the documentation. Certainly, complex applications will still require re-engineering because there is network connectivity, and the applications themselves may have been deployed in specific networks and with specific licenses, and more. But in any case, preserving applications in the Cloud and having the ability to restore them is a good step towards solving the problem. Veeam and Microsoft Azure were chosen to address the task due to partnership considerations and existing licenses.<strong><br>Source data</strong>:</p><ol><li>On-Premise Legacy Applications on Bare Metal and On-Premise Hypervisors;</li><li>Target servers deployed On-Premise and in Azure Cloud;</li><li>Veeam BR 12;</li><li>Deployed VMware vCenter;</li><li>Azure Subscription with Azure Blob Storage Account;</li></ol><p><strong>Main Goal:</strong></p><p>Obtain Backup of Legacy Applications in the cloud, with the ability to restore these applications in Azure Cloud.</p><p><strong>Additional tasks:</strong></p><p>Ability to perform regular testing of backups in an isolated environment.</p><p><strong>Solution:<br>Deployment of Veeam DR infrastructure:</strong></p><p>Create an Account on the Veeam website;<br>Download the Veeam DR distribution;<br>Format the disk with ReFS 64 KB on the server for Local Repository;<br>Create a Local Repository (do not use Default Local Repository);<br>Create an Azure Account and Compute Account on the server;<br>Create Azure Blob Repository and Azure Archive Repository;<br>Create SOBR Repository.</p><p><strong>Backup can be performed in two ways:</strong></p><ol><li>If the application is installed on a VM, backup can be done through the Hypervisor (<a href="https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=120">VMware ESXi</a>, Hyper-V);</li><li>If the application is installed on a Bare Metal server or if we do not have root access to the Hypervisor, backup can be done through the installed <a href="https://helpcenter.veeam.com/docs/agentforlinux/userguide/system_requirements.html?ver=60">Veeam agent</a>. This is the most risky and labor-intensive backup method.</li></ol><p><strong>Performing Backup via Veeam Agent <br>Requirements:</strong></p><p>Veeam Linux Agent must be installed on the Target VM. And the <a href="https://helpcenter.veeam.com/docs/agentforlinux/userguide/system_requirements.html?ver=60">requirements</a> for installing this agent must be met.;</p><p>Microsoft Azure Linux Agent must be installed on the Target VM. And the <a href="https://learn.microsoft.com/en-us/azure/virtual-machines/linux/create-upload-generic#general-linux-system-requirements">requirements</a> for installing this agent must be met.;</p><p>After installing the agents, you can connect to VBR and perform Backup:</p><ol><li>Do not read articles on the Veeam website.</li><li>On the VBR side, create a Protection Group for pre-installed Veeam Agents, after which Veeam will generate configuration files (XML and TLS certificate) that can then be used to configure agent connection to the VBR protection group.;</li><li># mkdir /var/tmp/veeam &amp;&amp; cd $_</li><li>Copy files (.xml and two distribution files) to the target Ubuntu to /var/tmp/veeam On Target Ubuntu:</li><li>On Target Ubuntu:</li><li># sudo dpkg -i ./distr1804/<strong>veeamsnap</strong>_6.0.3.1221_all.deb</li><li># touch ~/.rnd (to avoid the error (<strong>Can’t load /home/adminuser/.rnd into RNG</strong>)</li><li># sudo apt-get -f install</li><li>If Secure Boot is enabled on Ubuntu, remember the path where the following will be saved:<br>writing new private key to ‘/var/lib/shim-signed/mok/MOK.priv’;<br>veeamsnap.ko: Installing to /lib/modules/5.15.0–1045-azure/updates/dkms/).</li><li>If you received an error related to OpenSSL:<br># sudo touch /var/lib/shim-signed/mok/.rnd<br># sudo chown root:root /var/lib/shim-signed/mok/.rnd<br># sudo chmod 600 /var/lib/shim-signed/mok/.rnd<br># sudo apt-get -f install<br>Then import them and reboot:</li><li># sudo dpkg -i distr1804/veeam_6.0.3.1221_amd64.deb</li><li># veeamconfig mode setVBRsettings — cfg<strong> &lt;protection_group_name&gt;.xml</strong></li><li>Then perform synchronization:<br><strong># </strong>veeamconfig mode syncnow</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=312875fa9218" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS SAP certification exam]]></title>
            <link>https://alexanderilves.medium.com/aws-sap-certification-exam-d1c18d2de02c?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1c18d2de02c</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[devops-training]]></category>
            <category><![CDATA[devops-career]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Sat, 03 Feb 2024 21:34:54 GMT</pubDate>
            <atom:updated>2024-02-03T21:34:54.170Z</atom:updated>
            <content:encoded><![CDATA[<p>How I was preparing for the exam:</p><figure><img alt="AWS Certified Solutions Architect — Professional" src="https://cdn-images-1.medium.com/max/672/0*1d0eZlhhW14rlJuL.png" /></figure><p>I’m excited to share that I’ve achieved a new certification: AWS Certified Solutions Architect — Professional, complementing my existing MCSE and VMware VCP certifications! The exam was challenging but intriguing, reinforcing my commitment to continuous learning.</p><p>So, how did I prepare for the exam? Really I had practical experience in several projects with AWS services beforehand, and I began my exam preparation a year ago with Udemy courses from Stephane Maarek. This has been a year of reading numerous articles and working through practical scenarios provided by John Bonso.</p><p>What does the exam comprise? Like AWS SAA exam, this exam covers a vast scope, requiring knowledge of a multitude of Amazon products, their peculiarities, use cases, compatibility, and constraints. While some questions are obvious, such as choosing between ECS/EKS, AmazonMQ/SQS, and choosing a database, if Aurora DB is in the selection list :), others have subtle differences, and the correct answer lies in the details.</p><p>The exam is time-limited, and I finished answering with only one second left. In fact, I didn’t even have enough time to look at the list of questions I had marked for verification.</p><p>And finally, it’s a comprehensive survey exam, demanding knowledge across the AWS spectrum (in contrast to specific product exams like Docker). The best advice I can give is to explore as many AWS solutions and dumps as you can and deploy as many practical solutions as possible. Hands-on experience with CloudFormation, S3 deployment, CloudFront, databases, compute, and networking is crucial. Deploying several scenarios with each product on this list would be beneficial. It truly helps.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1c18d2de02c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#git push doesn’t work]]></title>
            <link>https://alexanderilves.medium.com/git-push-doesnt-work-5edde4d1900f?source=rss-1e687b795e7b------2</link>
            <guid isPermaLink="false">https://medium.com/p/5edde4d1900f</guid>
            <category><![CDATA[gh001]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[git-push]]></category>
            <category><![CDATA[large-files-detected]]></category>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Alexander Ilves]]></dc:creator>
            <pubDate>Sun, 23 Jul 2023 16:56:57 GMT</pubDate>
            <atom:updated>2023-07-23T16:56:57.843Z</atom:updated>
            <content:encoded><![CDATA[<p>You have tried to push your repository to remote, but you can’t so as getting error like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQjg_JuKSeVXvNRmFFKl4w.png" /><figcaption>git push error messages</figcaption></figure><p>The cause of the problem is in: remote: error: GH001: Large files detected. You may want to try Git Large File Storage — <a href="https://git-lfs.github.com/">https://git-lfs.github.com</a>.</p><p>The problem has started in a new repository, and I by mistake forget to exlude .terraform directory from repository in my .gitignore fail. I have realized that directory is too large for git, but it was late. What I have tried to do:</p><p>I have tried to remove .terraform directory from local Work Directory</p><p>I have tried to use #git push origin master -force.</p><p><strong>Solution:</strong></p><p># git filter-branch — tree-filter ‘rm -rf Terraform/.terraform/’ — prune-empty HEAD</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jy0iRgRXbb6rLbUO5woonA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5edde4d1900f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>