Announcing the AWS Exporter

Why we created the AWS exporter

The AWS exporter brings us even closer to realizing our vision of getting everything - AWS resources in this case - into the software catalog and the internal developer portal. By bringing live cloud resource data into the software catalog and mapping it into the relevant software catalog entities, all information will be easily visible to both developers and operations.

‍

What you can do with the AWS exporter (add data for 500 resources!)

Using the exporter you can add data from your AWS accounts into the software catalog.  You can map AWS resources such as S3 buckets, Lambda functions, SQS queues, RDS DB instances, ECS services and anything that’s in the AWS cloud control API. We actually support more than 500 such resources. Once you’ve added them and defined relations, you can create a complete, easily digestible map of your AWS accounts inside Port.

‍

In Port, this is done using blueprints and relations. A blueprint for a cloud resource (you can check our blueprints in the live demo) contains the data that should be collected as well as the relations to other blueprints. The AWS exporter is what brings the actual data into the catalog, creating entities.

‍

Here's, for example, a blueprint where we model all the SNS topics and all their Lambda subscribers:

For instance, for a Lambda function, we can bring metadata regarding its description, memory limit size, timeout, IAM execution role, runtime (Node, Python, Go,…), package type (Zip, Image), architectures (x86_64, arm64), etc. 

‍

Using these blueprints, you can get a unified view of all the SNS topics and Lambdas in your accounts and also the connections between them (if there are any). In addition, you can get the tags, deep links to the console and a lot more. 

‍

‍

We even go beyond what appears in these blueprints and present more details, per type of resource (in this case we will have an S3 blueprint, Lambda blueprint etc). For example, for S3 we can bring information such as bucket encryption, domain names, public access block configuration and more. For an SQS queue, we can bring metadata regarding its visibility timeout, max message size, retention period, tags and more.

‍

{{cta_7}}

‍

How it works

The AWS exporter is lightweight and takes AWS data into the blueprints and relations defined in your software catalog model. The exporter itself is deployed as an AWS serverless application that is deployed in your AWS account. 

‍

We recommend ingesting data through live events, such as create, update and delete of a resource. 

‍

Want to know more? Check our docs