Sebastian Müller
Sebastian Müller
Basically those two approaches are very different regarding (un-)restricted access: - https://github.com/medikoo/serverless-plugin-dynamodb-autoscaling/blob/master/lib/scaling-role-resource.json#L39 - https://github.com/sbstjn/serverless-dynamodb-autoscaling/blob/master/src/aws/role.ts#L62-L66
Good question, I thought about using kinesis analysis as well. But I do not know if you plan works, sorry ;)
Any chances to get this merged @steven-mercatante ? :)
As an alternative, we can store this information as a parameter in SSM. Maybe that's even better. 🤔
Can you please clarify what's the needed work here? There seem to be multiple ways how to achieve "this".
We use the `AdministratorAccess` managed policy and stopped building a least privilege policy at this point: ``` - servicecatalog:DescribeProduct - servicecatalog:ProvisionProduct - controltower:CreateManagedAccount - controltower:DescribeManagedAccount - sso:ListDirectoryAssociations - sso:DescribeRegisteredRegions -...
The "Activate IAM Access" feature should be a default when using superwerker. Currently. the budget report can only be accessed using the root user account. I started a discussion: https://github.com/superwerker/superwerker/discussions/216
Without #180 this is not as useful as intended, that's true. I'll just mark it as `blocked` until we came up with a solution for #180
I triggered the pipeline to test this.
[AWS Backups now supports S3](https://aws.amazon.com/about-aws/whats-new/2022/02/general-availability-aws-backup-amazon-s3/)