You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws-v3/resource-and-property-reference/resource-and-property-reference.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Each Port-supported resource type comes with a set of actions that align with AW
55
55
56
56
These mappings ensure that only the properties available from the selected AWS actions are ingested into your Port catalog.
57
57
58
-
### Enabling and Customizing Actions
58
+
### Enabling and customizing actions
59
59
60
60
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.
61
61
@@ -70,29 +70,30 @@ To collect additional properties from AWS resources, add the optional actions yo
70
70
query: 'true'
71
71
includeActions:
72
72
- DescribeInstanceStatusAction
73
+
```
73
74
74
-
In this configuration, Port will enrich your catalog by fetching all properties provided by the [DescribeInstanceStatus API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstanceStatus.html) for every EC2 instance.
75
+
In this case, Port will enrich your catalog by fetching all properties returned by the [DescribeInstanceStatus API](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeInstanceStatus.html) for every EC2 instance.
75
76
76
-
:::caution Action limit
77
-
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.
77
+
:::caution Maximum actions per resource
78
+
You can include a **maximum of 3 optional actions per resource kind** (default actions excluded). To use more than 3 optional actions, configure multiple resource kinds in your integration.
78
79
:::
79
80
80
81
81
82
### Querying resources from specific regions
82
83
83
-
The `regionPolicy` selector lets you control which AWS regions are queried by the integration. Use it to include or exclude regions per resource.
84
+
You can control which AWS regions Port queries for resources using the `regionPolicy` selector. This allows you to include or exclude specific regions per resource type.
84
85
85
86
- allow: List of regions explicitly permitted for querying
86
87
- deny: List of regions explicitly excluded from querying
87
88
88
89
#### How `regionPolicy` works
89
90
90
-
1. If both lists are empty:all regions are allowed.
91
-
2. If the region is in `deny`:it is excluded unless explicitly allowed.
92
-
3. If the region is in `allow`:it is included for querying.
93
-
4. If a region appears in both lists:it is excluded.
94
-
5. If only `deny` is specified:only regions in the `deny` list are excluded.
95
-
6. If only `allow` is specified:only regions in the `allow` list are included.
91
+
1. If both lists are empty, all regions are allowed.
92
+
2. If a region is listed in `deny`, it is excluded unless explicitly allowed.
93
+
3. If a region is listed in `allow`, it is included for querying.
94
+
4. If a region is present in both lists, it is excluded.
95
+
5. If only `deny` is specified, only the regions in `deny` are excluded.
96
+
6. If only `allow` is specified, only the regions in `allow` are included.
0 commit comments