iam-veeramalla / aws-devops-zero-to-hero Goto Github PK

I have been getting my hands on the recent AWS EKS hands-on project in which Abhishek is deploying the 2048 game onto a Kubernetes cluster. But the README.md doesn't have all the intralinks ready yet.

• Issue: This link is not working, as the section is not present in the README.md yet

Rename folders like 01-days for better indexing

There is wrong build command in the buildspec file in the line 15. There need to be - pip install -r day-14/simple-python-app/requirements.txt instead of - pip install -r day-13/simple-python-app/requirements.txt

The short URL Link on Readme looks easy to switch.
We can achieve the result with Complete Playlist on Youtube

In day-14/simple-python-app/app.py

For example:

from flask import Flask

app = Flask(__name__)


@app.route("/")
def hello():
    return "Hello, world!"


if __name__ == "__main__":
    app.run(port=5000, host="0.0.0.0")

Now I am able to curl app in ec2 in shell. But unable to access app outside EC2(Public)

any one faced this and fixed the issues.

just create the namespace
kubectl create serviceaccount aws-load-balancer-controller --namespace=kube-system
then the above-mentioned error will be resolved.

did anyone face an issue while associating iam -oidc ?

eksctl utils associate-iam-oidc-provider --cluster demo-cluster --approve
Error: unable to describe cluster control plane: operation error EKS: DescribeCluster, https response error StatusCode: 404, RequestID: a363bb46-4db6-49e2-a810-b8af86d3f65c, ResourceNotFoundException: No cluster found for name: demo-cluster.

• File: Prerequisites.md
• Issue: It should contain HELM as prerequisite which is a miss

12. Can you peer VPCs in different regions?
    No, VPC peering is limited to VPCs within the same region. To connect VPCs across regions, you would need to use VPN or AWS Direct Connect.

But AWS document says that we can peer the vpc across regions:
When you establish peering relationships between VPCs across different AWS Regions, resources in the VPCs (for example, EC2 instances and Lambda functions) in different AWS Regions can communicate with each other using private IP addresses, without using a gateway, VPN connection, or network appliance. The traffic remains in the private IP space.
https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html

Note: It's a great tutorial. Really appreciate your efforts. You are the real Guru !

I couldn't able to connect EC2 to mobxtream, IT"s show an error like=
Server refused our key
No supported authentication methods available (server sent: publickey)

this is error in above mentioned.

Hello Abhishek.Veeramalla,

Hope, you are doing well. First of all, I am really happy for what you are doing for free. I have faced a small issue related to lambda_handler function that must delete if there is not running EC2 instance and volume attached to it while following day 18 Cost Optimization video but when I run the code you provided it did not delete the snapshot since snapshot has volume id showing it even if the instance and volume are deleted then decided to write another script similar to yours and it worked well. Tested several times so if you find this issue workable then accept it so that other followers would not be confused or get stuck.

`
import boto3

def lambda_handler(event, context):
ec2 = boto3.client('ec2')

# Get all EBS snapshots
snapshots = ec2.describe_snapshots(OwnerIds=['self'])['Snapshots']

# Get all active EC2 instance and volume IDs
instances = ec2.describe_instances(Filters=[{'Name': 'instance-state-name', 'Values': ['running']}])['Reservations']
active_instance_volume_ids = set()

# Get active instance and volume IDs
for reservation in instances:
    for instance in reservation['Instances']:
        for volume in instance['BlockDeviceMappings']:
            active_instance_volume_ids.add(volume['Ebs']['VolumeId'])

# Iterate through snapshots and delete if not attached to any active instance or volume
deleted_snapshots_count = 0
for snapshot in snapshots:
    snapshot_id = snapshot['SnapshotId']
    volume_id = snapshot.get('VolumeId')
    
    if not volume_id or volume_id not in active_instance_volume_ids:
        # Delete the snapshot if it's not attached to any active instance or volume
        ec2.delete_snapshot(SnapshotId=snapshot_id)
        print(f"Deleted EBS snapshot {snapshot_id} as it was not attached to any active instance or volume.")
        deleted_snapshots_count += 1

return {
    'statusCode': 200,
    'body': f'Deleted {deleted_snapshots_count} unused EBS snapshots.'
}

`
Sincerely,
Zokhid