AWS apigateway documentation change
Summary
Added JSON formatting blocks and modified API Gateway ARN format by removing region specification
Security assessment
Formatting changes and ARN syntax correction improve documentation clarity but don't indicate security fixes or introduce security content
Diff
diff --git a/apigateway/latest/developerguide/api-gateway-control-access-using-iam-policies-to-invoke-api.md b/apigateway/latest/developerguide/api-gateway-control-access-using-iam-policies-to-invoke-api.md index fab62c4be..5967e690c 100644 --- a//apigateway/latest/developerguide/api-gateway-control-access-using-iam-policies-to-invoke-api.md +++ b//apigateway/latest/developerguide/api-gateway-control-access-using-iam-policies-to-invoke-api.md @@ -23,0 +24,6 @@ To control who can or cannot call a deployed API with IAM permissions, create an +JSON + + +**** + + @@ -47,0 +55,6 @@ For example, to grant a user permission to view a list of pets exposed by a spec +JSON + + +**** + + @@ -58 +71 @@ For example, to grant a user permission to view a list of pets exposed by a spec - "arn:aws:execute-api:us-east-1:account-id:api-id/*/GET/pets" + "arn:aws:execute-api::account-id:api-id/*/GET/pets" @@ -67 +80 @@ For example, to grant a user permission to view a list of pets exposed by a spec - "arn:aws:execute-api:us-east-1:account-id:api-id/*/POST/pets" + "arn:aws:execute-api::account-id:api-id/*/POST/pets" @@ -74,0 +89,6 @@ To grant a user permission to view a specific pet exposed by an API that is conf +JSON + + +**** + +