CircleCI Ideas logo
CircleCI Ideas
Home
Feedback
Server
81

    Boards

  • Feature Requests

  • Server

  • Orbs

  • Images

  • Insights & Reporting

  • Documentation

  • API

  • Runner

  • Webhooks & Notifications

  • VS Code Extension

  • CLI

  • Config

  • CD & Release Orchestration

  • Identities & Permissions

Powered by Canny

Server

If you're unsure of which feedback category to select, please reference our guide in the changelog or use the ""uncategorized" bucket so we can get your feedback to the right team.
AWS ECR authentication using Nomad builder IAM instance profile
When using CCI Server, we have more freedom regarding Nomad builders, so we give the builder instances permissions to download any and all of our ECR images. What we would like is for the Docker executor the freedom to use those ECR images without any credentials passed either via project environment variables or contexts. However currently the CircleCI configuration is preventing us from doing that as it always requires an aws_access_key_id and aws_secret_access_key Ex. docker: - image: our_ecr_image:latest aws_auth: aws_access_key_id: AWS_ACCESS_KEY_ID aws_secret_access_key: AWS_SECRET_ACCESS_KEY Can we get a setting which will use the Nomad builder instance profile instead? docker: - image: our_ecr_image:latest aws_auth: use_instance_profile: true The AWS SDK uses any and all possible credential sources, so in theory if no credentials are passed it should use the Instance Metadata to authorize unless you intentionally block that. Thanks Igor Serko, Lyst Ltd
1
·

under review

Powered by Canny