aws-cdk.asset-awscli-v1
A library that contains the AWS CLI for use in Lambda Layers
Decision gist · record as of 2026-08-14
Yes, if you are using AWS CDK to manage Lambda functions that require AWS CLI v1. The package is actively maintained, has low install friction, and eliminates manual CLI packaging. Not necessary if your Lambda functions do not need CLI access or if you prefer AWS CLI v2.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Lambda functions using this asset must use a Python 3.x runtime; requires AWS CDK and aws-cdk-lib installed.
- Active maintenance with a recent release (4 days old).
- Low install friction with only two runtime dependencies (jsii and publication).
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows commercial and private use with minimal restrictions; suitable for most projects.
last release 2026-08-10 (4 days) · last repo commit 2026-08-14 · 8 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 11,104,828 downloads/mo, #1,416 on PyPI
Alternatives
Verify before relying
import { ASSET_FILE, LAYER_SOURCE_DIR } from 'aws-cdk-asset-awscli-v1';
import * as lambda from 'aws-cdk-lib/aws-lambda';
import * as s3_assets from 'aws-cdk-lib/aws-s3-assets';
import { FileSystem } from 'aws-cdk-lib';
const asset = new s3_assets.Asset(this, 'layer-asset', {
path: ASSET_FILE,
assetHash: FileSystem.fingerprint(LAYER_SOURCE_DIR),
});
fn.addLayers(new lambda.LayerVersion(this, 'AwsCliLayer', {
code: lambda.Code.fromBucket(asset.bucket, asset.s3ObjectKey),
}));- Whether AWS CLI v1 receives security updates or is in maintenance-only mode
- Performance impact of bundling CLI v1 in Lambda layers relative to alternative approaches
What it is and what it does
This package provides a pre-built AWS CLI v1 asset designed to be consumed by AWS CDK constructs, specifically for use in Lambda Layers. It exposes two constants—ASSET_FILE and LAYER_SOURCE_DIR—that point to the bundled CLI and its source directory, allowing developers to easily add AWS CLI functionality to Lambda functions without manually packaging the CLI themselves.
The asset installs the CLI under /opt/awscli/aws within the Lambda layer, making it available to Lambda functions at runtime. It's built for modern Python versions (3.10 through 3.14) and integrates directly with CDK's Asset and LayerVersion constructs, reducing boilerplate and ensuring consistent CLI packaging across CDK-based infrastructure projects.
Use it for
- Add AWS CLI v1 to Lambda functions that need to invoke AWS services directly during execution
- Build Lambda layers that share a consistent AWS CLI version across multiple functions in a CDK stack
- Simplify packaging of CLI-dependent Lambda code by using pre-built, versioned assets instead of custom layers
- Ensure reproducible Lambda deployments by pinning a specific AWS CLI v1 version through CDK asset management
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are using AWS CDK to manage Lambda functions that require AWS CLI v1.
The package is actively maintained, has low install friction, and eliminates manual CLI packaging. Not necessary if your Lambda functions do not need CLI access or if you prefer AWS CLI v2.
Install
aws-cdk-asset-awscli-v1 on PyPI
Before you install
Active maintenance with a recent release (4 days old). Low install friction with only two runtime dependencies (jsii and publication). Supports Python 3.10 through 3.14.
Lambda functions using this asset must use a Python 3.x runtime; requires AWS CDK and aws-cdk-lib installed.
License in practice
Apache-2.0 permissive license allows commercial and private use with minimal restrictions; suitable for most projects.
Quickstart
import { ASSET_FILE, LAYER_SOURCE_DIR } from 'aws-cdk-asset-awscli-v1';
import * as lambda from 'aws-cdk-lib/aws-lambda';
import * as s3_assets from 'aws-cdk-lib/aws-s3-assets';
import { FileSystem } from 'aws-cdk-lib';
const asset = new s3_assets.Asset(this, 'layer-asset', {
path: ASSET_FILE,
assetHash: FileSystem.fingerprint(LAYER_SOURCE_DIR),
});
fn.addLayers(new lambda.LayerVersion(this, 'AwsCliLayer', {
code: lambda.Code.fromBucket(asset.bucket, asset.s3ObjectKey),
}));Verify before relying
- Whether AWS CLI v1 receives security updates or is in maintenance-only mode
- Performance impact of bundling CLI v1 in Lambda layers relative to alternative approaches
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesjsiipublication |
| Maintenance | Actively maintained 4 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 11,104,828 / month, #1,416 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableIntended Audience :: DevelopersLicense :: OSI ApprovedOperating System :: OS IndependentProgramming Language :: JavaScriptProgramming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Typing :: Typed |
Evidence: aws_cdk_asset_awscli_v1-2.2.293-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “aws cli lambda layer”
- aws-cdk.asset-awscli-v1Bundles AWS CLI v1 as a reusable asset for AWS CDK Lambda Layers,…
- aws-cdk.lambda-layer-kubectl-v35Provides a Lambda Layer packaging kubectl v1.35.2 and Helm v4.1.3 for…
- aws-cdk.asset-node-proxy-agent-v6Bundles the NPM proxy-agent package (version 6.3.0) as an AWS Lambda…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also aws-cdk.asset-node-proxy-agent-v6 · aws-cdk.asset-node-proxy-agent-v5 · aws-cdk.asset-kubectl-v20 · aws-cdk.lambda-layer-kubectl-v35 · aws-cdk.aws-s3-assets · aws-cdk.aws-lambda · aws-cdk.aws-lambda-python-alpha · aws-cdk.aws-imagebuilder · aws-cdk.aws-ecr-assets · aws-cdk.aws-autoscaling-common