A e2-standard-2 VM instance is currently unavailable in the asia-south1-a zone. Alternatively, you can try your request again with a different VM hardware configuration or at a later time

what should be recommended immediate action?

Hi @Jayalakshmi_K_M , does the workload have to be in asia-south1-a? Can you try launching the instance in asia-south1-b or asia-south1-c?

Alternatively, try a bit later or pick a different VM size, this should get you past the issue.

If you have any logs or screenshots of the issue put them here and can assist.

Thanks