openapi: 3.0.0 info: version: 2015-07-09 x-release: v4 title: 'APIs.io Engineering Platform Amazon API Gateway 2014 11 13 #Action=CreateAccessKey API' description: Amazon API Gateway

Amazon API Gateway helps developers deliver robust, secure, and scalable mobile and web application back ends. API Gateway allows developers to securely connect mobile and web applications to APIs that run on AWS Lambda, Amazon EC2, or other publicly addressable web services that are hosted outside of AWS.

x-logo: url: https://api.apis.guru/v2/cache/logo/https_twitter.com_awscloud_profile_image.png backgroundColor: '#FFFFFF' termsOfService: https://aws.amazon.com/service-terms/ contact: name: Mike Ralphson email: mike.ralphson@gmail.com url: https://github.com/mermade/aws2openapi x-twitter: PermittedSoc license: name: Apache 2.0 License url: http://www.apache.org/licenses/ x-providerName: amazonaws.com x-serviceName: apigateway x-origin: - contentType: application/json url: https://raw.githubusercontent.com/aws/aws-sdk-js/master/apis/apigateway-2015-07-09.normal.json converter: url: https://github.com/mermade/aws2openapi version: 1.0.0 x-apisguru-driver: external x-apiClientRegistration: url: https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_ct x-apisguru-categories: - cloud x-preferred: true servers: - url: http://apigateway.{region}.amazonaws.com variables: region: description: The AWS region enum: - us-east-1 - us-east-2 - us-west-1 - us-west-2 - us-gov-west-1 - us-gov-east-1 - ca-central-1 - eu-north-1 - eu-west-1 - eu-west-2 - eu-west-3 - eu-central-1 - eu-south-1 - af-south-1 - ap-northeast-1 - ap-northeast-2 - ap-northeast-3 - ap-southeast-1 - ap-southeast-2 - ap-east-1 - ap-south-1 - sa-east-1 - me-south-1 default: us-east-1 description: The Amazon API Gateway multi-region endpoint - url: https://apigateway.{region}.amazonaws.com variables: region: description: The AWS region enum: - us-east-1 - us-east-2 - us-west-1 - us-west-2 - us-gov-west-1 - us-gov-east-1 - ca-central-1 - eu-north-1 - eu-west-1 - eu-west-2 - eu-west-3 - eu-central-1 - eu-south-1 - af-south-1 - ap-northeast-1 - ap-northeast-2 - ap-northeast-3 - ap-southeast-1 - ap-southeast-2 - ap-east-1 - ap-south-1 - sa-east-1 - me-south-1 default: us-east-1 description: The Amazon API Gateway multi-region endpoint - url: http://apigateway.{region}.amazonaws.com.cn variables: region: description: The AWS region enum: - cn-north-1 - cn-northwest-1 default: cn-north-1 description: The Amazon API Gateway endpoint for China (Beijing) and China (Ningxia) - url: https://apigateway.{region}.amazonaws.com.cn variables: region: description: The AWS region enum: - cn-north-1 - cn-northwest-1 default: cn-north-1 description: The Amazon API Gateway endpoint for China (Beijing) and China (Ningxia) security: - hmac: [] tags: - name: '#Action=CreateAccessKey' paths: /#Action=CreateAccessKey: parameters: - $ref: '#/components/parameters/X-Amz-Content-Sha256' - $ref: '#/components/parameters/X-Amz-Date' - $ref: '#/components/parameters/X-Amz-Algorithm' - $ref: '#/components/parameters/X-Amz-Credential' - $ref: '#/components/parameters/X-Amz-Security-Token' - $ref: '#/components/parameters/X-Amz-Signature' - $ref: '#/components/parameters/X-Amz-SignedHeaders' get: x-aws-operation-name: CreateAccessKey operationId: GET_CreateAccessKey description:

Creates a new Amazon Web Services secret access key and corresponding Amazon Web Services access key ID for the specified user. The default status for new keys is Active.

If you do not specify a user name, IAM determines the user name implicitly based on the Amazon Web Services access key ID signing the request. This operation works for access keys under the Amazon Web Services account. Consequently, you can use this operation to manage Amazon Web Services account root user credentials. This is true even if the Amazon Web Services account has no associated users.

For information about quotas on the number of keys you can create, see IAM and STS quotas in the IAM User Guide.

To ensure the security of your Amazon Web Services account, the secret access key is accessible only during key and user creation. You must save the key (for example, in a text file) if you want to be able to access it again. If a secret key is lost, you can delete the access keys for the associated user and then create new keys.

responses: '200': description: Success content: text/xml: schema: $ref: '#/components/schemas/CreateAccessKeyResponse' '480': description: NoSuchEntityException content: text/xml: schema: $ref: '#/components/schemas/NoSuchEntityException' '481': description: LimitExceededException content: text/xml: schema: $ref: '#/components/schemas/LimitExceededException' '482': description: ServiceFailureException content: text/xml: schema: $ref: '#/components/schemas/ServiceFailureException' parameters: - name: UserName in: query required: false description: '

The name of the IAM user that the new key will belong to.

This parameter allows (through its regex pattern) a string of characters consisting of upper and lowercase alphanumeric characters with no spaces. You can also include any of the following characters: _+=,.@-

