Andrew

Whats the feasibility to set a default role instead of remembering the last assumed?

Could you please share the AMI that was being used

Do you have the latest version of the repository pulled? From looking at the line where the error is occurring (23) its probably the version before the fix https://github.com/RhinoSecurityLabs/cloudgoat/commits/master/scenarios/ecs_takeover/terraform/ec2.tf

The following data sources are now unused - data.aws_vpc.default - data.aws_subnets.all_subnets I would also recommend adding a [required version](https://github.com/terraform-linters/tflint-ruleset-terraform/blob/v0.4.0/docs/rules/terraform_required_providers.md) for the **archive** & **time** providers

Have the scenario create the CloudWatch group that the lambda will write to. Then when the scenario is destroyed it is also cleaned up

941aa8206d81ae86f87bd7c030362c7259e0ec75 The change to the platform are still building as arm, the ECS tasks then fails. I think the only thing needed to be added is the platform tag to...

From quickly looking at [aws-vault](https://github.com/99designs/aws-vault) you would need to export your temporary credentials locally. Something like this also might work, just set the profile to default or whatever aws-vaults uses...

Ahh looks like aws-vault does not write to the `~/.aws/credentials` What might need to be done it get the temporary credentials and put them in that file so CloudGoat can...

The tool [pike](https://github.com/JamesWoolfenden/pike) might be able to map some of the permissions out for you. The issue still remains that for most scenarios we need to create IAM users/roles with...

Any updates with this? I have been trying to get this to work myself. I found that nextcloud will create the `oc_admin` user which is not allowed to connect over...