Sudheer Satyanarayana's questions

I have a subscription, resource group and a VM. Let's call this VM as vm-01.

From the VM, I want to access Azure Storage containers and objects. I have installed the Azure CLI on this Linux VM.

Is it possible to access the storage service from the VM by using RBAC? I want execute commands like:

az storage container list

The documents I have read all point to using Azure Active Directory. I do not have Azure Active Directory service for this subscription and resource group.

I was thinking I could create a custom role and assign it to the VM. I was able to create the custom role and provide the required storage permissions to the role. However, I am not able to assign the custom role to the VM. In the Azure console, I see only options to assign the Azure Managed identities.

I am performing these steps on Ubuntu 22.04 host:

Download the cloud image

qemu-img create -b ../jammy-server-cloudimg-amd64.img -f qcow2 -F qcow2 myubuntu2204test01-base.img 10G

Create the file meta-data in the directory myubuntu2204test01:

instance-id: myubuntu2204test01
local-hostname: myubuntu2204test01.example.com
network:
  version: 2
  ethernets:
    enp1s0: 
    dhcp4: no
    addresses: [192.168.122.146/24]
    nameservers:
         addresses: [192.168.122.1]
    routes:
    - to: 0.0.0.0/0
      via: 192.168.122.1

Create the file user-data in the directory myubuntu2204test01:

#cloud-config
users:
  - name: someuser
    ssh_authorized_keys:
      - ssh-ed25519 somekey comment
    sudo: ["ALL=(ALL) NOPASSWD:ALL"]
    groups: sudo
    shell: /bin/bash

Generate the ISO image for ci data

genisoimage -output cidata.iso -V cidata -r -J user-data meta-data

Create The VM myubuntu2204test01

virt-install \
--name=testvmubuntu2204 \
--ram=512 --vcpus=1 \
--import \
--disk path=myubuntu2204test01-base.img,format=qcow2 \
--disk path=cidata.iso,device=cdrom \
--os-variant=ubuntu22.04 \
--network bridge=virbr0,model=virtio \
--graphics vnc,listen=0.0.0.0 --noautoconsole

The VM is created. But the VM does not have static IP networking as defined in meta-data. The VM has a default DHCP network configuration.

What is missing or incorrect in this process to create static IP for the guest VM?

I have tried defining the networking in both user-data and meta-data files, both of them fails to create static networking for the guest VM.

I have a CloudFront distribution. The origin is an S3 bucket that uses OAI.

I have created a lambda@edge function following directions from https://aws.amazon.com/blogs/compute/implementing-default-directory-indexes-in-amazon-s3-backed-amazon-cloudfront-origins-using-lambdaedge/

Basically, I want the lambda@edge function to redirect URLs ending in / to /index.html. Acting like Apache DirectroyIndex.

The CloudFront distribution works for URLs without the redirect requirement. But CloudFront does not seem to invoke my lamba@edge function.

I have ensured, there is a correct association between the CloudFront distribution and the labda@edge function version.

I made several test requests:

curl -I https://www.sudheer.net/blog/
HTTP/2 403 
content-type: application/xml
date: Sat, 19 Feb 2022 14:35:38 GMT
server: AmazonS3
x-cache: Error from cloudfront
via: 1.1 5d840d432727e3561fd1a3de915212ca.cloudfront.net (CloudFront)
x-amz-cf-pop: EWR53-C2
x-amz-cf-id: leub-Kgu4Bh9xH4Rn5o7bxs62B1NBO4ViEu6hv-_xtGG7DSQlBFEXw=

I get 403. I did not find any lambda@edge logs in any region.

What could be the issue? How do I go about finding it?

The Lambda@Edge function has the principals:

    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "",
            "Effect": "Allow",
            "Principal": {
                "Service": [
                    "edgelambda.amazonaws.com",
                    "lambda.amazonaws.com"
                ]
            },
            "Action": "sts:AssumeRole"
        }
    ]
}