AWS Profile Config Generator
Build clean, valid AWS CLI credentials (~/.aws/credentials) and configuration (~/.aws/config) files. Support for IAM Access Keys, Assumed Roles, AWS SSO / Identity Center, custom S3 endpoints (Cloudflare R2, MinIO), regions, and output formats.
AWS Profile Config Generator
Build and manage multiple profiles for your ~/.aws/config and ~/.aws/credentials files.
[default]
region = us-east-1
output = json
[profile production]
region = us-west-2
output = json
role_arn = arn:aws:iam::123456789012:role/ProductionAdmin
source_profile = default
external_id = ext-prod-99aws s3 ls --profile default~/.aws/config vs ~/.aws/credentials
The AWS CLI and SDKs read two files. ~/.aws/credentials holds secrets: aws_access_key_id and aws_secret_access_key. ~/.aws/config holds everything else: region, output format, role_arn, source_profile, SSO settings, and service endpoints. Profiles in the config file are written as [profile name], except the default profile, which is [default]. In the credentials file every section is just [name].
Example config file
A typical setup has a default profile with a region, a named profile for an assumed role that uses role_arn and source_profile, and an SSO profile that points to an sso-session block with sso_start_url and sso_region. Run aws configure list-profiles to see every profile the CLI can find.
Profiles for Cloudflare R2 and MinIO
Set endpoint_url under the profile, or use a services block with s3 = endpoint_url = ..., so aws s3 commands reach R2 or MinIO without passing --endpoint-url every time. For R2 set region = auto. Then run aws s3 ls --profile r2 to test.
Use a profile
Pass --profile name to any AWS CLI command, or export AWS_PROFILE=name for the shell session. Desktop S3 clients such as BucketMate can read the same profiles, so one file serves the CLI, SDKs, and GUI.