cleanstart/aws-cli

Verified Publisher

By CleanStart

•Updated about 12 hours ago

Secure by Design, Built for Speed, Hardened Container Images on a minimal base CleanStart OS.

Image
Developer tools
0

50K+

cleanstart/aws-cli repository overview

CleanStart Container for AWS CLI

Official AWS Command Line Interface (CLI) container image providing a unified tool to manage AWS services. This enterprise-ready container includes the latest AWS CLI v2, with support for all AWS services and commands. Features include AWS IAM authentication, S3 operations, EC2 management, and other AWS service interactions. Built on a security-hardened base image with minimal attack surface and FIPS-compliant cryptographic modules.

šŸ“Œ CleanStart Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments.

Key Features

  • Complete AWS CLI v2 functionality with all service commands
  • Built-in credential management and AWS IAM integration
  • Support for AWS profiles and configuration
  • FIPS 140-2 compliant cryptographic modules for secure operations

Common Use Cases

  • Automated AWS infrastructure management and deployment
  • S3 bucket operations and file transfers
  • EC2 instance management and monitoring
  • CloudFormation stack deployment and updates

Quick Start

Pull Latest Image Download the container image from the registry

docker pull cleanstart/aws-cli:latest
docker pull cleanstart/aws-cli:latest-dev

Basic Run Run the container with basic configuration

docker run -it --name aws-cli-test cleanstart/aws-cli:latest-dev --version

Production Deployment Deploy with production security settings

docker run -d --name aws-cli-prod \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  -v ~/.aws:/home/aws/.aws:ro \
  cleanstart/aws-cli:latest

Volume Mount Mount AWS credentials and working directory

docker run -v ~/.aws:/home/aws/.aws:ro -v $(pwd):/workspace cleanstart/aws-cli:latest

Port Forwarding Run with custom port mappings

docker run -p 8080:80 cleanstart/aws-cli:latest

Configuration

Environment Variables

VariableDefaultDescription
PATH/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binSystem PATH configuration
AWS_PROFILEdefaultAWS credentials profile to use
AWS_DEFAULT_REGIONus-east-1Default AWS region for operations

Security & Best Practices

Recommended Security Context

securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  runAsGroup: 1000
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ['ALL']

Best Practices

  • Use specific image tags for production (avoid latest)
  • Configure resource limits: memory and CPU constraints
  • Enable read-only root filesystem when possible
  • Run containers with non-root user (--user 1000:1000)
  • Use --security-opt=no-new-privileges flag
  • Regularly update container images for security patches
  • Implement proper network segmentation
  • Monitor container metrics for anomalies

Architecture Support

Multi-Platform Images

docker pull --platform linux/amd64 cleanstart/aws-cli:latest
docker pull --platform linux/arm64 cleanstart/aws-cli:latest

⁠Documentation Resources

Essential links and resources for further information

CleanStart Images: https://images.cleanstart.com/⁠

Community Images:
Docker Hub: https://hub.docker.com/u/cleanstart⁠
GitHub: https://github.com/cleanstart-containers⁠
AWS ECR Public Gallery: https://gallery.ecr.aws/cleanstart/⁠

Presence on Social Media:
Community: https://www.linkedin.com/groups/18324021/⁠
YouTube: https://www.youtube.com/@CleanStartOfficial⁠

Contribute to Container Use Cases: https://github.com/cleanstart-dev/cleanstart-use-cases/⁠

⁠Vulnerability Disclaimer

CleanStart offers Docker images that include third-party open-source libraries and packages maintained by independent contributors. While CleanStart maintains these images and applies industry-standard security practices, it cannot guarantee the security or integrity of upstream components beyond its control.

Users acknowledge and agree that open-source software may contain undiscovered vulnerabilities or introduce new risks through updates. CleanStart shall not be liable for security issues originating from third-party libraries, including but not limited to zero-day exploits, supply chain attacks, or contributor-introduced risks.

Security remains a shared responsibility: CleanStart provides updated images and guidance where possible, while users are responsible for evaluating deployments and implementing appropriate controls.

Tag summary

Content type

Image

Digest

sha256:81e81572a…

Size

79.2 MB

Last updated

about 12 hours ago

docker pull cleanstart/aws-cli:2.36.1-arm64