Multi Cloud Engineer

In 3+ decades of global work experience/learning, blessed with few inspiring mentors to achieve with super six execution steps:

1. Passion
2. Plan
3. Prepare
4. Practice
5. Physical exam
6. Permit

If not, wouldn't be Doctorate.  Many thanks to uplifting disciplines from them.

As 'Embrace the journey consistently, where result comes effortlessly', 6Ps derived me to become Multi Cloud Engineer (MCE) with 3:4:3 ambitions.

Illustration: In any case, multi cloud expertise in 3 years with divisible of 4 quarters (year) and 3 months (quarter) with the capital of self-drive/motivation!

'Grab every opportunity that comes on your way' - work initiatives got into AWS and Azure hands-on product engineering, followed by self-practices of Google cloud.

Thanks for being part of this passionate consistent journey to move forward in 2025 AI era!

Happy New Year 2025 to everyone in the world.

ChatGPT is down

Recent days, ChatGPT becomes part and parcel of our routine work.  Unfortunately, it is down for last couple of hours.

We now have to wait a while until the OpenAI team has solved the problem.

Eagerly looking into their status page https://status.openai.com/

Null Coalescing Operator

C# Null Coalescing Operator (??) is a powerful feature that allows developers to handle null values gracefully by providing a default value.

result = value1 ?? value2;

If value1 is not null, result is value1

If value1 is null, result is value2

Multiple ?? chain operators are used to provide multiple fallback values.

string? first = null;
string? second = null;
string third = "Final Value";

string result = first ?? second ?? third;
Console.WriteLine(result); // Output: "Final Value"

Starting with C# 8.0, the null-coalescing assignment operator (??=) can be used to assign a value to a variable if it is currently null

string? name = null;
name ??= "Default Name";
Console.WriteLine(name); // Output: "Default Name"

Advantages:

1. Cleaner Code: Reduces the need for explicit if checks for null.
2. Safe Fallbacks: Ensures default values in case of null.
3. Improves Readability: Code is more concise and expressive.

AWS reInvent 2024

Last week, we had AWS re:Invent 2024 flagship annual conference 

This premier cloud computing event brings together the global cloud computing community for a week of keynotes, technical sessions, product launches, and networking opportunities. 

As AWS continues to unveil its latest innovations and services throughout the conference, session recordings are available in public at https://reinvent.awsevents.com/on-demand/?trk=direct

Container Orchestration

Container orchestration refers to the automated management, coordination, and scheduling of containerized applications. It is essential for deploying, scaling, and managing containers in large, dynamic environments.

 Key container orchestration platforms include Kubernetes, Docker Swarm, and Apache Mesos. Here are some of the primary benefits:

1. Automated Deployment and Scaling: Orchestration platforms can automatically deploy containers across a cluster of machines and scale them up or down based on demand.
2. Service Discovery and Load Balancing: These platforms provide mechanisms to discover services and distribute traffic across containers to ensure high availability and reliability.
3. Self-Healing: Orchestration tools can automatically restart failed containers, replace and reschedule them to maintain the desired state of the application.
4. Efficient Resource Utilization: They ensure optimal use of infrastructure resources by managing container placement based on available resources and policies.
5. Monitoring and Logging: Orchestration platforms offer integrated monitoring and logging capabilities to track the health and performance of containers and applications.
6. Configuration Management: They provide mechanisms to manage and update configuration settings for containers in a centralized and controlled manner.
7. Security and Compliance: Orchestration tools often include features to manage security policies, enforce compliance, and handle secrets and sensitive data securely.

Shared Responsibility

The concept of shared responsibility in cloud computing refers to the division of security and compliance responsibilities between the cloud service provider (CSP) and the customer. The exact division of responsibilities can vary depending on the type of cloud service model (IaaS, PaaS, SaaS) being used.

The given diagram indicates the level of responsibility from IaaS to SaaS (from left to right)

In a nutshell, the shared responsibility model delineates which security tasks are handled by the cloud provider and which are handled by the customer, ensuring a clear understanding of each party's role in maintaining the overall security of the cloud environment.

Cloud IAM

Identity and Access Management (IAM) defines who can do what on which resources

Although IAM for Google and AWS perform the same function, they do it in very different ways.

Google uses Service accounts to control service-to-service authentication; AWS uses IAM Roles and Profiles to accomplish this control.

Details are listed in the below table

Concept	Google Cloud	Amazon Cloud
Programmic Identity	IAM service account	IAM role and instance profile
User Identity	Federated and managed outside IAM	Identify profiles within AWS and EC2
Policy	List of binding for set of users by role	Documents based permission apply to cloud users
Permission Collection	User vs Role pairing	Managed policies
Predefined set of permission	Predefined roles	Managed policies