http://aws-core-labs.rofriday.com/20_build_deploy_goof/index.html Clone and Deploy the Sample Application Estimated Completion Time: 30 minutes Introduction In this module we will build our sample applications, push their container images to Amazon Elastic Container Registry (ECR), and deploy the application to Amazon Elastic Kubernetes Service (EKS). This will prepare us for Modules 2 and 3. Hugo en-US http://aws-core-labs.rofriday.com/20_build_deploy_goof/21_build_goof_images/index.html Mon, 01 Jan 0001 00:00:00 +0000 http://aws-core-labs.rofriday.com/20_build_deploy_goof/21_build_goof_images/index.html Now that you’ve cloned the repo to your working environment, we’ll build a few container images that run our application examples in Amazon Elastic Kubernetes Service (EKS) but before we can do anything, we need to create some ECR repositories to house the build images so EKS has somewhere to pull them from. Create the ECR repositories The following commands will create 3 repositories for the images we will be building: http://aws-core-labs.rofriday.com/20_build_deploy_goof/22_eks_deploy/index.html Mon, 01 Jan 0001 00:00:00 +0000 http://aws-core-labs.rofriday.com/20_build_deploy_goof/22_eks_deploy/index.html For the purpose of this workshop, we have created an Amazon EKS cluster on which we will run the “Goof apps” and you will now deploy the applications that we have built on it. Update the Kubeconfig file # update kubeconfig file aws eks update-kubeconfig --name $(aws eks list-clusters --query 'clusters[0]' --output text) Create and set context to a namespace We will be running these applications in a specific namespace. # Create a namespace kubectl create ns snyk-aws # Set the current context to use the new namespace kubectl config set-context --current --namespace snyk-aws # Verify snyk-aws Namespace was successfully created kubectl get ns $ kubectl get ns NAME STATUS AGE default Active 124m kube-node-lease Active 124m kube-public Active 124m kube-system Active 124m snyk-aws Active 113s 🚨 WARNING 🚨 ::alert[This workshop deploys a Log4Shell exploit server. This should never be ran in a Production Environment! Please ensure you understand the security implications and have taken appropriate precautions. Use in a controlled, isolated environment to avoid any unintended security risks.]{type=“warning”}