' schema: type: string pattern: '[\w+=,.@-]+' minLength: 1 maxLength: 128 - name: Action in: query required: true schema: type: string enum: - CreateAccessKey - name: Version in: query required: true schema: type: string enum: - 2010-05-08 tags: - '#Action=CreateAccessKey' post: x-aws-operation-name: CreateAccessKey operationId: POST_CreateAccessKey description:

Creates a new Amazon Web Services secret access key and corresponding Amazon Web Services access key ID for the specified user. The default status for new keys is Active.

If you do not specify a user name, IAM determines the user name implicitly based on the Amazon Web Services access key ID signing the request. This operation works for access keys under the Amazon Web Services account. Consequently, you can use this operation to manage Amazon Web Services account root user credentials. This is true even if the Amazon Web Services account has no associated users.

For information about quotas on the number of keys you can create, see IAM and STS quotas in the IAM User Guide.

To ensure the security of your Amazon Web Services account, the secret access key is accessible only during key and user creation. You must save the key (for example, in a text file) if you want to be able to access it again. If a secret key is lost, you can delete the access keys for the associated user and then create new keys.

responses: '200': description: Success content: text/xml: schema: $ref: '#/components/schemas/CreateAccessKeyResponse' '480': description: NoSuchEntityException content: text/xml: schema: $ref: '#/components/schemas/NoSuchEntityException' '481': description: LimitExceededException content: text/xml: schema: $ref: '#/components/schemas/LimitExceededException' '482': description: ServiceFailureException content: text/xml: schema: $ref: '#/components/schemas/ServiceFailureException' requestBody: content: text/xml: schema: $ref: '#/components/schemas/CreateAccessKeyRequest' parameters: - name: Action in: query required: true schema: type: string enum: - CreateAccessKey - name: Version in: query required: true schema: type: string enum: - 2010-05-08 tags: - '#Action=CreateAccessKey' components: parameters: X-Amz-Signature: name: X-Amz-Signature in: header schema: type: string required: false X-Amz-Content-Sha256: name: X-Amz-Content-Sha256 in: header schema: type: string required: false X-Amz-Algorithm: name: X-Amz-Algorithm in: header schema: type: string required: false X-Amz-Security-Token: name: X-Amz-Security-Token in: header schema: type: string required: false X-Amz-SignedHeaders: name: X-Amz-SignedHeaders in: header schema: type: string required: false X-Amz-Credential: name: X-Amz-Credential in: header schema: type: string required: false X-Amz-Date: name: X-Amz-Date in: header schema: type: string required: false schemas: statusType: type: string enum: - Active - Inactive CreateAccessKeyResponse: type: object required: - AccessKey example: AccessKey: AccessKeyId: AKIAIOSFODNN7EXAMPLE CreateDate: 2015-03-09 18:39:23.411000+00:00 SecretAccessKey: wJalrXUtnFEMI/K7MDENG/bPxRfiCYzEXAMPLEKEY Status: Active UserName: Bob properties: AccessKey: allOf: - $ref: '#/components/schemas/AccessKey' - description: A structure with details about the access key. description: 'Contains the response to a successful CreateAccessKey request. ' AccessKey: type: object required: - UserName - AccessKeyId - Status - SecretAccessKey properties: UserName: allOf: - $ref: '#/components/schemas/userNameType' - description: The name of the IAM user that the access key is associated with. AccessKeyId: allOf: - $ref: '#/components/schemas/accessKeyIdType' - description: The ID for this access key. Status: allOf: - $ref: '#/components/schemas/statusType' - description: 'The status of the access key. Active means that the key is valid for API calls, while Inactive means it is not. ' SecretAccessKey: allOf: - $ref: '#/components/schemas/accessKeySecretType' - description: The secret key used to sign requests. CreateDate: allOf: - $ref: '#/components/schemas/dateType' - description: The date when the access key was created. description:

Contains information about an Amazon Web Services access key.

This data type is used as a response element in the CreateAccessKey and ListAccessKeys operations.

The SecretAccessKey value is returned only in response to CreateAccessKey. You can get a secret access key only when you first create an access key; you cannot recover the secret access key later. If you lose a secret access key, you must create a new access key.

userNameType: type: string pattern: '[\w+=,.@-]+' minLength: 1 maxLength: 64 LimitExceededException: {} accessKeyIdType: type: string pattern: '[\w]+' minLength: 16 maxLength: 128 NoSuchEntityException: {} dateType: type: string format: date-time accessKeySecretType: type: string format: password ServiceFailureException: {} existingUserNameType: type: string pattern: '[\w+=,.@-]+' minLength: 1 maxLength: 128 CreateAccessKeyRequest: type: object title: CreateAccessKeyRequest properties: UserName: allOf: - $ref: '#/components/schemas/existingUserNameType' - description: '

The name of the IAM user that the new key will belong to.

This parameter allows (through its regex pattern) a string of characters consisting of upper and lowercase alphanumeric characters with no spaces. You can also include any of the following characters: _+=,.@-

' securitySchemes: hmac: type: apiKey name: Authorization in: header description: Amazon Signature authorization v4 x-amazon-apigateway-authtype: awsSigv4 externalDocs: description: Amazon Web Services documentation url: https://docs.aws.amazon.com/apigateway/ x-hasEquivalentPaths: true