Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

APIs.io Engineering Platform #Action=DeleteRolePermissionsBoundary API

The #Action=DeleteRolePermissionsBoundary API from APIs.io Engineering Platform — 1 operation(s) for #action=deleterolepermissionsboundary.

This API exposes 2 operations across 1 path, and defines 5 schemas. It is described by OpenAPI 3.0.0, at version 2015-07-09.

Requests are made against 4 base URLs: http://apigateway.{region}.amazonaws.com, https://apigateway.{region}.amazonaws.com, http://apigateway.{region}.amazonaws.com.cn, https://apigateway.{region}.amazonaws.com.cn.

2 operations 1 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2015-07-09
Base URL
https://{bucketname}.s3.amazonaws.com
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

APIs.io Engineering Platform #Action=DeleteRolePermissionsBoundary API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (hmac). By default, every request must be authenticated.

  • hmac — Amazon Signature authorization v4

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

#Action=DeleteRolePermissionsBoundary 2
GET
/#Action=DeleteRolePermissionsBoundary
Deletes the permissions boundary for the specified IAM role. You cannot set the boundary for a service-linked role. Deleting the permissions boundary for a role might increase its permissions. For ex…
GET_DeleteRolePermissionsBoundary 10 params → 200480481482
POST
/#Action=DeleteRolePermissionsBoundary
Deletes the permissions boundary for the specified IAM role. You cannot set the boundary for a service-linked role. Deleting the permissions boundary for a role might increase its permissions. For ex…
POST_DeleteRolePermissionsBoundary 9 params body → 200480481482

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed is DeleteRolePermissionsBoundaryRequest (1 property). Each schema is shown below with its type and property counts.

DeleteRolePermissionsBoundaryRequest
object
1 property 1 required
UnmodifiableEntityException
NoSuchEntityException
roleNameType
string
ServiceFailureException

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

engineering-platform-action-deleterolepermissionsboundary-api-openapi.yml Raw ↑