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
  • Create an Amazon AMI to deploy manually in EC2
  • Deploy with Terraform
  • Deploy to ECS with a Docker Image
  • Deploy with AWS CDK (AWS Cloud Development Kit)

Was this helpful?

Deployment Strategies

PreviousManaging DependenciesNextContributing

Last updated 3 years ago

Was this helpful?

Each organization is different in how they would wish to deploy ConsoleMe, and which specific operating system or base image they would want to deploy ConsoleMe on. We don't currently support or recommend any specific deployment flows. But we have a few resources that might help you get started. Help is definitely wanted in this area, so please contribute if you have guidance in this area.

Create an Amazon AMI to deploy manually in EC2

ConsoleMe includes an example Packer configuration to assist with creating an image. You'll want to craft a custom configuration for ConsoleMe before creating an image, or be prepared to SSH into the instance you create to debug. Ensure that you have , and valid AWS credentials configured for the account you want the AMI deployed to.

To create an image with Packer, run the following command in the ConsoleMe repository:

make create_ami

Deploy with Terraform

ConsoleMe has that can assist you with deploying ConsoleMe in a central account, and creating the roles that ConsoleMe needs in your spoke accounts. The central account configuration does not currently handle ACM (for TLS certificates), Route53, or load balancing.

Deploy to ECS with a Docker Image

ConsoleMe has an example that you can use to generate a docker image with for ConsoleMe. You'll need to craft your own ConsoleMe configuration.

Deploy with AWS CDK (AWS Cloud Development Kit)

ConsoleMe has that can assist you with deploying ConsoleMe in a central account, and creating the roles that ConsoleMe needs in your spoke accounts. The central account configuration handles ACM (for TLS certificates), Route53, load balancing, DynamoDB tables, Redis cache, authentication via Cognito and configuration storage in S3 bucket.

Packer installed
example Terraform files
docker-compose deployment file
example CDK files