Відео

Glad I could help. Please stay tuned

Yes definitely you can, you have to handle the case inside your lambda functions and check for the http method and process accordingly

Glad it was helpful!

So nice of you

Yes, in the newer AWS Inspector, they streamlined the setup process compared to the older console. Now, AWS Inspector automatically scans your resources once it’s activated, making it much simpler and more straightforward to use. Here’s an overview of the updated setup process: 1. Activate Amazon Inspector: You just need to enable Amazon Inspector, and it will automatically start assessing supported resources like EC2 instances and ECR repositories in your account. 2. EC2 and IAM Setup: - Ensure that your EC2 instances have the appropriate IAM roles and permissions to allow Inspector to access and scan them. - AWS provides a managed policy, `AmazonInspector2ReadOnlyAccess`, that you can attach to an IAM role for users who need read-only access to Inspector findings. 3. No Need to Define Assessment Targets and Templates: - In the new version, Amazon Inspector automatically discovers resources and continuously assesses them for vulnerabilities and exposures. You no longer need to create assessment templates or targets manually. 4. Automatic Continuous Scanning: - Once activated, Inspector runs in the background and continuously monitors resources. It uses AWS Security Hub to consolidate findings, and you can view and manage these findings within the Inspector dashboard. So, yes, after activation, you no longer need to create assessment templates or targets manually. Inspector now handles those things automatically in the background for supported services, making it simpler and more efficient for ongoing security monitoring.

Glad to help

You mean custom data is it? Or you want to create a new table using Glue?

I will try my best

Yes you can do it definitely

There is a newer version currently I am working on. Will publish soon

Yes definitely its possible, Make sure you host the s3 website as static website then and lambda is needed.

Glad it was helpful!

Sure

Please check 11:28 minutes. I have explained how to do it.

Glad it helped

Thanks

In AWS console you will get that information in the landing page of EC2 if you select one of the resource. In the details section of the ec2

Thanks

Take a look into this discussion community.spiceworks.com/t/change-company-name-for-some-ad-users-from-a-csv-file/826810

Glad it was helpful!

Sorry, I don’t get you question

A new and updates version will come very soon. Stay tuned

Glad it was helpful!

Thanks a lot

Excellent question. Try Systems Manager. aws.amazon.com/blogs/mt/how-to-patch-windows-ec2-instances-in-private-subnets-using-aws-systems-manager/

Can you make video of this for linux

Will do

Glad you enjoyed it

You are most welcome

ua-cam.com/video/fYW-TQ9A2Lo/v-deo.html

Keep learning and gain experience. Follow my channel for real time projects and take up some courses online/offline.

Glad you liked it

Thanks for your comment. What exactly is your need? What are the services you are considering?

Glad it was helpful!

Glad to hear that

Thanks for liking

Check out other videos. Many of them are in cdk python

Check the description box

I will definitely try to

Yes sure, dis you check the description box?

@@beyondthecloud I beg your pardon, I cannot see any links to the source code. this is why I'm sending you this comment.

Can you please the description box?

You are welcome!

Cleaning up an Amazon EKS (Elastic Kubernetes Service) cluster using `eksctl` involves a few key steps, including deleting the cluster itself, associated node groups, and any related AWS resources. Here's a general guide on how to do it: ### Prerequisites 1. **Install `eksctl`:** Ensure you have `eksctl` installed. If not, you can install it following the instructions [here](eksctl.io/). 2. **AWS CLI:** Make sure you have the AWS CLI installed and configured with the appropriate credentials. ### Steps to Clean Up EKS Cluster 1. **Delete Nodegroups:** First, you may need to delete the node groups associated with the cluster. This step ensures that the worker nodes are terminated and their associated resources (like EC2 instances) are cleaned up. ```sh eksctl delete nodegroup --cluster=<cluster-name> --name=<nodegroup-name> ``` - Replace `<cluster-name>` with the name of your EKS cluster. - Replace `<nodegroup-name>` with the name of the node group. If you have multiple node groups, you'll need to run this command for each one. 2. **Delete Fargate Profiles:** If your cluster has any Fargate profiles, you should delete them as well: ```sh eksctl delete fargateprofile --cluster=<cluster-name> --name=<fargate-profile-name> ``` - Replace `<fargate-profile-name>` with the name of the Fargate profile. 3. **Delete the EKS Cluster:** After deleting node groups and Fargate profiles, you can delete the EKS cluster itself: ```sh eksctl delete cluster --name=<cluster-name> ``` This command deletes the EKS cluster and all its associated resources (like VPC, security groups, CloudFormation stacks, etc.) created by `eksctl`. ### Additional Cleanup While `eksctl` handles most of the cleanup, you may have additional resources associated with your EKS cluster, such as: - **Elastic Load Balancers (ELBs)** - **Amazon EFS volumes** - **ECR repositories** - **CloudWatch log groups** - **IAM roles and policies** These may need to be manually reviewed and deleted via the AWS Management Console or AWS CLI if not automatically removed. ### Verification After deletion, verify that all resources have been cleaned up to avoid unexpected charges. You can use the AWS Management Console, AWS CLI, or tools like AWS Cost Explorer to ensure no lingering resources remain. ### Example Script ```sh #!/bin/bash CLUSTER_NAME="your-cluster-name" # Delete node groups eksctl delete nodegroup --cluster=$CLUSTER_NAME --all # Delete Fargate profiles eksctl delete fargateprofile --cluster=$CLUSTER_NAME --all # Delete the cluster eksctl delete cluster --name=$CLUSTER_NAME ``` This script deletes all node groups and Fargate profiles before removing the cluster. ### Note Ensure you have backups or snapshots of any important data before deleting your cluster and its associated resources. This action is irreversible and will result in the loss of all data stored in the cluster.