Urgent.News

What's breaking now, across thousands of outlets.

Tech

Free AWS, Azure and GCP architecture icons as SVG

I queried the registry and counted. Amazon publishes 739 architecture icons, Microsoft 626, and Google 214. Together that is 1,579 icons across three download pages, three zip files, and three different ideas of what an icon should look like. If you write architecture docs, you have lived this. You want a Lambda box and a BigQuery box in the same README, and you end up unzipping two archives to…

The wire story provides information about the availability of architecture icons for Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). A total of 1,579 icons are offered across these three providers, covering various categories such as services, resources, categories, and groups. Each provider offers icons in different sizes (16, 32, 64 pixels) and default versions, with AWS icons being the most extensive set at 739 files.

The naming convention for the icons follows the provider's product naming, which can lead to confusion. For example, the AWS Lambda icon is named aws-aws-lambda, not simply aws-lambda. The icons are licensed under different terms for each provider. AWS icons are licensed under CC-BY-ND-2.0, which means they can be shared unmodified with credit but cannot be altered.

Azure icons are licensed under MIT and Azure-specific terms, while Google Cloud icons are licensed under Apache-2.0, with additional company-specific usage terms.

The story emphasizes the usefulness of these icons in various contexts, such as README files, slide decks, and generated diagrams. They can be easily embedded using an img tag with the appropriate SVG file path. The size of the icons ranges from 725 bytes for Google Cloud to 13,951 bytes for AWS, making them lightweight for most web applications.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

DAY 3 - SAGA Design Pattern

To manage distributed transactions across multiple microservices. It divides a large transaction into a series of smaller local transactions. Executed independently.

  • SAGA pattern manages distributed transactions across microservices.
  • Breaks large transaction into smaller local transactions executed independently.
  • Compensating actions undo previously completed operations in case of failure.

Why Most Type-Safe Validation Fails in Production (And How JEV Fixes It)

If you've shipped a production system that handles structured data — API payloads, form submissions, config files, event streams — you've probably hit this exact wall: Your validation logic works…

  • Validation in production lacks field-specific details
  • Type safety at compile time doesn't guarantee runtime confidence
  • JEV returns typed, structured decision objects for validation

More from Thursday 24 September →