Shared Secret

Table Of Contents

Goal

Create an end-to-end fully encrypted, publicly accessible secret storage tool

Components

  • AWS Code Commit (Ruby v2.7) - a fork of OneTimeSecret with additional features, more developed UX & mobile capabilities.
  • AWS Elastic Beanstalk (which includes EC2 instances deployed with boot-strap configurations defined in the beanstalk configuration)
  • AWS S3 (Terraform Remote State, misc. components)
  • AWS Elasticache (v3.2.10)
  • AWS ELB (Application Load Balancer)
  • AWS ACM (Amazon Certificate Manager)
  • AWS Route 53 (DNS Management)

Deployment Model The goal of the deployment is to deploy all initial platform components through Terraform. Due to the complexity/work-exerted model for Elastic Beanstalk, those components may be deployed manually.

Deployment Overview shared secret

Feedback Looking for general feedback - not looking to monetize.

Tags :
Share :

Related Posts

Diagramming using CloudMapper

The snowball effect for organizations & startups using AWS is a real thing. You may start experimenting with using one of the cloud platforms (AWS in this article) and soon to find out you have quite the labyrinth of policies, groups, users, access keys and more. This handy tool developed by the security company DUO (now owned by Cisco) will help you untangle the ball of yarn that started with a back & forth between you and the developers.

Read More

Backup AWS Route 53 using AWS Lambda

This has been updated to use AWS CDK and is much more refined. Check out: https://www.troydieter.com/post/r53_backups_2.0/ Need a way to automatically back up your AWS Route53 public DNS zones? Look no further, as a combination of the following AWS products can fit the need: Lambda Route53 CloudWatch S3 This will execute a Lambda function every 6 hours (or whichever you set the CloudWatch event to). It will use the IAM role to export your Route53 public zones as a CSV & JSON to the S3 bucket of your choice.

Read More