Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External secrets #2456

Open
sisygoboom opened this issue Jan 29, 2025 · 2 comments
Open

External secrets #2456

sisygoboom opened this issue Jan 29, 2025 · 2 comments
Labels
feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed

Comments

@sisygoboom
Copy link

Environment information

System:
  OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
  CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1270P
  Memory: 12.05 GB / 15.34 GB
  Shell: /usr/bin/zsh
Binaries:
  Node: 20.11.1 - ~/.n/bin/node
  Yarn: 1.22.22 - ~/.yarn/bin/yarn
  npm: 9.7.1 - ~/.npm-global/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.5.1
  @aws-amplify/backend: 1.12.0
  @aws-amplify/backend-auth: 1.4.2
  @aws-amplify/backend-cli: 1.4.6
  @aws-amplify/backend-data: 1.4.0
  @aws-amplify/backend-deployer: 1.1.13
  @aws-amplify/backend-function: 1.11.0
  @aws-amplify/backend-output-schemas: 1.4.0
  @aws-amplify/backend-output-storage: 1.1.4
  @aws-amplify/backend-secret: 1.1.5
  @aws-amplify/backend-storage: 1.2.4
  @aws-amplify/cli-core: 1.2.1
  @aws-amplify/client-config: 1.5.5
  @aws-amplify/deployed-backend-client: 1.5.0
  @aws-amplify/form-generator: 1.0.3
  @aws-amplify/model-generator: 1.0.12
  @aws-amplify/platform-core: 1.5.0
  @aws-amplify/plugin-types: 1.7.0
  @aws-amplify/sandbox: 1.2.9
  @aws-amplify/schema-generator: 1.2.6
  aws-amplify: 6.12.0
  aws-cdk: 2.174.1
  aws-cdk-lib: 2.174.1
  typescript: 5.7.2
No AWS environment variables
No CDK environment variables

Describe the feature

We need to be able to fetch secrets that are not managed by amplify. We would like the secret() function to be able to receive arns and/or logical ids from the wider AWS account or have an externalSecret() function.

This is because of some corporate rules, amplify is flexible enough to meet all other needs but this would require a significant amount of tinkering on our behalf so would be good to avoid.

Use case

Meeting corporate rules, using backend as a standalone cdk framework without the need for amplify managed service.

@sisygoboom sisygoboom added the pending-triage Incoming issues that need categorization label Jan 29, 2025
@ykethan
Copy link
Member

ykethan commented Jan 29, 2025

Hey @sisygoboom, thank you for reaching out. Marking this as feature request to support fetching existing secrets in the account.

@ykethan ykethan added feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed and removed pending-triage Incoming issues that need categorization labels Jan 29, 2025
@ykethan
Copy link
Member

ykethan commented Jan 29, 2025

@sisygoboom could you also provide us any additional details on the constraints and use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed
Projects
None yet
Development

No branches or pull requests

2 participants