The following questions are part of the Questionnaire for Deploying advanced event mesh in a Customer-Controlled Region. If you are planning to deploy advanced event mesh using an Amazon EKS cluster, you must first complete the Common Questions, and then answer the following questions related to your deployment:
Amazon EKS Cluster
You must answer the following questions about your AWS EKS cluster.
| Question | Possible Answers | How SAP Uses This Information | Links to Related Documentation |
|---|---|---|---|
|
Do you have subnets for the worker nodes in all zones in your region? |
Yes |
High availability event broker services require three availability zones. |
|
|
Have you deployed the AWS Cluster Autoscaler? If not, do you have sufficient worker nodes to support the event broker services? |
Using Autoscaler Cluster has sufficient worker nodes |
SAP recommends that you use the AWS Cluster Autoscaler in your cluster. The alternative is to provision sufficient worker nodes. |
|
|
Are your cluster’s VPC and Subnets properly sized to support the number of event broker services you’d like to create? |
Yes |
The number of event broker services that can be created in a cluster is limited by the available IP addresses in the VPC and its subnets. By default, EKS uses the Amazon VPC CNI to assign IP addresses from the cluster’s VPC to its pods. This means it is critical to properly size the VPC CIDR block to support the number of event broker services you intend to create. Additionally, if you are using GP3 for your storage class, you must also deploy the Amazon EBS CSI driver, which consumes IP addresses in the VPC. Consider the size of your cluster’s network carefully, as it is not possible to change its size after creation. |
Amazon EKS Messaging Connectivity
You must answer the following questions about your AWS EKS Messaging Connectivity.
| Question | Possible Answers | How SAP Uses This Information | Links to Related Documentation |
|---|---|---|---|
|
If you are intending to use a LoadBalancer service to connect to your event broker service, have you deployed the AWS Load Balancer Controller into your cluster? |
Yes |
SAP recommends that customers use the AWS Load Balancer Controller because the in-tree alternative is deprecated. |
|
|
If you intend to use LoadBalancer services to connect to your event broker services, have you tagged the Subnets that will contain the ENIs for the NLBs so the AWS Load Balancer Controller can find them? |
Yes No |
The AWS Load Balancer documentation defines this as the best practice for AWS Load Balancers. SAP's best practice Terraform project for EKS applies the tags to the public and private subnets. If the terraform script cannot apply the tags, you must provide the tags to SAP so we can apply them with a service annotation. |
Subnet Auto Discovery in AWS Load Balancer Controller documentation |
|
Are there any additional annotations required in your environment (beyond the standard ones) that must be used on the LoadBalancer service for proper operation? |
Yes No |
SAP requires the extra service annotations to configure the Mission Control Agent so it can create event broker services. |
Load Balancer in Installing in Amazon Elastic Kubernetes Service (EKS) |
Amazon EKS Storage
You must answer the following questions about your AWS EKS storage.
| Question | Possible Answers | How SAP Uses This Information | Links to Related Documentation |
|---|---|---|---|
|
Have you created a storage class based on our best practices? |
Yes |
Some storage class parameters need to be set to properly support the creation of event broker services as well as other features. |
|
|
Which underlying disk type does your storage class use? |
GP2 GP3 |
SAP supports the deployment of event broker services only to GP2 and GP3 disks. |
Storage Class in Installing in Amazon Elastic Kubernetes Service (EKS) |
|
What is the name of the storage class? |
SAP requires the name to properly configure the Mission Control Agent so it can create event broker services. |
Storage Class in Installing in Amazon Elastic Kubernetes Service (EKS) |