> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/glossary/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/glossary/a/access-key.md). # Access Key An access key is a set of credentials used to access and authenticate a user's account or resources in a cloud computing environment. It typically consists of an access key ID and a secret access key, which are used together to authenticate a user's identity and grant access to resources. They are typically used for programmatic access to resources, such as through APIs or command-line interfaces. Access keys can be created and managed by users themselves, or by administrators with appropriate permissions. They can also be revoked or deleted when no longer needed, helping to ensure security and protect against unauthorized access. Access keys are typically used in conjunction with other security measures, such as multi-factor authentication and access controls, to ensure that only authorized users have access to resources. They can be rotated periodically to help maintain security and reduce the risk of unauthorized access. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.console.zenlayer.com/glossary/a/access-key.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.