Home
Implementation Guides
Implementation Guide for Red Hat JBoss Enterprise Application Platform
Using AWS Secrets and Configuration Provider with Kubernetes Secret Store CSI Driver
AWS Secrets Manager securely retrieves secrets from the AWS Secrets Manager for Amazon Elastic Kubernetes Service (Amazon EKS) Kubernetes pods.

Implementation Guides
- Implementation Guide for Apache Tomcat
- Implementation Guide for Red Hat JBoss Enterprise Application Platform
  - Cloud Native Unica Overview
  - Docker, Kubernetes, and Helm
    In this release, we have implemented Cloud Native Unica using Docker, Kubernetes, and Helm.
  - ELK Overview
    The ELK Stack is a collection of three open-source products: Elasticsearch, Logstash, and Kibana.
  - Pre-installation configurations
    Before installing or upgrading to Cloud Native Unica, you should complete some configurations.
  - Cloud Native Unica Helm release architecture
    The following is a diagrammatic representation of the Cloud Native Unica Helm release architecture:
  - Helm chart configuration
    Before you start the installation or upgrade of Cloud Native Unica, you should configure the appropriate configMap YAML files.
  - Installation and verifying the installation
  - Post installation configurations
    The following topics contain details about post installation configurations related to the products of Unica.
  - Migration of on-premises applications to Cloud Native Unica
  - Cloud Native Unica upgrade
    To upgrade an earlier version of Cloud Native Unica to a newer version, complete the following steps:
  - Scaling Unica containers
    Scaling a deployment ensures creation and scheduling of new Pods. Scaling increases the number of Pods to the new required state. Kubernetes also supports autoscaling of Pods.
  - Deployment monitoring
    The Kubernetes Dashboard is a web-based user interface to monitor deployments.
  - Using Red Hat OpenShift
    You can use OpenShift to develop and runcontainerized applications. OpenShift allows applications, and the data centers that support them, to expand from just a few machines and applications to thousands of machines that serve millions of clients.
  - Product utilities
    You can execute all the utilities of the Unica products in their assigned pods.
  - Using secret to avoid passwords in plain text
    To use a secret to avoid using passwords in plain text, complete the following steps:
  - Using AWS Secrets and Configuration Provider with Kubernetes Secret Store CSI Driver
    AWS Secrets Manager securely retrieves secrets from the AWS Secrets Manager for Amazon Elastic Kubernetes Service (Amazon EKS) Kubernetes pods.
    - AWS Secret Manager Implementation
      To implement AWS Secret Manager, ensure that the prerequisites are met and the configurations are executed.
  - Enabling Multicast using Weave-Net CNI plugin on AWS EKS cluster
    You can enable multicasting on AWS EKS cluster only for Kubernetes versions 1.21 or above,
  - FAQs and troubleshooting
    This section covers the frequently asked questions and troubleshooting issues.
  - Uninstalling the chart
  - Appendix: Description of Helm chart parameters
    The following topics contain description of the parameters present in the configMap YAML files:
- Implementation Guide for Oracle WebLogic Server

Using AWS Secrets and Configuration Provider with Kubernetes Secret Store CSI Driver

AWS Secrets Manager securely retrieves secrets from the AWS Secrets Manager for Amazon Elastic Kubernetes Service (Amazon EKS) Kubernetes pods.

AWS Secrets and Config Provider (ASCP) contains an an easy-to-use plugin that provides secrets to applications that operate on Amazon EKS. The plugin supports industry-standard Kubernetes Secrets Store and Container Storage Interface (CSI) driver.

The benefits of ASCP are as follows:

Provides compatibility for legacy Kubernetes workloads that fetched secrets through the file system or etcd.
Securely store and manage your secrets in Secrets Manager.
Retrieve secrets, using applications that run on Kubernetes, without writing a custom code.
Use AWS Identity and Access Management (IAM) and resource policies on your secret to limit and restrict access to specific Kubernetes pods inside a cluster to tightly control secrets accessible by the pods.

AWS Secrets Manager Working Concept with Unica

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.