stelligent / cloudformation_templates Goto Github PK

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

I stumbled upon this piece of code https://github.com/stelligent/cloudformation_templates/blob/master/labs/codebuild/codebuild.yml#L194 while searching for reference how to create a proper CodeBuild service role. Giving a role arn:aws:iam::aws:policy/AdministratorAccess is a terrible security practice, even for example code. A malicious pull request could alter the buildspec.yml and access the whole AWS account.

Launching autoscaling/bakedami-elb-rdsbackend.yml by clicking "launch" expects the template to be in S3, but CF complains with this message;
Template validation error: S3 error: The specified key does not exist.

https://github.com/stelligent/cloudformation_templates/blob/master/labs/opsworks/codepipeline-opsworks.json

codepipeline-REGION-ACCTID

https://twitter.com/PaulDuvall/status/790571522859479040

Request

• Bug
• [ *] New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

Include tags options ( in service catalog) in the portfolio for the product to auto include when spinning up the product

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• Running infrastructure gives RemoteAccessNetwork

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• https://github.com/stelligent/cloudformation_templates/blob/master/storage/mysql-rds.yml redirects to GitHub's 404 page.
• Readme file for the repo is where that link lives

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• Would be great to figure out some magic to add template validation testing in CircleCI
• Maybe a Rakefile task?

Request

• Bug

Details

I've run into a problem when it comes to CodePipeline notifications, and it seems that your code (codepipeline-notifications.yml) is experiencing the same problem. If you can, please verify that your template isn't working as expected.

Steps to reproduce:

1. Run aws cloudformation create-stack --stack-name Notifications --template-body file://codepipeline-notifications.yml --parameter ParameterKey=EmailAddress,ParameterValue=<your email> and wait for stack to be created
2. Accept the subscription confirmation by clicking the link in the received e-mail
3. Trigger a CodePipeline that is configured to fail and wait for it to complete
4. Verify that you haven't received an e-mail, but at this point you ought to have
5. Navigate to CloudWatch and edit your rule. Don't change anything, just click through the wizard and update the rule in the console.
6. Trigger the pipeline again. This time you will receive an e-mail.

As I said, I don't think anything is wrong in your template. I'm experiencing the same issue with one of my templates. But it would be beneficial if your sample indicated that the template didn't behave as expected, given you are able to reproduce the issue.

Best regards,
Mattias

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• Rename all .template file extensions to .json
• Upload renamed files to S3
• Update all links to point to the .yml templates in S3 besides launcher links still need to point to .json until yaml support added.
• Also, move templates to stelligent-public/cloudformation-templates/github/* instead of having the subfolders (pain in the ass, bad idea from me)

@LevonBecker You know we've got this? https://github.com/stelligent/stelligent_commons/tree/master/cloudformation

Thanks for sharing great templates! I could get a good amount of knowledge of AWS architecture through these.

Thanks!

-- J

Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• Could you explain why bastion template has an IAM Role? I think I don't need any role at all because it is just a host to jump to private servers.