Michael Wittig

Just to make sure that I understand this: The API actions only work in the org's root account ?

works on aws-cli/1.11.133 Python/2.7.5 Linux/3.10.0-693.el7.x86_64 botocore/1.6.0

@artburkart but I believe we first have to figure out the minimum version?

@laurikimmel in our test, we install `apt-get install git awscli` and it works. Have you used the install.sh script for installation of aws-ec2-ssh?

Hi @benwaine your alerting stack seems to be named `sn-alerting-Alerting-1VKQQLE2KMQ26` not `sn-alerting`. You can create a normal (not nested) CloudFormation stack based on cfn-modules/alerting, name it `sn-alerting` and your idea...

The centralized place might already exist (but not easy to find): https://github.com/cfn-modules/docs/blob/master/CONTRIBUTING.md#interfaces * `alb-listener` implements the `ExposeArn` interface * `ecs-nlb-listener-and-target` implements the `Target` interface * `ecs-alb-target` implements the `Target` interface...

Just one question before we start: What is the current behaviour? I expect import_users to fail if the group is deleted?

I usually prefer "fail fast" over skipping errors. My opinion: If there is a group that does not exists this is a configuration issue that should be fixed.

One scenario that I can imagine where this change breaks stuff is when users are created with other tools than `aws-ec2-ssh`. And I know some people doing this to get...

@kisst in which AWS region are you running?