You're Invited:Meet the Socket Team at BlackHat and DEF CON in Las Vegas, Aug 4-6.RSVP
Socket
Book a DemoInstallSign in
Socket

@aws-cdk/cli-plugin-contract

Package Overview
Dependencies
Maintainers
2
Versions
15
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@aws-cdk/cli-plugin-contract

Contract between the CLI and authentication plugins, for the exchange of AWS credentials

2.181.1
latest
Source
npmnpm
Version published
Weekly downloads
44K
-13.1%
Maintainers
2
Weekly downloads
 
Created
Source

AWS CDK CLI Library

cdk-constructs: Stable

Overview

As any piece of software that interacts with an AWS account, the CDK CLI needs AWS credentials for authentication and authorization. When it comes to choose which sources to get credentials from, it has the same behavior as the AWS CLI. But this basic behavior may result in some failure scenarios:

  • The initial set of credentials to work with cannot be obtained.
  • The account to which the initial credentials belong to cannot be obtained.
  • The account associated to the credentials is different from the account on which the CLI is trying to operate on.

Since these failures may happen for valid use case reasons, the CDK CLI offers an alternative mechanism for users to provide AWS credentials: credential provider plugins.

This package defines the types and the contract between the CLI and the plugins, which plugin authors are expected to adhere to.

The entrypoint is communicated to the CLI via the --plugin command line argument. The value of this argument should be a JavaScript file that, when require'd, will return an instance of the Plugin interface.

Once the CLI gets an instance of a plugin, it first initializes plugin by calling the Plugin.init() method, if one is defined. The CLI uses this method to pass an instance of IPluginHost to the plugin. The plugin, in turn, can use the repository to register one or more instances of CredentialProviderSource, which is where the actual logic for providing credentials is located.

If, in the authentication process, the CLI decides to use plugins, it will try each credential provider source in the order in which they were registered. For each source, the first thing the CLI will check is whether the source is ready to interact at all, by calling the isAvailable() method. If it is available, the next check is whether it can provide credentials for the specific account the CLI is targeting at that moment. This is the canProvideCredentials() method.

If both checks pass, the CLI asks the source for credentials by calling getProvider(). In addition to the account ID, this method also receives the Mode of operation, which can be ForReading or ForWriting. This information may be useful to tailor the credentials for the use case. For example, if the CLI needs the credentials only for reading, the plugin may return credentials with more restricted permissions.

Keywords

aws

FAQs

Package last updated on 16 Jul 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

About

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc

U.S. Patent No. 12,346,443 & 12,314,394. Other pending.