ConsoleMe
GitHub
  • About
  • Architecture
  • Features
    • Credentials
      • AWS Console Login
      • AWS Credential Broker
    • Policy Management
      • Policies View
      • Policy Editor for IAM, SQS, SNS, and S3
      • Self-Service IAM Wizard
      • Policy Request - Review Page
      • Role Creation and Cloning
  • Demo
  • Quick Start
    • Docker
    • Local
  • Prerequisites
    • Required IAM Permissions
      • Central Account
      • Spoke Accounts
  • Configuration
    • Web App Authentication and Authorization
      • Local Development (Auth bypass)
      • ALB Auth (Recommended)
      • Retrieving Google Groups
      • OIDC/OAuth2
        • Cognito
        • Okta
      • SAML
      • Plain-Text Headers
    • Role Credential Authorization
      • Role Tags
        • Role Tagging Service Control Policy (Recommended)
      • Role Authorization through Dynamic Configuration
      • Custom Authorization (Internal Plugin)
    • Account Syncing
    • Metrics
    • Dynamic Configuration
    • AWS Resource Syncing
    • CLI Authentication
    • Sending email through SES
    • AWS Secret Manager Integration
    • CloudTrail Integration via AWS Event Bridge
    • Slack Notifications
  • Celery Tasks
    • Celery Flower
  • Development Guide
    • UI Components
    • Managing Dependencies
  • Deployment Strategies
  • Contributing
  • FAQ
  • License
  • Security
  • Weep CLI
    • Getting Started with Weep
    • AWS Credentials in the CLI using Weep and ConsoleMe
    • Configuration
    • Commands
      • List
      • Serve
      • Export
      • File
      • Credential Process
    • Assuming Roles
    • Advanced Configuration
      • Routing for Metadata Service
      • Shell Completion
Powered by GitBook
On this page

Was this helpful?

  1. Configuration

AWS Secret Manager Integration

PreviousSending email through SESNextCloudTrail Integration via AWS Event Bridge

Last updated 3 years ago

Was this helpful?

If you'd like to add secrets to ConsoleMe's configuration, we recommend using our AWS Secrets Manager integration. Using this is simple:

  1. Make a YAML file that contains the secrets that you would like to merge into your ConsoleMe configuration.

oidc_secrets:
  client_id: oidc_client_id
  secret: 12345SuperS3KrET!1
  client_scope:
    - email
    - openid
jwt_secret: "ConsoleMeJwtSigningSecret"
  1. Add this secret to AWS Secrets Manager

The secret that you store in AWS Secrets Manager must be valid YAML.

  1. Give permissions to your role (The role that the ConsoleMe service uses on-instance) to read your new secret

  2. Modify your ConsoleMe Configuration YAML to reference this secret in an extends parameter.

Example:

extends: 
  - AWS_SECRETS_MANAGER:my_secret_name_1
  
auth:
  get_user_by_oidc: true
  set_auth_cookie: true
.... Other configuration

Deploy ConsoleMe. If you're deploying the vanilla ConsoleMe docker image, you can specify an environment variable with an S3 location that ConsoleMe can download it's configuration from. More details are in the section.

Central Account
Configuration