Adding Amazon as an infrastructure sponsor.

Author: daveverwer

FrontEnd/styles/supporters.scss

@@ -24,6 +24,8 @@
     section {
         ul {
             display: grid;
+            gap: 20px;
+            row-gap: 40px;
             margin: 60px 0;
             padding: 0;
 
@@ -35,12 +37,13 @@
                     display: flex;
                     align-items: center;
                 }
-            }
 
-            @media screen and (max-width: $mobile-breakpoint) {
-                gap: 20px;
+                &:last-child:nth-child(odd) {
+                    grid-column: span 2;
+                    justify-self: center;
+                }
 
-                li {
+                @media screen and (max-width: $mobile-breakpoint) {
                     justify-content: center;
                 }
             }

Public/images/blog/swift-package-index-and-amazon-logos.png

@@ -0,0 +1,15 @@
+![The Swift Package Index logo next to the Amazon logo](/images/blog/swift-package-index-and-amazon-logos.png)
+
+It may surprise you to learn how much hosting infrastructure a site like the Swift Package Index needs.
+
+We obviously need a web server, or actually a few web servers, as we want redundancy so the site is never down for you, even when we do maintenance. Of course, we also need a redundant database to store all that metadata. We also need a staging site so we can test changes before they go live. There’s no point in having a redundant hosting plan if you push changes into production that completely break the site!
+
+Then there’s our “build system” that powers all the compatibility information. That system consists of 10 very powerful machines that crunch through more than 500,000 Swift builds during a busy month. Those machines also build all the documentation that we host for almost 1,000 packages.
+
+The build machines also generate hundreds of thousands of build logs per month and millions of documentation files that need hundreds of gigabytes of storage. We have been using [Amazon AWS](https://aws.amazon.com) for this storage so far, but our were starting to rise as we host more and more documentation.
+
+Which is why we’re delighted to announce today that Amazon is [joining our set of infrastructure sponsors](/supporters) by donating credits to the project. We’ll use these credits to continue to host the logs documentation that you use every day.
+
+We want to say a huge thank you to every one of our infrastructure sponsors for keeping this site hosted and processing. We could not do what we do without their support.
+
+We’d also love to [thank all our supporters](/supporters) who keep this project running as smoothly as it does. Your support is invaluable.

Public/images/sponsors/amazon.png

@@ -188,3 +188,8 @@
   summary: We recently transitioned our Mac build machines that power our compatibility and documentation build system from a manually configured and maintained collection of Mac mini machines to a new Orka cluster from MacStadium. It provides complete isolation for builds, and a more efficient use of our build machines.
   published_at: 2024-07-08
   published: true
+- slug: welcoming-amazon-as-an-infrastructure-supporter
+  title: Welcoming Amazon as an infrastructure supporter
+  summary: We are thrilled to announce that Amazon is joining Apple as a supporter of the Swift Package Index by providing infrastructure support.
+  published_at: 2024-10-28
+  published: true

Public/images/sponsors/amazon~dark.png

@@ -40,6 +40,10 @@ enum Supporters {
         .init(name: "Microsoft Azure",
               logo: .init(lightModeUrl: "/images/sponsors/microsoft.png",
                           darkModeUrl: "/images/sponsors/microsoft~dark.png"),
+              url: "https://azure.microsoft.com"),
+        .init(name: "Amazon AWS",
+              logo: .init(lightModeUrl: "/images/sponsors/amazon.png",
+                          darkModeUrl: "/images/sponsors/amazon~dark.png"),
               url: "https://azure.microsoft.com")
     ]