Updating publish instruction for eusc aws account

Author: sumoanema

CONTRIBUTING.md

@@ -50,6 +50,7 @@ First of all, thanks for contributing!. Before contributing please read the [COD
   because AWS caches the layer code internally.
   - However, once you update or redeploy them, `v10` will no longer be available.
 
+#### Releasing layer for Commercial AWS
 1. Change the *AWS_PROFILE* environment variable using below command. The profile should point to sumocontent aws account.
   `export AWS_PROFILE=<sumo content profile>`
 1. Update the layer version in *config/version.go*.
@@ -62,6 +63,21 @@ First of all, thanks for contributing!. Before contributing please read the [COD
 1. Run the following command to verify that the layer version is published across regions:
    `sh verify_layer_versions.sh`
 
+#### Releasing layer for EUSC(Euorpean Sovereign cloud) AWS
+We have a seperate EUSC production aws account where we need to publish. 
+1. You need to get the EUSC accessid and accesskey via dev cli.
+  `dev hcvault login`
+  `dev hcvault cli_env -a esc-production`
+1. Change the *AWS_PROFILE_EUSC* environment variable using below command. The profile should point to eusc production aws account.
+  `export AWS_PROFILE_EUSC=<eusc production profile>`
+1. Update the layer version in *config/version.go*.
+1. Go to scripts folder
+  `cd scripts/`
+1. Change the layer_name variable in zip.sh to avoid replacing the prod.
+1. Run the following command to publish the layer:
+   `sh zip_special_partitions.sh`
+1. The zip file generated by previous step should have `extensions` folder in it, which should consist of the binary for the extension.
+
 ### Github Release
 
   - The new extension binary and zip files gets released automatically after the tags are pushed using Github actions(Refer tagged-release in https://github.com/marvinpinto/action-automatic-releases).