Issues when executing build-s3-dist.sh about genomics-secondary-analysis-using-aws-step-functions-and-aws-batch HOT 6 CLOSED

@ury -

These are a couple of variances due to differences in Linux distributions and MacOS.

The crhelper install doesn't throw a traceback when using Amazon Linux 2 for a Cloud9 instance. Even with the traceback under Ubuntu, the crhelper package still gets installed into the desired target path:

./source/setup/lambda

You can safely ignore the sed errors. They are due to the -i '' option provided, which is necessary with the version of sed on MacOS, but not with sed on LInux.

All assets get built into two folders:

1. ./deployment/global-s3-assets: contains the main solution installation template and required asset bundles.
2. ./deployment/regional-s3-assets: contains only the installation asset bundles and sample data used for the solution.

These match with the process that AWS Solutions uses to enable global deployment of solutions.

from genomics-secondary-analysis-using-aws-step-functions-and-aws-batch.

Thanks Lee,
I proceeded per your clarifications. There are a couple of instructions in README.md that I wasn't sure about:

aws s3 cp ./dist/ s3://my-bucket-name-<aws_region>/$SOLUTION_NAME/$VERSION/ --recursive --acl bucket-owner-full-control --profile aws-cred-profile-name

./dist - which folder is that? I assumed it refers to the deployment folder and used it when uploading to S3.

And then:

Deploy the solution to your account by launching a new AWS CloudFormation stack using the link of the solution template in Amazon S3.

you clarified that the template resides in the ./deployment/global-s3-assets folder, so I used the link for the template in that folder

When I create the stack, I get the following error:
Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 41067856-0c25-4845-99ed-4516f64a0b1d)

In the template, I understand that the following file is expected: [bucket_name]-[region_name]/[solution_name]/[version]/SetupLambdaBundle.zip, and in my case the file resides in [bucket_name]-[region_name]/[solution_name]/[version]/global-s3-assets/SetupLambdaBundle.zip.

To match the above, I uploaded only the global-s3-assets folder to S3 and launched the stack creation process again. This time it lasted longer, but failed during the Setup resource creation:

Failed to create resource. Code Build job 'GenomicsWorkflow-Setup:c82b0974-a7a4-4031-a4be-1b343e176964' in project 'GenomicsWorkflow-Setup' exited with a build status of 'FAILED'.

At this point, I think I should wait for your insights regarding the above, as I did at least one thing wrong.

from genomics-secondary-analysis-using-aws-step-functions-and-aws-batch.

@ury -

I'm curious about your use case here. Are you attempting to install the solution as is, or have you customized it and wanting to deploy the customized assets?

from genomics-secondary-analysis-using-aws-step-functions-and-aws-batch.

Hi Lee,
At this point, I'm attempting to install it as-is.

from genomics-secondary-analysis-using-aws-step-functions-and-aws-batch.

from genomics-secondary-analysis-using-aws-step-functions-and-aws-batch.

Closing this issue for now. Feel free to re-open if needed.

from genomics-secondary-analysis-using-aws-step-functions-and-aws-batch.