Unleashing Cloud Potential: AWS Cloud Consumption Strategy

Umair Dinarwala Muhammad Waqas Mike Williams Ido Vapner #kyndryl #cloudarchitecture #

Many customers are embarking on their business transformation by embracing the cloud. The engagement process varies at different stages, encompassing design, build, migration, and management of the cloud environment. In this discussion, I will delve into the various cloud consumption methods available with AWS.

Within AWS, there are three agreement options available for customers to subscribe to cloud services:

1.?????Solutions Provider Account Model (SPAM)

2.?????End Customer Account Model (ECAM)

3.?????Customer Account – Self Managed

It's important to note that each model has its own benefits and considerations, and the choice depends on the specific requirements and preferences of the customer.

Let's deep dive into each consumption way and align the consumption strategy according to customer requirements:

SPAM:

In the Solutions Provider Account Model (SPAM), all the accounts created for the client will be consolidated under the Solutions Provider (SI Partner) master account. This means that the Solutions Provider will have governance and control over policies and security guardrails for these accounts.

As a reseller for AWS services, the SI Partner will handle the billing and charge the customer for the AWS service consumption. The advantage of going through the SI Partner is that they may be able to offer additional discounts or pricing advantages compared to direct consumption.

By centralizing the management and billing under the SI Partner, customers can benefit from a simplified experience, as they only need to interact with the SI Partner for service provisioning, support, and billing inquiries.

It's worth noting that the specific discounts and pricing structures may vary based on the agreements and negotiations between the SI Partner and AWS. Customers should discuss and negotiate these terms with their SI Partner to ensure they are getting the best value for their AWS service consumption.

ECAM:

End Customer Account Model (ECAM), the customer maintains ownership of their AWS account, including the AWS root account. This grants them complete control over governance, security, and the overall management of their AWS environment.

However, in terms of billing, there is a partnership with the SI partner. To facilitate this billing arrangement, collaboration with your SI Partner and AWS Alliance is necessary. They will invite the customer account to be linked with their SI master account solely for billing purposes.

In the ECAM, the customer retains full autonomy over their AWS resources, including governance and security configurations. The SI partner's role primarily revolves around handling the invoicing and charging back of AWS consumption to the customer.

To enable this method, effective coordination with your SI Partner and AWS Alliance is crucial. They will work together to establish the necessary billing processes to ensure accurate and timely billing for the customer's AWS usage.

By establishing clear communication and alignment between the customer, SI partner, and AWS Alliance, responsibilities and expectations related to governance, security, and billing can be effectively defined. This collaborative approach ensures a seamless implementation of the ECAM, with the customer maintaining ownership while benefiting from the billing support provided by the SI partner.

Customer Account Model:

In this consumption model, the customer maintains full ownership of the AWS account across all aspects, including governance, security, and billing.

As the account owner, the customer has complete control over governance policies, access controls, and configurations to ensure compliance and security best practices are implemented according to their specific requirements. Additionally, the customer retains direct control over the billing process. They are responsible for managing and paying for the AWS services consumed within their account. This allows them to have a clear understanding of their usage, costs, and overall financial management.

With ownership of the account, the customer has the flexibility to configure and optimize their AWS resources, choose appropriate service offerings, and leverage various AWS tools and features to meet their specific needs and objectives. Overall, in this consumption model, the customer has the authority to govern their AWS account, implement security measures, and take full responsibility for billing, allowing them to tailor their cloud environment according to their unique requirements.

Conclusion

In conclusion, the choice of consumption strategy depends on the specific needs and preferences of the customer. It is essential to present all available options and align the consumption strategy accordingly during the engagement process.

By providing comprehensive information and discussing the pros and cons of each model, customers can make informed decisions that best suit their requirements. This approach ensures that the chosen consumption strategy aligns with their goals, maximizes benefits, and meets their specific business needs.

Effective communication and collaboration with the customer throughout the engagement process will help determine the most suitable consumption model and ensure a successful cloud journey for their business transformation.

Author:

Arun Kumar is a seasoned cloud practice architect working with Kyndryl Canada. With a strong background in architecting system designs for various clients, Arun brings extensive expertise in cloud solutions. He holds architect certifications in AWS (Amazon Web Services), GCP (Google Cloud Platform), and OCI (Oracle Cloud Infrastructure). Arun's diverse skill set and industry knowledge enable him to design robust and scalable cloud architectures that meet the unique requirements of his clients.