-
### Describe the bug
There are no options in CDK to set the deployment type from inplace to blue/green deployment. On the console, you can easily switch
### Expected Behavior
i expected some config…
-
### Description
When deploying StackSets using aws_cloudformation_stack_set_instance the API provides a means to [manage which accounts in the target OUs will receive the deploys](https://docs.aws.am…
-
This hook started failing recently for us, but I'm not sure what is to blame. The source URL in the CloudFormation console does not match this repository:
It links to an non-existent repo [here](…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the c…
-
https://docs.aws.amazon.com/inspector/latest/user/scanning-cis.html
- [x] Redo manual permission change on Monday
- [ ] Add IAM infrastructure code to attach CIS policy to GitLab role
- [ ] Add I…
-
### Name of the resource
Other
### Resource Name
AWS::IAM:*
### Issue Description
CloudFormation does not automatically create the following stack-level tags for IAM resources, as stated in this …
-
### Before opening, please confirm:
- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or clo…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help…
-
### Subject of the issue
When I try to add `package_args ` like this `sam package --signing-profiles HelloWorld=MySigningProfile...` it generateas a type error, please help me to found my issue. I d…
-
I plan to add AWS CloudFormation support to NixOps.
Reasons:
- CloudFormation is a well-tested tool for declaratively creating AWS resources
- Affords us full access to the [range of AWS resourc…
ghost updated
4 years ago