<?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 Avi Keinan on Medium]]></title>
        <description><![CDATA[Stories by Avi Keinan on Medium]]></description>
        <link>https://medium.com/@avi-k?source=rss-c68758d65b91------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*da2Q-rzYWix7mG10</url>
            <title>Stories by Avi Keinan on Medium</title>
            <link>https://medium.com/@avi-k?source=rss-c68758d65b91------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 22:41:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avi-k/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[Why Your Route53 Hosted Zone Has a 50-Record Limit]]></title>
            <link>https://avi-k.medium.com/why-your-route53-hosted-zone-has-a-50-record-limit-0b3a12308294?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b3a12308294</guid>
            <category><![CDATA[dns]]></category>
            <category><![CDATA[cloudfront]]></category>
            <category><![CDATA[route-53]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Mon, 11 May 2026 05:02:18 GMT</pubDate>
            <atom:updated>2026-05-11T05:02:18.874Z</atom:updated>
            <content:encoded><![CDATA[<p>Why Your Route53 Hosted Zone Has a 50-Record Limit</p><p>I was adding a DNS record to one of my domains in Route53 and got this error:</p><p>Exceeded limit MAX_RRSETS_BY_ZONE</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jIakbCLrZZFt_qOpUfMnQg.png" /></figure><p>Not the most helpful error message. <a href="https://medium.com/p/0b3a12308294/edit">I checked the documentation </a>to understand what quota this is actually referring to:</p><blockquote><strong>MAX_RRSETS_BY_ZONE</strong>: The maximum number of records that you can create in the specified hosted zone</blockquote><p>I reached the max record count (subdomains) for that hosted zone. But the number didn’t add up. I use Route53 regularly and know the <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html#:~:text=10%2C000%20per%20hosted%20zone">default is 10,000 records</a>. I went back to the console to check how many records are there:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*Z0_WFRJRNmKO6mCUzvtUBA.png" /></figure><p>The table showed 50 and that was the actual limit. This wasn’t a new account or a freshly created hosted zone, I’d been using it for a while.</p><p>A quick search led me to a <a href="https://x.com/farique/status/2044212429060530327">post by Far on X</a> that pointed me in the right direction.</p><p>The cause was the hosted zone being attached to a CloudFront distribution on a free flat-rate pricing plan. That plan covers Route53 costs, but it <a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/flat-rate-pricing-plan.html#:~:text=Records%20per%20Hosted%20Zone">caps you at 50 records</a> (the pro plan raises that to 100), but either way, you’re nowhere near the default 10,000.</p><p>I found the distribution in the CloudFront console:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0I8DUEzyZcA3MPGx7yhxFg.png" /></figure><p>Under “Manage plan” you can see what’s included in the current plan, and there’s a Detach button. Clicking Detach moves the hosted zone back to standard pay-as-you-go billing and restores the 10,000-record quota:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*4xmGqmDAjsF6X5O-Qr2KAg.png" /></figure><p>AWS asks for a quick confirmation that you understand the zone is switching to on-demand billing:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*FFNyUG3IiC6Q8vutxMat-w.png" /></figure><p>Worth noting: detaching has <strong>no impact</strong> on DNS resolution or traffic. It only affects billing and the quota.</p><p>After detaching, I could create records again. I also confirmed the new quota via the CLI:</p><pre>aws route53 get-hosted-zone-limit --hosted-zone-id &lt;HOSTED-ZONE-ID&gt;<br>--type MAX_RRSETS_BY_ZONE</pre><p>Back to 10,000:</p><pre>{<br> “Limit”: {<br> “Type”: “MAX_RRSETS_BY_ZONE”,<br> “Value”: 10000<br> },<br> “Count”: 50<br>}</pre><p>If you want to re-attach the zone to a flat-rate plan later, you can do that from the same “Manage plan” screen in CloudFront.</p><p>The fix itself is straightforward once you understand the root cause. The frustrating part is that the error message provides almost no useful context, there’s no indication that the limitation is tied to a CloudFront pricing plan.</p><p>A more descriptive error message could have saved significant time on investigation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b3a12308294" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Common Cloud Mistakes Early-Stage Startups Make and How to Avoid Them]]></title>
            <link>https://medium.com/doit-international/common-cloud-mistakes-early-stage-startups-make-and-how-to-avoid-them-384d01463a7f?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/384d01463a7f</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-mistakes]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[early-stage-startup]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 10:22:54 GMT</pubDate>
            <atom:updated>2026-03-14T07:38:39.738Z</atom:updated>
            <content:encoded><![CDATA[<p>In my role at <a href="https://www.doit.com/">DoiT</a>, I work daily with startups that are just beginning their cloud journey.</p><p>And I keep seeing the same mistakes, over and over again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GaSJ3-GZweQtLj2gWblexg.png" /></figure><p>I’m sharing a few of them here, hoping you can avoid them before they become expensive/painful/hard to fix:</p><h3>1. The AWS Account Is Opened Under a Founder’s Personal Email</h3><p>Very often, the first AWS account is created using a founder’s private Gmail address.</p><p>In this situation, the account legally and operationally belongs to a person, not to the company.</p><p>If the founder leaves, there is a conflict, or (worst case) something happens to them, ownership becomes a serious business risk.</p><p>Beyond that, personal email is usually less secure than a corporate mailbox: no enforced MFA, no centralized auditing, weaker identity governance and a major obstacle when performing an audit for certification.</p><p>A compromise of the founder’s email often means full control over the company’s AWS environment.</p><p>This also creates a <strong>single point of failure</strong>.</p><p><strong>Best practice:</strong></p><p>Create a shared group mailbox, for example: aws@example.com</p><p>Add at least two team members (someone is always sick, on vacation, or at a conference), and use plus-addressing to separate environments in different AWS accounts:</p><ul><li>aws+production@example.com</li><li>aws+organization@example.com</li><li>aws+development@example.com</li></ul><h3>2. Creating resources in the Management Account</h3><p>A startup begins with a single AWS account that hosts everything: production, development, demos, and a developer&#39;s playground.</p><p>As the company grows, it becomes necessary to separate environments. The easiest way seems to be to turn this single account into the <strong>Management Account</strong> in AWS Organizations and create new member accounts via the organization.</p><p>The problem: the management account is the only account that <strong>cannot be governed</strong> by organization-wide controls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*aXqheuA8HlWDYIwIs3TOyw.png" /><figcaption>AWS Organization <a href="https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html">Service Control Policies documentation</a></figcaption></figure><p>Typical policies you want to enforce:</p><ul><li>All EC2 EBS volumes must be encrypted.</li><li>Resources cannot be created in unauthorized regions.</li><li>Expensive instance types (GPU) are restricted.</li><li>IAM users are forbidden (only roles are allowed).</li></ul><p>None of these applies to the Management Account, which, in this case, is also the production account.</p><p>Worse, AWS does not allow converting a Management Account into a Member Account.</p><p>Once the production account is also the management account, the only solution is a full organizational migration: rebuilding the organization, recreating policies, reconfiguring permissions, and reonboarding every employee to a new Single Sign On (SSO) endpoint.</p><p>If you are currently in a stage where everything runs in a single AWS account and want to start separating environments, <strong>create a new standalone AWS account</strong>, set it as the Management Account via AWS Organizations, and invite the existing Production account to become a member account in the new organization.</p><h3>3. Postponing Compliance</h3><p>If you plan to sell to enterprise customers, you will eventually be asked for compliance:</p><ul><li><strong>SOC 2 / ISO 27001</strong> for B2B SaaS</li><li><strong>HIPAA</strong> for healthcare</li><li><strong>PCI DSS</strong> for fintech and payments</li></ul><p>Retrofitting an existing product and organization to new compliance requirements is extremely hard.</p><p>It affects not only cloud architecture, but also development workflows, access control, and even employment contracts (IP ownership, confidentiality, device management, etc.).</p><p>Fixing cloud infrastructure is challenging but achievable. Changing contracts and organizational processes later is far more difficult. Therefore, engaging a compliance advisory partner from the very first lines of your product’s code will significantly simplify the journey.</p><h3>4. All Eggs in One Basket</h3><p>AWS allows you to manage domain registration, renewal and DNS inside Route 53; this is convenient and dangerous.</p><p>If the AWS account is suspended (due to a billing issue, security incident, or leaked IAM key), your domain may be affected as well.</p><p>When email stops working, it becomes very difficult to communicate with AWS Support to resolve the issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*128KGEqTQ6s8Q9LMq3-HgA.png" /><figcaption>posts from r/aws in Reddit.com</figcaption></figure><p><strong>Best practice:</strong></p><p>Keep the company’s primary domain outside the main production AWS account, even in a separate provider like GoDaddy or NameCheap or in a dedicated AWS account. If you are locked out of your production account, you can still maintain the DNS records with the other provider/account.</p><h3>5. Maintain an expiration calendar so you don’t miss critical renewal dates</h3><p>Even in the first year, a startup quickly accumulates:</p><ul><li>Contracts</li><li>API keys</li><li>Credit cards</li></ul><p>What they all have in common is an expiration date.</p><p>The unwanted outcomes are usually:</p><ul><li>Blocked AWS accounts due to non-payment.</li><li>Unexpected service outages due to an expired API key.</li><li>Rushed contract renewal negotiations due to missed or imminent renewal dates.</li></ul><p>A shared calendar with automated reminders (“Credit card 3344 expires in 30 days”, “MAP Provider contract renewal in 45 days”) helps prevent these issues.</p><h3>Final Thought</h3><p>There are many challenges to deal with. I would strongly recommend finding a mentor who has been a founder before and has already led several startups. Experienced advice is truly worth gold.</p><p>If you want to build your cloud the right way from day one, <a href="http://doit.com/">DoiT</a> brings the technology, the expertise, and years of experience helping both startups and global enterprises avoid these exact mistakes — and many others.</p><p>Let’s make your cloud a growth engine, not a risk factor.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=384d01463a7f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doit-international/common-cloud-mistakes-early-stage-startups-make-and-how-to-avoid-them-384d01463a7f">Common Cloud Mistakes Early-Stage Startups Make and How to Avoid Them</a> was originally published in <a href="https://medium.com/doit-international">DoiT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Storage Transfer Service User Agent and IPs]]></title>
            <link>https://avi-k.medium.com/google-storage-transfer-service-user-agent-and-ips-ff6c969d8f62?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff6c969d8f62</guid>
            <category><![CDATA[google-cloud]]></category>
            <category><![CDATA[ip-range]]></category>
            <category><![CDATA[storage-transfer]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Sat, 13 Dec 2025 19:53:32 GMT</pubDate>
            <atom:updated>2025-12-13T19:53:32.847Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I learned: <br>If you see “[Google CM]” user agent in your CloudTrail data events, and it’s using an IP address (74.125.38.225) that is not listed in Google Cloud <a href="https://www.gstatic.com/ipranges/cloud.json">services IP ranges</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/0*Wtvn56GLq2dGToWF" /></figure><p>It’s a sign that someone in the organization is using the “Google Storage Transfer Service” to copy files from S3 to Google Cloud Storage.</p><p>(I posted this <a href="https://www.linkedin.com/posts/avi-keinan-14828738_today-i-learned-if-you-see-google-cm-activity-6991037093577658368-5ZRG/">3 years ago on Linkedin</a>, and recently people started sending me messages that this was very helpful, so I’m also sharing this here).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff6c969d8f62" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resize images on-the-fly with GCP Cloud Functions and Google Cloud CDN]]></title>
            <link>https://medium.com/doit-international/resize-images-on-the-fly-with-gcp-cloud-functions-and-google-cloud-cdn-4c03e75843c8?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c03e75843c8</guid>
            <category><![CDATA[resize-images]]></category>
            <category><![CDATA[cloud-functions]]></category>
            <category><![CDATA[google-cloud]]></category>
            <category><![CDATA[cdn]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Thu, 28 Aug 2025 08:31:34 GMT</pubDate>
            <atom:updated>2025-08-28T08:31:34.600Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I will explain why you should resize images in your websites, and how you can leverage Google Cloud Functions with GCP Load Balancer and Cloud CDN to deliver on-the-fly resized images to improve your website performance, save expensive storage space and improve your website loading time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V9xev5Heg4ECVosJ-cVtGQ.png" /><figcaption>Image generated with ChatGPT 5</figcaption></figure><p>Almost every major website resizes the photos displayed on the site, and that’s for three primary reasons:</p><ul><li>Downloading large images leads to high bandwidth usage and high data transfer costs.</li><li>Scaling down images via HTML requires the client browser to download the entire image and then spend CPU time resizing it, leading to slower loading time of your website.</li><li>Without resizing on-the-fly, you need to store different sizes of the same image for your website&#39;s Desktop, Mobile, Tablet and email (newsletter), as storage costs in the cloud start at $0.02/GB per month, which could be expensive.</li></ul><p><em>Read more about image optimization in Steve Souders&#39; book, </em><a href="https://www.amazon.com/Even-Faster-Web-Sites-Performance/dp/0596522304"><em>Even Faster Web Sites</em></a><em>, Chapter 10.</em></p><p>Using Google Cloud Content Delivery Network (CDN) allows us to provide faster loading times to our static content, as the objects are cached at the edge network, which is spread globally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*cuXoMcws3ECElQZS.jpg" /><figcaption><a href="https://cloud.google.com/blog/products/networking/understanding-google-cloud-network-edge-points">Google Network</a></figcaption></figure><p>The solution in this article uses the following services:</p><ul><li>Google Cloud Storage — to store the images in full size.</li><li>Cloud Function — to resize the objects on the fly.</li><li>Google Cloud Load Balancer with Cloud CDN enabled — the users will access the load balancer to retrieve the images.</li></ul><p>We create a GCP Cloud Load Balancer (LB) and configure it to invoke a Cloud Function, the function pulls an image from Google Cloud Storage (GCS), resize it, and the LB reply with the resized image and save the image at the edge for future requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/1*7SAohan7x3C1hBkOvCWcMw.png" /></figure><h4>How to deploy</h4><p>We create a Google Cloud Storage (GCS) Bucket and upload all the objects (images) in their original size.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*qEeggLbQzs7LzT6qKuIMgw.png" /></figure><p>We set a name for the bucket and configure a regional location, and click on the <strong>Create</strong> button:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*ZeLi6c6VhaB8rtfEjTVIpw.png" /></figure><p>We uploaded an image, for example, nasdaq.jpg (of the Nasdaq building in Times Square, which I took in 2019) to this bucket in its original size, 6.3 MB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qD6Kml1Rm377iy4t1MZOiQ.png" /></figure><p>The next step is to create a function. Go to the Cloud Functions console and click on <strong>Write a function.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/809/1*FxbCTyBraOzlNp05Uvpsqw.png" /></figure><p><em>If this is the first time you use Cloud Functions, you might see a message “Cloud Functions API is enabled”. This means that Cloud Functions features are being enabled in your project at no extra cost.</em></p><p>In this step, we need to configure the function:</p><ol><li>We use the inline editor.</li><li>Set a name for the function.</li><li>Choose the region — that should be the <strong>same as the GCS region</strong>.</li><li>Set the runtime. In this demo, we work with Python.</li><li>And uncheck the IAM authentication so the LB can invoke the function.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/823/1*ZS-Z89t0zf_U4GGGEOOY_A.png" /></figure><p>Now click on the <strong>Create</strong> button, and if it’s the first time you use GCP services, you might need to enable a few more APIs:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*rLdrBK1NEw0DpyD8QQrDNQ.png" /><figcaption>in this example we need to enable Cloud Build to build the container that run the function,</figcaption></figure><p>Now it’s the fun part, We need to write the code that actually pulls the file from GCS, resizes it and returns the resized file.</p><p>We wanted to see if this could be done entirely by ChatGPT, so I had a few iterations with the LLM, after writing the following prompts:</p><p><em>“Write Python code to resize jpg png images to x,y based on the string provided.”</em></p><p><em>“Let’s assume it’s google cloud function that pass the params as query string and the file needs to be loaded from gcs and the result should be sent to a load balancer with the appropriate mime type.”</em></p><p><em>“What should I put in requirements.txt for this code?”</em></p><p><em>“Now I&#39;m getting ‘Error processing image: module ‘PIL.Image’ has no attribute ‘ANTIALIAS’’”</em></p><p>The result is the following code. In line 9, set the bucket that we use:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/af7b11342c19ad1eb849a52428125d9a/href">https://medium.com/media/af7b11342c19ad1eb849a52428125d9a/href</a></iframe><p>This is the <strong>requirements.txt</strong> file to configure Cloud Functions, which Python libraries it should use to build the container:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/63329fff300518d7dd30bb0219a1a70f/href">https://medium.com/media/63329fff300518d7dd30bb0219a1a70f/href</a></iframe><p>When we update the code in <strong>main.py</strong> and the libraries in <strong>requirements.txt</strong>, we see a warning that “The specified function (entry point) might not be present in your source code. Please ensure the entry point in your code matches the input field.”</p><p>This is because the function is calling the <strong>resize_image </strong>function, and Cloud Functions default function name is<strong> hello_http:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GrbamfHJ654sdwVXYDntFg.png" /></figure><p>We change the <strong>Function entry point</strong> to <strong>resize_image </strong>and click <strong>Save and redeploy.</strong></p><p>Cloud Functions builds the container of our code. It might take a couple of minutes, and we can track the status of the build at the top of the dashboard:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*hWLuUfRk1m_8PBPGojvrmg.png" /></figure><p>Note: Cloud Function invokes a function. The function uses <a href="https://cloud.google.com/compute/docs/access/service-accounts#default_service_account">Compute Engine Default Service Account</a>, which grants the function access to all the GCS Buckets in the project. We will not cover this in the article, but as a best practice, you should use a dedicated service account with the least privileged access.</p><p>The next step is to create a Load Balancer. Search for “Load Balancer” in the search console, access the Load Balancer dashboard and click on <strong>Create load balancer</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*Ilnm98shU3793IyT2Bv7DQ.png" /></figure><p>We want to create a Global, Public Facing, Application Load Balancer, Under the type of the load balancer, choose <strong>Application Load Balancer (HTTP/HTTPS):</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/827/1*kw6WHTS_gGfper0DLc5e_w.png" /></figure><p>We want our users from around the world to be able to access the load balancer, so we choose <strong>Public Facing (external)</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*JrtEB7yS5IBZTe87p4G35w.png" /></figure><p>We chose the Global load balancer to leverage the Google Cloud CDN feature, which allows us to cache the resized image at the edge server (at no extra cost).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*Eh-w5wvsVvJ9e9UmivO2RQ.png" /></figure><p>Then we choose the latest Load Balancer generation and click the<strong> Next </strong>and <strong>Create </strong>button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*cgM7r3h6SnHgZgvWrk1ZRg.png" /></figure><p>To simplify this stage, we create an HTTP <strong>frontend</strong> endpoint for the Load Balancer.</p><p>Set a name for the Load Balancer and the frontend IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDMpd3GUaurdwaua_iyk3g.png" /></figure><p>Click on <strong>Backend Configuration,</strong> and in the <strong>Backend services &amp; backend buckets</strong> box, click on <strong>Create a backend service</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*ch_UyMgW_CRUT-QKKuOxcw.png" /><figcaption><em>The backend service tells the Load Balancer to which resource pass the request, in our configuration, it’s a Cloud Function.</em></figcaption></figure><p>Set a name and a description for the backend service, and change the <strong>Backend type</strong> to <strong>Serverless network endpoint group</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*1JBC2SCqaRThOycnsrClkw.png" /></figure><p>Scroll down to the <strong>Backends</strong> area. Under New backend, click on the Serverless network endpoint groups and click on <strong>Create Serverless network endpoint group</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*19xYuhF0Kbnp0x5cDkn4Yw.png" /></figure><p>Set the Name for the Endpoint and choose the region where you create the Cloud Function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*vKaSgtfgUHaVD9rPZ5YwdA.png" /></figure><p>If you have never invoked the function before, this error pop up:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*IrtswXceeSECUHC7MLUH8A.png" /></figure><p>Go to the link in the error and enable Cloud Function API:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/1*lQUearOskaE_cCibQsZ4Eg.png" /></figure><p>Go back to the Serverless network endpoint page, set a name for the endpoint, the Region where the function is located, and choose Cloud Run (It might be confusing, but Cloud Functions are now called Cloud Run Functions, and use the same underlying technology).</p><p>Select the function and click on <strong>Create</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*AI1ea3M9hxRmhQBk6hUh8g.png" /></figure><p>In the backend page, we can configure Cloud CDN cache settings:</p><p>We can configure the CDN to cache the response for the duration (1 hour from row 54 in the script), or a longer duration.</p><p>I want to highlight that <strong>CDN uses a warm cache</strong>, meaning that only frequently requested content is stored in the CDN cache. If you set a 1-year cache for your content, but there are no frequent requests to the content, you can expect that after some time the CDN will pull the content from the origin (the function).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*1QVgBVMZY3hkgDzL0EWN-w.png" /></figure><p>See the Logging feature (marked with the arrow above). It is great for debugging and tracking usage, but also costly ($512 for 1 TB of logs).</p><p>If you generate a lot of requests, you can set the <strong>Sample rate</strong> to <strong>0.01</strong> to log one request out of every 100 requests.</p><p>Let’s scroll down to <strong>Security:</strong></p><p>By default, Google enables <strong>Cloud Armor</strong>, the Web Application Firewall (WAF), for our backend, but since there is <a href="https://cloud.google.com/armor/pricing">additional cost </a>and this is a demo, we disable it by clicking on the <strong>Cloud Armor backend security policy</strong> and changing it to <strong>None.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*igCkdy_RhQEliTRlM1WDCA.png" /></figure><p>The next step is to click on <strong>Create</strong>, and in the Load Balancer dashboard, click on <strong>Create</strong> again.</p><p>Note: Creating and updating a Load Balancer in GCP can take up to 15 minutes to propagate.</p><p>Now, once the load balancer is ready, click on the name of the load balancer and you see the IP that was generated:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JCOkiq1OlRUTjfzQ8W0Peg.png" /></figure><p>We access this IP and specify the name of the image and the height and width:</p><p><a href="http://34.49.21.153/?image=nasdaq.jpg&amp;size=500x600">http://34.49.21.153/?image=nasdaq.jpg&amp;size=500x600</a></p><p>The result: Instead of a 6.5 MB file, we received a smaller, resized image, weighing 63 KB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*ofFK8XsmpHbY5CBjh2dxVw.png" /></figure><p>My job is to guide customers in using the cloud. Come see what we can do for you at <a href="http://doit.com/services">doit.com/services</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c03e75843c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doit-international/resize-images-on-the-fly-with-gcp-cloud-functions-and-google-cloud-cdn-4c03e75843c8">Resize images on-the-fly with GCP Cloud Functions and Google Cloud CDN</a> was originally published in <a href="https://medium.com/doit-international">DoiT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing .IL Domains — Practical Insights]]></title>
            <link>https://avi-k.medium.com/managing-il-domains-practical-insights-296a70b8e468?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/296a70b8e468</guid>
            <category><![CDATA[domains]]></category>
            <category><![CDATA[isoc]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Sun, 24 Aug 2025 07:33:59 GMT</pubDate>
            <atom:updated>2025-08-24T07:33:59.733Z</atom:updated>
            <content:encoded><![CDATA[<h3>Managing .IL Domains — Practical Insights</h3><p>From time to time, I assist colleagues abroad who manage domains in Israel and encounter difficulties.</p><p>I thought it would be useful to put some of the “unwritten rules” into writing, to help others facing similar challenges.</p><h4>Background</h4><p>Israel has two country-code top-level domains (ccTLDs): <strong>.il</strong> and <strong>.ישראל</strong> (“Israel” in Hebrew).</p><p>Most domains are registered under the <strong>second-level domain (SLD): .co.il</strong>, which is designated for commercial use.</p><p>The ccTLDs are administered by the <a href="https://www.guidestar.org.il/organization/580299543"><strong>Israel Internet Association (ISOC-IL)</strong></a>, a non-profit organization operating since 1997.</p><p>Domain registration and management are handled via <a href="https://en.isoc.org.il/il-cctld/registrar-information/domain-name-registrars"><strong>Accredited Registrars</strong></a>. As of August 2025, there are 14 registrars.</p><h3>Registration Costs and Terms:</h3><p>ISOC-IL charges registrars a wholesale fee of <strong>₪56 per year </strong>(approx. USD 16.5) for registering or renewing a domain for 1 year. End-users typically pay a higher retail price, set by their registrar.</p><p>Domains can be registered or renewed for <strong>1 year and up to 5 years</strong>.</p><h3>DNS Updates:</h3><p>The <strong>.il DNS Root servers are</strong> updated <strong>five times a day </strong>(including weekends) at the following hours (Israel Time, GMT+3):</p><ul><li>07:00</li><li>11:00</li><li>13:00</li><li>17:00</li><li>21:00</li></ul><p>Requests submitted to an Accredited Registrar are not always relayed to ISOC instantly, so it is best to send update instructions in advance to avoid missing the next scheduled update.</p><p>Once relayed, changes appear within minutes on ISOC’s <strong>Whois servers</strong> (whois.isoc.org.il), but propagation to the root DNS servers follows the update schedule above.</p><h3>When a Domain Expires:</h3><p>Upon reaching its expiration date, a domain enters a <strong>grace period</strong> lasting between <strong>30 and 120 days</strong>.</p><p>During the grace period, a query to the WHOIS server will contain:</p><pre>remarks: Domain not renewed. Being revoked.</pre><p>During the <strong>final two weeks</strong> of this period, the domain’s DNS records are suspended. Here is an example of a WHOIS query with disabled DNS:</p><pre># whois.isoc.org.il<br><br><br>% The data in the WHOIS database of the .il registry is provided<br>% by ISOC-IL for information purposes, and to assist persons in<br>% obtaining information about or related to a domain name<br>% registration record. ISOC-IL does not guarantee its accuracy.<br>% By submitting a WHOIS query, you agree that you will use this<br>% Data only for lawful purposes and that, under no circumstances<br>% will you use this Data to: (1) allow, enable, or otherwise<br>% support the transmission of mass unsolicited, commercial<br>% advertising or solicitations via e-mail (spam);<br>% or  (2) enable high volume, automated, electronic processes that<br>% apply to ISOC-IL (or its systems).<br>% ISOC-IL reserves the right to modify these terms at any time.<br>% By submitting this query, you agree to abide by this policy.<br><br>query:        blogpost.co.il<br><br>reg-name:     blogpost<br>domain:       blogpost.co.il<br><br>descr:        Jonathan Miller<br>descr:        12 Haneviim Street<br>descr:        Jerusalem<br>descr:        9456123<br>descr:        Israel<br>phone:        +972 52 3347788<br>fax-no:       +972 52 3347788<br>e-mail:       jmiller AT example.org<br>admin-c:      GI-JM4521-IL<br>tech-c:       GI-JM4521-IL<br>zone-c:       GI-JM4521-IL<br>nserver:      ns1.randomdns.net  (Disabled)<br>nserver:      ns2.randomdns.net  (Disabled)<br>remarks:      Domain not renewed. Being revoked.</pre><p>This suspension serves as a strong warning to the owner of the domain that renewal is required.</p><p>Once the domain is renewed, DNS functionality is restored according to the regular update schedule.</p><blockquote><strong><em>Note:</em></strong><em> Renewal does not count the grace period itself. The domain is extended by one full year starting from the original expiration date.</em></blockquote><h3>Emergency Situations:</h3><p>Israel&#39;s business hours are <strong>Sunday through Thursday, 08:00–17:00 or 09:00–18:00 (GMT+3)</strong>.</p><p>Both registrars and ISOC-IL provide support via email and phone.</p><p>In emergencies, it’s possible to contact ISOC directly to correct errors.</p><p><strong>Best practice:</strong> Request that your Accredited Registrar provide you with an emergency contact for use outside normal business hours.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=296a70b8e468" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google Cloud Data: Standard Network vs. Premium Network]]></title>
            <link>https://avi-k.medium.com/google-cloud-data-standard-network-vs-premium-network-d9499104d03f?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9499104d03f</guid>
            <category><![CDATA[premium-network]]></category>
            <category><![CDATA[data-transfer]]></category>
            <category><![CDATA[cost-optimization]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[gcp]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 21:49:11 GMT</pubDate>
            <atom:updated>2025-06-25T21:49:11.721Z</atom:updated>
            <content:encoded><![CDATA[<p>In Google Cloud, when we create a server or a load balancer, Google offers us two networking tiers:</p><ul><li><strong>Premium Network</strong></li><li><strong>Standard Network</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/409/1*2dzlftkdEm9emJFnUfV_uA.png" /></figure><p>With the <strong>Premium Network</strong>, traffic from the internet reaches the Google Point of Presence (POP) closest to the user (this is the connection point between your ISP and Google), and from there, the traffic travels through Google’s internal backbone network all the way to the server.</p><p>With the <strong>Standard Network</strong>, traffic arrives at the region via the public internet. Because the internet consists of many providers and peering agreements (which sometimes prioritize cost savings over performance or speed), you may not always be able to utilize 100% of the bandwidth allocated to you by your ISP.</p><p>As a result, the <strong>Premium Network</strong> offers better performance, but it’s significantly more expensive. Also, with Premium Network, pricing is based on the <strong>user’s location</strong>.</p><p>For example, if your server is in Europe and your users are in Australia, Korea, or South America, you’ll pay <strong>63% more</strong> for data transfer compared to <strong>Standard Network</strong>.</p><h3>When should you not use Premium Network?</h3><p>Because the performance and cost gap is so large, I want to share a few real-world cases where <strong>Premium</strong> is unnecessary and <strong>Standard</strong> is perfectly fine:</p><h4>Do you have servers in another cloud? Are they in the same country?</h4><p>For example, I have servers in <strong>AWS</strong> and <strong>GCP</strong> in <strong>Northern Virginia</strong>. AWS region is us-east-1, and GCP region is us-east4.</p><p>Sometimes, these servers are across the street, with an AWS data center on one side and a GCP data center on the other.</p><p>To improve performance and reduce costs, cloud providers lay fiber optic cables between their data centers, and <strong>both Premium and Standard networks share this same infrastructure</strong>. That means performance is identical.</p><h4>Are your servers and users in the same country?</h4><p>They’re probably using the <strong>same POP</strong> to access Google’s network.</p><p>I’m based in Israel. When I access a Google server located in Israel, my connection point (POP) is <strong>exactly the same</strong>, whether I use <strong>Standard</strong> or <strong>Premium</strong>.</p><p>So in that case, there’s no performance difference between the two network types.</p><h3>Performance test</h3><p>To validate this, I launched two GCP servers:</p><ul><li>One using the <strong>Premium Network</strong></li><li>One using the <strong>Standard Network</strong></li></ul><p>Both with eight vCPUs (in GCP, network speed is proportional to the number of vCPUs), I also launched a third server in the AWS region in Israel (c7g.8xlarge).</p><p>The ping between AWS and GCP servers was identical: ~4.5ms</p><p>The Download speed from GCP (both Premium and Standard) to AWS was also the same: ~3200 Mbit/s</p><p>I then downloaded the file from the GCP Instances to my home computer, and again, the speed was the same: 800 Mbit/s</p><h3>Conclusion:</h3><p>There are many use cases where Premium Network is unnecessary, and switching to Standard Network can lead to significant cloud cost savings.</p><h3>P.S.:</h3><p>Each network tier has its own set of IP classes.</p><p>To switch from Network Premium Tier to Standard Tier, you must change the server’s IP address.</p><p>If you’re using the Standard Tier, <a href="https://cloud.google.com/blog/products/networking/standard-tier-network-now-includes-200-gb-data-transfer-per-month">the first 200 GB of outbound traffic</a> per month are free.</p><h3>Speed test details:</h3><ul><li>The GCP servers each had <strong>eight vCPUs</strong>, allowing speeds up to ~7 Gbps</li><li>The AWS instance supports at least <strong>7.5 Gbps</strong></li><li>The speed test was performed using <strong>nginx</strong>, with output file written to /dev/null to avoid disk I/O interference</li><li>My home computer is connected to <strong>1 Gbps fiber</strong>, and in local Israeli speed tests I’ve reached <strong>870 Mbit/s</strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9499104d03f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The risks of S3 Object Lock — why you should block it if you don’t need it]]></title>
            <link>https://medium.com/doit-international/the-risks-of-s3-object-lock-why-you-should-block-it-if-you-dont-need-it-9dbf7b43ec5f?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dbf7b43ec5f</guid>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[warm]]></category>
            <category><![CDATA[aws-s3]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Fri, 16 May 2025 09:02:56 GMT</pubDate>
            <atom:updated>2025-05-19T10:05:18.446Z</atom:updated>
            <content:encoded><![CDATA[<h3>The risks of S3 Object Lock — why you should block it if you don’t need it</h3><p>In Amazon S3, you can upload objects (files), choose a storage class, define who can access the file, configure automatic deletion, and more. Billing is hourly, and you can delete any object at any time to stop paying for its storage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*XoWN6eBVDngItT82xJeBaw.png" /></figure><p>One feature AWS introduced is <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lock.html"><strong>Object Lock</strong></a> — a mechanism that allows you to prevent objects from being deleted or overwritten. It’s designed to protect data meant for long-term retention, whether for compliance or archival purposes, from being accidentally or maliciously removed.</p><p>When creating a bucket, you can choose an Object Lock <strong>Retention Mode</strong>, which dictates how AWS will restrict object deletions:</p><ul><li><strong>Governance mode</strong> — Objects are write-protected, but users with special permissions can override or remove the lock.</li><li><strong>Compliance mode</strong> — Objects are completely immutable for the set retention period. No one, not even the root account user or AWS support, can delete them during this time.</li></ul><p>In both options, you can define a retention period between <strong>1 day and 100 years</strong>, counted individually for each object from when it’s uploaded to S3.</p><p>Once Object Lock is enabled on a bucket, you can define each object&#39;s lock mode and retention period when you upload an object. If you don&#39;t specify these settings during upload, the default settings will apply.</p><p>If you change the default settings later, they will only affect <strong>new objects</strong> — existing objects will retain the lock configuration they were uploaded with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*UwzUaq6SzgS9xNITF7bT1A.png" /></figure><p>Let’s focus on <strong>Compliance mode</strong>:</p><p>If you enable it, once an object is uploaded, no IAM Role or user — not even the root user — can delete the objects until the retention period ends. Not even AWS support can help you delete it prematurely.</p><p>You will get the following error:</p><p>“Access Denied because object protected by object lock.”</p><h3>So why would you want to block it?</h3><p>To reduce the damage in the event of a compromised AWS account.</p><p>Let me explain — there are three common patterns attackers follow when gaining access to an AWS account:</p><ol><li><strong>Ransom &amp; Destruction</strong>: Encrypt backups, demand ransom, and delete resources to cause chaos.</li><li><strong>Crypto mining</strong>: Launch expensive GPU-compute instances across all available regions to mine cryptocurrency.</li><li><strong>Financial drain</strong>: Provision costly resources like metal instances and massive EBS volumes, or purchase Redshift Reserved nodes to rack up charges.</li></ol><p>One particularly nasty trick an attacker might use is to <strong>create an S3 bucket with Object Lock for a long term in Compliance mode and</strong> upload huge files using zombie EC2 instances or even content that is illegal to hold.</p><p>Later, during a cost review or anomaly detection, you may discover a bucket containing <strong>massive amounts of undeletable data</strong>, costing <strong>thousands to tens of thousands of dollars</strong> per month, with no way to remove it.</p><h4>So, how do you delete a bucket with objects protected by Compliance mode?</h4><p>You can’t.</p><p>The only way is to <strong>close the entire AWS account </strong>with all its resources, which is a major pain, especially for production environments.</p><p>You’ll need to migrate your entire workload to a new AWS account — a process that can take weeks or even months, similar to a full environment migration.</p><h3>How do you block it?</h3><p>With <strong>Resource Control Policies (RCP)</strong> — a feature in AWS Organizations that lets you enforce policies across accounts in your organization (except the management account) for resources such as S3 Buckets.</p><p>You can create a resource policy that <strong>denies any attempt to enable Object Lock </strong>(unfortunately, <a href="https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazons3.html#amazons3-s3_object-lock-mode:~:text=PutBucketObjectLockConfiguration">it’s not possible to limit</a> it only to Compliance Mode). If someone tries to apply it, they’ll receive an Access Denied error.</p><p><strong>Pro tip:</strong> You can also allow only specific users (e.g., the security team) to bypass the restriction, while blocking everyone else. That way, you retain control without exposing the account to unnecessary risk.</p><p>Here’s an example RCP that blocks the use of Compliance mode entirely, for existing and new buckets:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09c5c5ea9d9a906fb0bb35ce1f4ee39d/href">https://medium.com/media/09c5c5ea9d9a906fb0bb35ce1f4ee39d/href</a></iframe><p>I applied the policy, created a new bucket, and when I tried to enable Compliance mode, I got the following error:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4IAHVsMfceAzeafWpbsKBA.png" /></figure><h4>Final thoughts:</h4><p>If you’re serious about <strong>minimizing long-term financial damage</strong> from misconfigurations or unauthorized access, I strongly recommend applying this policy.</p><p>By the way, <strong>Compliance mode</strong> isn’t limited to S3 — it also exists in:</p><ul><li><strong>EBS Snapshots</strong> — backups of EC2 volumes (disks)</li><li><strong>AWS Backup Vault </strong>— AWS Backup service</li></ul><p>You should consider blocking those as well, depending on your risk posture.</p><p>Discover even more helpful resources by visiting us at doit.com/services — your next step to success awaits!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dbf7b43ec5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/doit-international/the-risks-of-s3-object-lock-why-you-should-block-it-if-you-dont-need-it-9dbf7b43ec5f">The risks of S3 Object Lock — why you should block it if you don’t need it</a> was originally published in <a href="https://medium.com/doit-international">DoiT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS EC2 Billing Operations description (from Cost and Usage Report — CUR)]]></title>
            <link>https://avi-k.medium.com/aws-ec2-billing-operations-description-from-cost-and-usage-report-cur-57068596afe8?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/57068596afe8</guid>
            <category><![CDATA[finops]]></category>
            <category><![CDATA[ec2]]></category>
            <category><![CDATA[aws-ec2-operations]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Tue, 13 May 2025 16:06:28 GMT</pubDate>
            <atom:updated>2025-05-13T16:12:14.669Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS EC2 Billing Operations description (from Cost and Usage Report — CUR)</h3><p>Every now and then, as part of my FinOps work, I come across cases where I need to understand what operating system is used in EC2 instance basedo n AWS Cost and Usage report, under the Operation tab, you can find the RunInstances code, based on the numbers in the following table, you can determine the operating system (Linux, Windows, SUSE, etc.).</p><p>I decided to write it down here for future cases:</p><pre>Operation Name                           Description                      <br> ----------------------- ----------------------------------------------------- <br>   RunInstances               Dedicated Linux<br>   RunInstances               Linux Dedicated Host Instance hour<br>   RunInstances               Linux instance-hour (or partial hour) under monthly free tier<br>   RunInstances               On Demand Linux<br>   RunInstances               On Demand Linux Instance hour under 750 free hrs/month free trial ending Dec 31 2025<br>   RunInstances               Reservation Linux<br>   RunInstances               Unused Reservation Linux<br>   RunInstances:0002          Dedicated Windows<br>   RunInstances:0002          On Demand Windows<br>   RunInstances:0002          Reservation Windows<br>   RunInstances:0002          Windows Dedicated Host Instance hour<br>   RunInstances:0002          Windowsinstance-hour (or partial hour) under monthly free tier<br>   RunInstances:0002:SV001    Windows Spot in US East (N. Virginia) in VPC Zone #1<br>   RunInstances:0002:SV006    Windows Spot in US East (N. Virginia) in VPC Zone #6<br>   RunInstances:0002:SV006    Windows Spot in US West (N. California) in VPC Zone #6<br>   RunInstances:0002:SV007    Windows Spot in US East (N. Virginia) in VPC Zone #7<br>   RunInstances:0002:SV012    Windows Spot in US East (N. Virginia) in VPC Zone #12<br>   RunInstances:0002:SV062    Windows Spot in US East (N. Virginia) in VPC Zone #62<br>   RunInstances:0004          On Demand Linux with SQL Std<br>   RunInstances:0006          Dedicated Usage Windows with SQL Std<br>   RunInstances:0006          On Demand SQL Std<br>   RunInstances:0006          On Demand Windows with SQL Std<br>   RunInstances:000g          On Demand SUSE<br>   RunInstances:0010          Dedicated RHEL<br>   RunInstances:0010          On Demand REHL<br>   RunInstances:0010          RHEL instance-hour (or partial hour) under monthly free tier<br>   RunInstances:0014          On Demand RHEL with SQL Standard<br>   RunInstances:0100          On Demand Linux with SQL Server Enterprise<br>   RunInstances:0102          On Demand Windows with SQL Server Enterprise<br>   RunInstances:0200          On Demand Linux with SQL Web<br>   RunInstances:0202          Dedicated Windows with SQL Web<br>   RunInstances:0202          On Demand Windows with SQL Web<br>   RunInstances:0210          On Demand RHEL with SQL Web<br>   RunInstances:0800          On Demand Windows BYOL<br>   RunInstances:0g00          On Demand Ubuntu Pro<br>   RunInstances:0g00          On Demand Ubuntu Pro Instance hour under 750 free hrs/month free trial ending Dec 31 2025<br>   RunInstances:0g00:SV007    Ubuntu Pro Spot in US East (N. Virginia) in VPC Zone #7<br>   RunInstances:0g00:SV012    Ubuntu Pro Spot in US East (N. Virginia) in VPC Zone #12<br>   RunInstances:1010          On Demand Red Hat Enterprise Linux with HA<br>   RunInstances:CB            Capacity Block Linux<br>   RunInstances:CB            Capacity Block Reservation Linux<br>   RunInstances:SV001         Linux/UNIX Spot in US East (N. Virginia) in VPC Zone #1<br>   RunInstances:SV005         Linux/UNIX Spot in US East (N. Virginia) in VPC Zone #5<br>   RunInstances:SV006         Linux/UNIX Spot in US East (N. Virginia) in VPC Zone #6<br>   RunInstances:SV006         Linux/UNIX Spot in US West (N. California) in VPC Zone #6<br>   RunInstances:SV006:aa      (VTD Tier 1) Linux/UNIX Spot in US West (N. California) in VPC Zone #6<br>   RunInstances:SV007         Linux/UNIX Spot in US East (N. Virginia) in VPC Zone #7<br>   RunInstances:SV009         Linux/UNIX Spot in US West (N. California) in VPC Zone #9<br>   RunInstances:SV009:aa      (VTD Tier 1) Linux/UNIX Spot in US West (N. California) in VPC Zone #9<br>   RunInstances:SV012         Linux/UNIX Spot in US East (N. Virginia) in VPC Zone #12<br>   RunInstances:SV062         Linux/UNIX Spot in US East (N. Virginia) in VPC Zone #62</pre><p>Notes:</p><p>The information in this table is partially documented on the <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/billing-info-fields.html">AWS Website</a>, and I haven’t figured out yet what “VPC Zone” means, as it’s not a unique identifier per region.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57068596afe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Increase MacBook Pro disk space on a budget]]></title>
            <link>https://avi-k.medium.com/increase-macbook-pro-disk-space-on-a-budget-62923aa88c92?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/62923aa88c92</guid>
            <category><![CDATA[sd-car]]></category>
            <category><![CDATA[macbook-pro]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Mon, 28 Oct 2024 16:30:55 GMT</pubDate>
            <atom:updated>2024-10-28T16:30:55.402Z</atom:updated>
            <content:encoded><![CDATA[<p>Increase MacBook Pro disk space on a budget</p><p>I have a <a href="https://support.apple.com/en-us/111838">MacBook Pro M2 pro chip</a> with 500GB SSD storage, and I’m running out of space.</p><p>You can choose a model with a larger SSD drive when purchasing a MacBook. However, since the drive is soldered to the motherboard, it cannot be upgraded later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*Gmr-dENpjW7CXShRZ5EXJg@2x.png" /><figcaption>MacBook Pro SSD upgrade options</figcaption></figure><p>I didn’t want to ask my employer to replace my MacBook with a more expensive version. It doesn’t make sense to spend over $2,500 just because I ran out of disk space, so I decided to take advantage of the SD card slot that the MacBook has:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/0*Cq3o8VMYvxqi8QgF.png" /><figcaption>The SD card slot location, on the right side of a MacBook Pro</figcaption></figure><p>I ordered from Amazon.com a <a href="https://www.amazon.com/SanDisk-1-5TB-microSDXC-Memory-Adapter/dp/B0CJMRW771?th=1">SanDisk 1.5Tb Micro SD card</a> and <a href="https://www.amazon.com/dp/B012F8ALBC?ref=ppx_yo2ov_dt_b_fed_asin_title">BaseQi iSDA 504A</a> for $118.98:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ln81O3tzsoDpCBDC6pqKsw.jpeg" /></figure><p>I specifically ordered the BaseQi because it doesn’t stick out from the MacBook, unlike other SD adapters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YSs1USKQ9aXNvrBxYgxPXw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2fT5oaP1FWJJDMiTttILA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fPPnABIFLdxB0_E6hQC_rA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vZvcqD1ZLg6RM_GPoGqKGw.jpeg" /></figure><p>After that, I formatted the card from exFAT to APFS (Apple’s file system), and that’s it — ready to go.</p><p>In terms of performance, <a href="https://www.kingston.com/en/blog/personal-storage/memory-card-speed-classes#:~:text=Minimum%20sequential%20write%20speed">since I ordered a U1 card</a>, The SD card performance is around <strong>20 MB/s for writing</strong> and <strong>88 MB/s for reading</strong>. Since most of my tasks involve reading from this SD card, it’s great for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62923aa88c92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to allocate contiguous IP blocks in AWS]]></title>
            <link>https://avi-k.medium.com/how-to-allocate-contiguous-ip-blocks-in-aws-69e8891493fd?source=rss-c68758d65b91------2</link>
            <guid isPermaLink="false">https://medium.com/p/69e8891493fd</guid>
            <category><![CDATA[elastic-ip]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[contiguous-ip-blocks]]></category>
            <category><![CDATA[ipam]]></category>
            <category><![CDATA[aws-ipam]]></category>
            <dc:creator><![CDATA[Avi Keinan]]></dc:creator>
            <pubDate>Sat, 26 Oct 2024 07:22:09 GMT</pubDate>
            <atom:updated>2024-10-26T07:22:09.309Z</atom:updated>
            <content:encoded><![CDATA[<p>A month ago, AWS launched a new feature that allows us to allocate contiguous IP blocks.</p><p>Many companies prefer a contiguous IP block to share with their customers to whitelist access.</p><p>It’s much easier to send: “open access to <a href="http://52.52.52.48/29">52.52.52.48/29</a>”. <br>Instead of something like: “open access to <a href="http://54.240.143.3/">54.240.143.3</a> <a href="http://13.56.210.25/">13.56.210.25</a> <a href="http://18.232.47.205/">18.232.47.205</a> <a href="http://18.240.17.104/">18.240.17.104</a> <a href="http://52.95.245.37/">52.95.245.37</a> <a href="http://35.178.74.122/">35.178.74.122</a>”</p><p>Before this feature was available, you had to contact AWS Support and ask them to allocate a CIDR for you. Now, this can be done automatically.</p><p>To allocate an IP block, you need to create an IPAM Pool via AWS VPC IPAM. You can use the <strong>IPAM free tier</strong> (many try to avoid the IPAM advanced tier due to the cost).</p><p>Then, allocate a /29 cidr (8 IPs) or /30 (4 IPs) in IPAM:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*29H6iuLvjDep49JMeQhc9g.png" /></figure><p>The next step is to allocate an Elastic IP via the EC2 console. You can pick the IPAM pool, and AWS will associate an IP from the CIDR you allocated in IPAM:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*i-iDx4XvKr5T9tUXjuAzow.png" /></figure><p>What’s the catch?<br>Once we have created an allocation of a CIDR range, there is a charge of $5.84 per month (hourly charge) <strong>per IP</strong>, the price is higher than a regular Elastic IP, which costs $3.65 (hourly charge).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69e8891493fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>