AWS resource-explorer documentation change
Summary
Added multiple AWS services and their resource types to the list of supported resources in AWS Resource Explorer, including security-related services like Amazon Inspector and IAM certificate resources
Security assessment
The changes add documentation for security-adjacent services (e.g., Amazon Inspector, IAM certificate resources) but show no evidence of addressing specific vulnerabilities. The updates appear to be routine expansion of supported services.
Diff
diff --git a/resource-explorer/latest/userguide/supported-resource-types.md b/resource-explorer/latest/userguide/supported-resource-types.md index c9a5dc552..5f96519c9 100644 --- a/resource-explorer/latest/userguide/supported-resource-types.md +++ b/resource-explorer/latest/userguide/supported-resource-types.md @@ -54,0 +55,2 @@ You can still use these resource types in their own services, but they are no lo + * AWS AppConfig + @@ -86,0 +89,2 @@ You can still use these resource types in their own services, but they are no lo + * Amazon CloudWatch Observability Access Manager + @@ -94,0 +99,2 @@ You can still use these resource types in their own services, but they are no lo + * AWS CodeDeploy + @@ -112,0 +119,2 @@ You can still use these resource types in their own services, but they are no lo + * AWS Cost Explorer + @@ -156,0 +165,6 @@ You can still use these resource types in their own services, but they are no lo + * Amazon EventBridge Pipes + + * Amazon EventBridge Scheduler + + * Amazon EventBridge Schemas + @@ -182,0 +197,2 @@ You can still use these resource types in their own services, but they are no lo + * AWS HealthOmics + @@ -186,0 +203,2 @@ You can still use these resource types in their own services, but they are no lo + * Amazon Inspector + @@ -192,0 +211,2 @@ You can still use these resource types in their own services, but they are no lo + * AWS IoT Core Device Advisor + @@ -194,0 +215,2 @@ You can still use these resource types in their own services, but they are no lo + * AWS IoT FleetWise + @@ -224,0 +247,2 @@ You can still use these resource types in their own services, but they are no lo + * Amazon Managed Blockchain + @@ -309,0 +334,2 @@ You can still use these resource types in their own services, but they are no lo + * `apigateway:vpclinks` + @@ -330,0 +357,9 @@ You can still use these resource types in their own services, but they are no lo +### AWS AppConfig + + * `appconfig:application` + + * `appconfig:deploymentstrategy` + + + + @@ -399,0 +435,2 @@ You can still use these resource types in their own services, but they are no lo + * `backup:report-plan` + @@ -433,0 +471,2 @@ You can still use these resource types in their own services, but they are no lo + * `cloudfront:continuous-deployment-policy` + @@ -456,0 +496,2 @@ You can still use these resource types in their own services, but they are no lo + * `cloudtrail:channel` + @@ -496,0 +538,7 @@ You can still use these resource types in their own services, but they are no lo +### Amazon CloudWatch Observability Access Manager + + * `oam:sink` + + + + @@ -526,0 +575,9 @@ You can still use these resource types in their own services, but they are no lo +### AWS CodeDeploy + + * `codedeploy:application` + + * `codedeploy:deploymentconfig` + + + + @@ -601,0 +659,9 @@ You can still use these resource types in their own services, but they are no lo +### AWS Cost Explorer + + * `ce:anomalymonitor` + + * `ce:anomalysubscription` + + + + @@ -948,0 +1015,4 @@ You can still use these resource types in their own services, but they are no lo + * `events:archive` + + * `events:endpoint` + @@ -955,0 +1026,21 @@ You can still use these resource types in their own services, but they are no lo +### Amazon EventBridge Pipes + + * `pipes:pipe` + + + + +### Amazon EventBridge Scheduler + + * `scheduler:schedule-group` + + + + +### Amazon EventBridge Schemas + + * `schemas:discoverer` + + + + @@ -1021,0 +1113,2 @@ You can still use these resource types in their own services, but they are no lo + * `gamelift:location` + @@ -1077,0 +1171,2 @@ You can still use these resource types in their own services, but they are no lo + * `groundstation:mission-profile` + @@ -1098,0 +1194,11 @@ You can still use these resource types in their own services, but they are no lo +### AWS HealthOmics + + * `omics:referenceStore` + + * `omics:runGroup` + + * `omics:workflow` + + + + @@ -1128,0 +1235,7 @@ You can still use these resource types in their own services, but they are no lo +### Amazon Inspector + + * `inspector:target/template` + + + + @@ -1143,0 +1257,4 @@ You can still use these resource types in their own services, but they are no lo + * `iot:cacert` + + * `iot:cert` + @@ -1175,0 +1293,7 @@ You can still use these resource types in their own services, but they are no lo +### AWS IoT Core Device Advisor + + * `iotdeviceadvisor:suitedefinition` + + + + @@ -1186,0 +1311,11 @@ You can still use these resource types in their own services, but they are no lo +### AWS IoT FleetWise + + * `iotfleetwise:decoder-manifest` + + * `iotfleetwise:model-manifest` + + * `iotfleetwise:signal-catalog` + + + + @@ -1323,0 +1459,7 @@ You can still use these resource types in their own services, but they are no lo +### Amazon Managed Blockchain + + * `managedblockchain:accessors` + + + + @@ -1431,0 +1574,2 @@ You can still use these resource types in their own services, but they are no lo + * `personalize:solution` + @@ -1726,0 +1871,4 @@ You can still use these resource types in their own services, but they are no lo + * `transfer:certificate` + + * `transfer:connector` +