• Airlock Secure Access Hub
  • About this document
  • About Airlock IAM
  • IAM 8.3 release notes
  • Security best practices
  • Installation and upgrade
    • Quick start guide
    • Data sources
    • Installation on Linux
    • IAM as Docker image
      • Getting the Docker image
      • Container deployment
        • App parameters as ENV variables
        • Timezone
        • Separate ext. / int. containers
        • Logging
        • Resource limits and cgroups
      • External secrets
      • Storage and volumes
      • Examples
      • Troubleshooting
    • Upgrade Airlock IAM
  • Operation
  • Initial configuration
  • Configuration management
  • Authentication
  • Self-services
  • Target applications
  • OAuth and OIDC
  • SAML
  • API access control
  • Flows (Airlock IAM concept)
  • Loginapp Configuration
  • Adminapp Configuration
  • Service Container Configuration
  • Transaction Approval Configuration
  • IAM REST APIs
  • Customizing UIs and texts
  • Third-party licenses
  1. Installation and upgrade
  2. IAM as Docker image
  3. Container deployment
  4. Separate ext. / int. containers

Separate external/internal containers

For security reasons it is recommended to run external web application modules like Loginapp, and internal web applications, like Adminapp in separate Docker containers.

Airlock IAM provides a mechanism for that. See Sandboxing with profiles and the below.