Skip to main content

Check out Port for yourself 

AWS Resource and Property Reference

Welcome to the reference guide for AWS resource, actions and properties, as supported by AWS CloudFormation and used in Port integrations.

Supported Resource Types​

Explore detailed documentation for each AWS resource and action available for integration. For each resource type, you'll find information about supported actions, required permissions, and usage best practices.

Resource type identifiers follow a standardized format, allowing you to easily recognize and reference each AWS entity:

service-provider::service-name::data-type-name

For example, an EC2 instance is identified as:

AWS::EC2::Instance

Refer to the sidebar or the list below to navigate to individual resource reference pages where you'll find actionable integration details, sample configurations, and official AWS documentation links.

More Resource Types Coming Soon

We're continuously expanding support for additional AWS resource types to ensure comprehensive coverage of your AWS infrastructure.

If you need support for a specific AWS resource or action that isn’t yet available, please consider opening a feature request or reach out to us through chat, Slack, or our Support Portal.

Your feedback helps us prioritize what to build next.

Actions​

Actions define the set of API operations performed to discover and fetch resources within your AWS environment. These actions are mapped directly to AWS API calls—for example, DescribeInstances for EC2 or ListBuckets for S3—which determine the resource data that Port can ingest and keep up to date.

Ensure required AWS permissions are granted

Each action requires specific AWS IAM permissions. Your integration’s AWS credentials must have these permissions; otherwise, the action will not succeed and its data will not be available in Port.

How Actions Map to AWS Operations​

Each Port-supported resource type comes with a set of actions that align with AWS's official API operations. For instance:

  • For Amazon S3 Buckets, the ListBucketsAction leverages the ListBuckets API, and additional actions like GetBucketTaggingAction or GetBucketEncryptionAction invoke their respective AWS endpoints.
  • For EC2 Instances, DescribeInstancesAction maps to the DescribeInstances API and brings in detailed instance configuration.

These mappings ensure that only the properties available from the selected AWS actions are ingested into your Port catalog.

Enabling and Customizing Actions​

With Port, you have full control over which AWS resource properties are discovered and ingested into your catalog by specifying the actions to use for each resource type. Actions define what data you collect and the AWS permissions required.

  • Default Actions: These are enabled automatically, ensuring basic discovery such as listing all S3 buckets or EC2 instances without additional configuration.
  • Optional Actions: Enable these to collect more detailed properties for your AWS resources. You must explicitly add optional actions in your integration configuration for Port to use them.

To collect additional properties from AWS resources, add the optional actions you need to the includeActions field of your configuration. For example, to include status details from EC2 instances by enabling the DescribeInstanceStatusAction, add the following:

- kind: AWS::EC2::Instance
  selector:
    query: 'true'
    includeActions:
      - DescribeInstanceStatusAction

In this configuration, Port will enrich your catalog by fetching all properties provided by the DescribeInstanceStatus API for every EC2 instance.

Action limit

You can include a maximum of 3 optional actions per resource kind (excluding default actions). To use more than 3 actions, you can configure multiple resource kinds in your integration.

Refer to the individual resource documentation pages for a table of actions, their AWS mapping, and necessary IAM permissions.