In TAC (Cisco CX) org we have seen cases where customers are trying and struggling to build the cluster_layer.zip. This has been compounded by AWS lamdba functions glibc libraries deviating from a standard ubuntu release (18.04). It has caused issues like this.
I suggest that we use github actions to do the steps necessary to build the cluster_layer.zip and publish them in a github release. The end user then just needs to download the artifact, modify the Configuration.json file and then upload the artifacts to the S3 bucket per the instructions.
Included in the repo is a github action that will build a cluster_aws.zip file that includes cluster_layer.zip, cluster_manager.zip and cluster_lifecycle.zip. Also included is an updated readme in the cluster/aws folder that clarifies the necessary steps.
Ideally, the repo should provide all these artifacts for each of the deployment scenarios and environments rather than expecting the end user to build them.
In TAC (Cisco CX) org we have seen cases where customers are trying and struggling to build the
cluster_layer.zip. This has been compounded by AWS lamdba functionsglibclibraries deviating from a standard ubuntu release (18.04). It has caused issues like this.I suggest that we use github actions to do the steps necessary to build the
cluster_layer.zipand publish them in a github release. The end user then just needs to download the artifact, modify theConfiguration.jsonfile and then upload the artifacts to the S3 bucket per the instructions.Included in the repo is a github action that will build a
cluster_aws.zipfile that includescluster_layer.zip,cluster_manager.zipandcluster_lifecycle.zip. Also included is an updated readme in thecluster/awsfolder that clarifies the necessary steps.Ideally, the repo should provide all these artifacts for each of the deployment scenarios and environments rather than expecting the end user to build them.