AWS Secrets Manager Reviews and details

Social recommendations and mentions

• Your Plaintext Email is a DevSecOps Blind Spot

  A Hardened Channel for Sensitive Communication: While dedicated secrets management tools (like HashiCorp Vault, AWS Secrets Manager, etc.) are essential for storing and managing application secrets, secure E2EE email provides a significantly safer channel for human-to-human communication that might involve discussing sensitive topics, sharing unavoidable one-off credentials (with immediate rotation plans), or... - Source: dev.to / 20 days ago

• Building Custom Kendra Connectors and Managing Data Sources with IaC

  Some data sources are protected by some form of credentials. Unless the data source is a public website or stored in another AWS resource such as Amazon S3, Kendra or your custom data source will need credentials to fetch data. In either case, AWS Secrets Manager can be used to securely manage your credentials. - Source: dev.to / about 1 month ago

• Deploy AWS Lambda Functions and Amazon DynamoDB with AWS CDK on LocalStack

  In this example, we need to set up two AWS Lambda, AWS Secrets Manager and Amazon DynamoDB resources. - Source: dev.to / about 1 month ago

• Enhancing Your CI/CD Security: Tips and Techniques to Mitigate Risks

  You have to handle secrets like API keys and passwords carefully. Instead of hardcoding them into your code, you should use secure secrets management tools like HashiCorp Vault or AWS Secrets Manager. Additionally, following API key authentication best practices ensures secure handling of sensitive credentials. This keeps sensitive information protected and reduces the risk of accidental leaks. - Source: dev.to / about 1 month ago

• Starters Guide: End-to-End Guide to Building with LLMs on SageMaker

  Credential Management: Avoid storing sensitive data like access keys directly, utilizing AWS Secrets Manager, or using environment variables. - Source: dev.to / 3 months ago

• Secrets Management in Kubernetes: Best Practices for Security

  Integration with External Systems Kubernetes External Secrets can integrate with tools like HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and Google Cloud Secret Manager. For instance, to use HashiCorp Vault:. - Source: dev.to / 4 months ago

• The New Dev's Guide to Externalizing App Config

  Cloud platforms provide tools like AWS Secrets Manager, Azure Key Vault, and Google Cloud Secret Manager for exactly this purpose. These services, which evolved from patterns Mitchell Hashimoto pioneered with Vault in 2015, store and encrypt your configuration. - Source: dev.to / 5 months ago

• Production-Ready Terraform Module for Seamless Disaster Recovery: Primary and Secondary Clusters with Zero Downtime

  Secure Secrets: Consider using Terraform’s Sensitive Variables or integrating with secret management tools like AWS Secrets Manager or HashiCorp Vault. - Source: dev.to / 5 months ago

• Pydantic Settings + AWS the easy way

  We have a basic settings class that needs to load data from Environmet variables, parameter store and secrets manager. - Source: dev.to / 9 months ago

• Building a WhatsApp generative AI assistant with Amazon Bedrock and Python

  Edit WhatsApp configuration values in Facebook Developer in AWS Secrets Manager console. - Source: dev.to / about 1 year ago

• Keeping secrets out of public repositories

  If you’re asking yourself where you should be keeping secrets, you should be using a secrets manager. Two examples include Doppler (https://doppler.com). - Source: Hacker News / about 1 year ago

• Command Line Interface Guidelines

  A secrets management service would be most convenient. Documentation makes them easy to set up without having to build anything extra yourself. A secrets manager like Doppler (https://Doppler.com) has the advantage of protecting your secrets in a secure place and the advantage of minimizing exposure of those secrets - even to your own developers. That way, you don't end up with a data breach that could have easily... - Source: Hacker News / about 1 year ago

• A mistakenly published password exposed Mercedes-Benz source code

  It seems like they made a lot of assumptions that something like this wouldn't happen. They assumed employees would never leak secret information, and that their GitHub repos would never be exposed. They could've used https://doppler.com) and never had this problem. It's a little too easy to get comfortable thinking things work well the way they are. This should be a warning to other companies to seriously... - Source: Hacker News / about 1 year ago

• Kubernetes Secret Management

  AWS Secrets Manager is a fully managed service that simplifies the storage and retrieval of secrets within the AWS ecosystem. It integrates seamlessly with Kubernetes deployments, providing a scalable and secure solution for secret management. - Source: dev.to / over 1 year ago

• Refactoring a serverless application to use Step Functions third-party API call integration

  So we create a connection first and specify authorization pattern, which is API key in this case. EventBridge Connections uses Secrets Manager to store the key. - Source: dev.to / over 1 year ago

• A beginner's guide to AWS Best Practices

  AWS gives two sensible options - Systems Manager Parameter Store or AWS Secrets Manager. There are pros and cons to both options, but understand that Parameter Store is just as secure as Secrets Manager, provided you use the SecureString\ parameter type. More info here. - Source: dev.to / over 1 year ago

• Deploy Secure Spring Boot Microservices on Amazon EKS Using Terraform and Kubernetes

  If you have noticed, you are setting secrets in plain text on the application-configmap.yml file, which is not ideal and is not a best practice for security. The best way to do this securely would be to use AWS Secrets Manager, an external service like HashiCorp Vault, or Sealed Secrets. To learn more about these methods see the blog post Shhhh... Kubernetes Secrets Are Not Really Secret!. - Source: dev.to / over 1 year ago

• Secure GitHub Actions by pull_request_target

  In this post, I described how to build secure GitHub Actions workflows by pull_request_target event instead of pull_request event. Using pull_request_target, you can prevent malicious codes from being executed in CI. And by managing secrets in secrets management services such as AWS Secrets Manager and Google Secret Manager and access them via OIDC, you can restrict the access to secrets securely. To migrate... - Source: dev.to / over 1 year ago

• The Complete Microservices Guide

  Secret Management: Securely stores sensitive configuration data and secrets using tools like AWS Secrets Manager or HashiCorp Vault. Avoid hardcoding secrets in code or configuration files. - Source: dev.to / over 1 year ago

• How to Write Impeccably Clean Code That Will Save Your Sanity

  Do not add secrets into your repository. Instead use an environment file or a Secrets Management Service like AWS Secrets Manager. - Source: dev.to / almost 2 years ago

• Programmatically retrieving secrets from Parameter Store and Secrets Manager

  So we are better off adding the secrets to a central place like Parameter Store or Secrets Manager. - Source: dev.to / almost 2 years ago