Check our terms and conditions, privacy policies, and cookies policy.
Copyright 2024 © All rights Reserved. Designed by LACNet
Creating EKS Cluster over private network using CloudFormation template.
https://lacchain-cft.s3.us-east-2.amazonaws.com/CFT-EKS-LN-1.1.yaml
Creating Identity Provider for EKS Cluster
Objective: Creating an identity provider for an Amazon Elastic Kubernetes Service (EKS) cluster. The identity provider is necessary for authenticating users and granting them access to the EKS cluster.
Prerequisites
Instructions
Below is a video guide for the following instructions:
.env
file will be used in the script to configure the deployment..env
file secure and do not share it with unauthorized individuals. It contains sensitive information related to your EKS cluster..env
file. Ensure that you have obtained the correct .env
file and filled up respective information from the CloudFormation EKS stack outputs and review the .env
file for node customization requirements. The script is responsible for deploying resources related to the EKS cluster and requires the .env
file containing the necessary information..env
is available at https://raw.githubusercontent.com/launchnodes/ln-lacchain/master/.env
.env
file with required information obtained from the CloudFormation stack outputs..env
File.env
file containing the required information (e.g., IP address, EKS cluster name, region, Node Name, Email address).
source <(curl -s -L https://raw.githubusercontent.com/launchnodes/ln-lacchain/master/deploy.sh) testnet
ops.sh
script. This script provides various commands that can be executed in the AWS Cloud Shell or a terminal environment. Here are the available commands:getPodRestart
: Use this command to restart the writer pods in the cluster.getEnodeId
: Use this command to obtain the Enode ID of the Writer Node.getNodeAddress
: Use this command to fetch the address of the Writer node.getConnectionStatus
: Use this command to check the status of the nodes’ connection.getbesuLogs
: Use this command to view the besu container logs To execute any of these commands, follow these steps:ops.sh
script available. If not follow stage 3 again. ops.sh
script is located.
source ops.sh
Check our terms and conditions, privacy policies, and cookies policy.
Copyright 2024 © All rights Reserved. Designed by LACNet