Get started
Yandex Identity and Access Management

Method list

Written by

Retrieves the list of access keys for the specified service account.

HTTP request

GET https://iam.api.cloud.yandex.net/iam/aws-compatibility/v1/accessKeys

Query parameters

Parameter Description
serviceAccountId ID of the service account to list access keys for. To get the service account ID, use a list request. If not specified, it defaults to the subject that made the request. The maximum string length in characters is 50.
pageSize The maximum number of results per page to return. If the number of available results is larger than pageSize, the service returns a nextPageToken that can be used to get the next page of results in subsequent list requests. Default value: 100. The maximum value is 1000.
pageToken Page token. To get the next page of results, set pageToken to the nextPageToken returned by a previous list request. The maximum string length in characters is 100.

Response

HTTP Code: 200 - OK

{
  "accessKeys": [
    {
      "id": "string",
      "serviceAccountId": "string",
      "createdAt": "string",
      "description": "string",
      "keyId": "string"
    }
  ],
  "nextPageToken": "string"
}
Field Description
accessKeys[] object

An access key. For more information, see AWS-compatible access keys.
accessKeys[].
id		 string

ID of the AccessKey resource. It is used to manage secret credentials: an access key ID and a secret access key.
accessKeys[].
serviceAccountId		 string

ID of the service account that the access key belongs to.
accessKeys[].
createdAt		 string (date-time)

Creation timestamp.

String in RFC3339 text format.
accessKeys[].
description		 string

Description of the access key. 0-256 characters long.
accessKeys[].
keyId		 string

ID of the access key. The key is AWS compatible.
nextPageToken string

This token allows you to get the next page of results for list requests. If the number of results is larger than pageSize, use the nextPageToken as the value for the pageToken query parameter in the next list request. Each subsequent list request will have its own nextPageToken to continue paging through the results.
In this article: