awslabs / aws-cyclone-solution Goto Github PK

If selecting to have ACS (AWS-Cyclone-Solution) build VPCs for you then options should be there to create both private and public VPCs. Endpoint options already supported will enable private VPCs

Allows the submission of array jobs. Please comment if you have input on what the submission format/method should be. For example a text or csv file with all jobs or linux arrays in command line?

Users can pass resource parameters in to config tables. Idea here would be to include a schema validation function in that lambda to catch any issues before they happen and return an error to user.

This will create launch templates across all enabled regions that can be used by Batch clusters and as EC2 task definitions for EC2 clusters.

When task definition job name is longer than 60 characters the IAM role cannot be created and this causes the stack deployment to fail. Needs further investigation.

This might also be causing a situation where resources cannot be deleted unless config is removed from dynamodb manually. Needs to be investigated

Ability to deploy an API front-end in private VPC. This would need to be an option within front-end-stack. A config option would be placed in setttings.json. Could also be specified in hyper cli when creating a new host. Initially this would only be when deploying host via CDK either from CLI or manually using cdk deploy. It would later be added to CLoudformation based deployment of front-end based on create-host command.

Currently CLI only returns the "message:internal server error". More detailed error responses should be returned when something is not working.

linux_parameters never get set correctly.

If you have more than the limit of the default dynamodb scan operation, it will not process all the items.

Ability to create Parallel clusters and submit jobs. Pcluster copies would be spread across regions / AZs and be abstracted to look like one cluster. Pcluster task definitions will be the parameters offered by Slurm as part of a job submit.

Currently in development, this will allow you to create EC2 clusters and submit jobs with ec2 launch templates as task definitions.

Currently *_api_key stored in SSM Parameter Store as a string. It would be best to store this as a SecureString.

Option to deploy a NAT Instance in main region VPC for Egress. This should be accompanied by automatic routing from any hub region VPC that is peered to main region for 0.0.0.0/0 --> main region NAT instance.

Ability to terminate jobs, probably built into the qdel command which currently will not stop jobs running.