AWS icons are the official service marks Amazon publishes for architecture diagrams: all 439 of them here in SVG, one file per service, free to download one by one or as a single ZIP, no signup
Drawing something with these icons?
Describe the architecture and Datadef places the AWS icons for you, on a canvas you can edit rather than a slide you assemble by hand.
No account needed · Editable canvas, not a picture
AWS icons are the set of service and resource marks that Amazon Web Services publishes for drawing architecture diagrams: one icon per service (EC2, S3, Lambda, RDS and the rest), plus group and boundary shapes for accounts, regions, VPCs and subnets. Amazon releases them as the AWS Architecture Icons and asks that they be used as drawn, in their own colours, to represent the service they stand for. The console, the AWS documentation and most conference slides use them, which is why a diagram drawn with anything else looks wrong to an AWS engineer.
Developers use them in draw.io, Lucidchart, Figma and slide decks to draw the request path, the VPC and its subnets, and the data pipeline, so a reviewer can read the picture without a legend. Every icon on this page is a single SVG, so it stays sharp at any size and exports to PNG when a tool needs one. Datadef uses the same set: describe the architecture in the box above, or point it at a repository, and it places the icons in the right zones on a canvas you can edit.
This collection includes icons for all major AWS services: Lambda, S3, EC2, RDS, DynamoDB, CloudFront, API Gateway, ECS, EKS, and 430+ more services.
Perfect for cloud architecture diagrams, technical documentation, presentations, and DevOps workflows.
This page is the whole set. Each service below has its own page instead: the single SVG, the names people search it by, and the architecture it usually appears in. S3 is the busiest of them, and the aws bedrock logo is the one people search for as a logo rather than an icon. The ec2 icon page explains where the instance mark belongs on a diagram and where it does not.
Icons are the easy half of an AWS diagram. Deciding which services to show, and how to group VPCs, accounts and regions so the picture stays readable, is the harder half. The AWS data platform diagram guide works through that layer by layer, from ingestion to serving. If you are still picking the tool to draw it in, the review of AWS architecture diagram tools compares what each one does with the official icon set. And for the S3 to Glue to Redshift shape most AWS data diagrams turn out to be, the data pipeline diagram generator starts you from a draft with the icons already placed.
Loading icons...
Click the download button on any icon to get the SVG file. Use them in any design tool or code editor.
Import icons into Figma, Sketch, PowerPoint, or directly into Datadef for AI-powered architecture diagrams.
Skip manual work: use the AWS architecture diagram generator to place these icons automatically from a plain-English description.
Instead of manually placing icons, describe your AWS architecture in plain English and get a professional diagram in seconds.
Includes all 439 AWS icons + 226 GCP icons + 624 Azure icons. No credit card, no subscription.
Yes. Every icon downloads on its own, and all 439 download together as one ZIP, with no account, no email and no watermark. The marks belong to Amazon Web Services, so follow their brand guidelines when you publish a diagram that uses them. Their terms are at https://aws.amazon.com/architecture/icons/
SVG. They are vectors, so they stay sharp at 24 pixels in a table and at 400 pixels on a slide, and they can be resized without soft edges. The ZIP contains 439 SVG files, one per service, each named after the service it shows.
Yes. PowerPoint has imported SVG since the 2016 release, Keynote and Google Slides accept them, and Figma and draw.io read them natively. Drag the file in and it keeps its vector edges rather than pixelating when you scale the slide.
439 on this page, one per service, covering S3, Lambda, EC2, RDS and the rest of the catalogue. Each one also has its own page with the architecture it usually appears in.