Nikhil Reddy

@borrell @k4n30 We are reviewing this scenario and have updated the [documentation](https://docs.aws.amazon.com/solutions/latest/aws-security-hub-automated-response-and-remediation/deployment-stackset.html) to withdraw the steps provided for deploying the solution using service managed stacksets, we will resolve this issue...

@eduardopuente Thanks for providing this information, we will patch this error in a future release.

@eduardopuente Issue has been resolved in the latest version of the solution v1.4.0.

@fionah821 I tried to replicate the issue, used the following steps, the solution worked as per the configuration I had provided. * Created a stack in ap-southeast-2 with default timezone...

Hi @dbrenecki Can you confirm if the solutions is being used to schedule RDS Aurora Clusters?, If yes can you confirm if the RDS instances within a cluster are not...

Hi @dbrenecki If no RDS Instance in the clusters have been tagged and this error is being logged, it could be a different issue and not the same as #240....

Hi @dbrenecki Have you tried enabling the detailed logging for the solution, i.e. "Enable CloudWatch Logs" is set to "Yes" for the stack? This will provide more detailed logging, and...

Hi @sergii-maliarov-nordcloud Thank you for the feedback, we will update the documentation, the feature request will be added to a backlog, and will be evaluated/prioritized by the team.

@AleiScho Thanks for the feedback we will look into this.

Hi @fergoid2511 * The version 2.0.0 has been rolled back #289 * The solution is designed to support only on-demand instances. * The solution (v1.4.0) uses a parameter __START_EC2_BATCH_SIZE__ in...