eks-quickstart | AWS Cloud Development Kit and the AWS Elastic | Continuous Deployment library

by jasonumiker Python Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | eks-quickstart Summary

eks-quickstart is a Python library typically used in Devops, Continuous Deployment, Docker applications. eks-quickstart has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However eks-quickstart build file is not available. You can download it from GitHub.

This project is an example of how you can combine the AWS Cloud Development Kit (CDK) and the AWS Elastic Kubernetes Serivce (EKS) to quickly deploy a more complete and "production ready" Kubernetes environment on AWS. I describe it a bit more in a recent blog post -

Support

Quality

Security

License

Reuse

Support

eks-quickstart has a low active ecosystem.

It has 12 star(s) with 6 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 0 have been closed. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of eks-quickstart is current.

Quality

eks-quickstart has 0 bugs and 0 code smells.

Security

eks-quickstart has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

eks-quickstart code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

eks-quickstart is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

eks-quickstart releases are not available. You will need to build from source code and install.

eks-quickstart has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of eks-quickstart

Get all kandi verified functions for this library.

eks-quickstart Key Features

No Key Features are available at this moment for eks-quickstart.

eks-quickstart Examples and Code Snippets

No Code Snippets are available at this moment for eks-quickstart.

Community Discussions

Trending Discussions on eks-quickstart

How to modify the default capacity instance role for EKS using CDK?

QUESTION

How to modify the default capacity instance role for EKS using CDK?

Asked 2020-Jan-27 at 23:07

We're trying to setup logging using an EKS cluster. We're currently running a cluster with a single EC2 instance. AWS has provided kubectl commands that create the necessary kubernetes config.

When applying this to our existing EKS setup, we cannot properly define the instance role that has the permissions to write to CloudWatch.

the cloudwatch agent shows these errors in its pod logs:

...

ANSWER

Answered 2020-Jan-27 at 23:07

You can set the policy after creating the cluster on the DefaultCapacity

Source https://stackoverflow.com/questions/59643258

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install eks-quickstart

This project is an example of how you can combine the AWS Cloud Development Kit (CDK) and the AWS Elastic Kubernetes Serivce (EKS) to quickly deploy a more complete and "production ready" Kubernetes environment on AWS. I describe it a bit more in a recent blog post - https://jason-umiker.medium.com/automating-the-provisioning-of-a-production-ready-kubernetes-cluster-with-aws-eks-cdk-b1f0e8a12723.
You can either deploy this from your machine or leverge CodeBuild.
We've deployed Flux to deploy - and then keep in sync via GitOps - our default Gatekeeper policies and constraints. In order for that to work, though, we'll need to get the SSH key that Flux generated and add it to GitHub to give us the required access.
Connect to the Bastion via Systems Manager Session Manager or code-server
Run fluxctl identity --k8s-fwd-ns kube-system
Take the SSH key that has been ouput and add it to GitHub by following these instructions - https://docs.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account
(Optional) If you don't want to wait up to 5 minutes for Flux to sync you can run fluxctl sync --k8s-fwd-ns kube-system
If you set deploy_vpn to True in eks_cluster.py then the template will deploy a Client VPN. Note that you'll also need to create client and server certificates and upload them to ACM by following these instructions - https://docs.aws.amazon.com/vpn/latest/clientvpn-admin/client-authentication.html#mutual - and update ekscluster.py with the certificate ARNs for this to work.
Open the AWS VPC Console and go to the Client VPN Endpoints on the left panel
Click the Download Client Configuration button
Edit the downloaded file and add: A section at the bottom for the server cert in between and Then under that a section for the client private key between and
Install the AWS Client VPN Client - https://aws.amazon.com/vpn/client-vpn-download/
Create a new profile pointing it at that configuration file
Connect to the VPN

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: