Answers: <p>AWS secrets are still accessible via the CLI.</p>
  
  <p>The link you provided goes to an old version of the AWS CLI.  Check out the latest version and commands here: <a href="https://awscli.amazonaws.com/v2/documentation/api/latest/reference/secretsmanager/index.html" rel="nofollow noreferrer">https://awscli.amazonaws.com/v2/documentation/api/latest/reference/secretsmanager/index.html</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2020-06-07T15:36:48.427Z
Answers: thanks though
  the first part of the command is still aws secretsmanager and if i do 
  aws --help it dosn't display secretsmanager as an avalible option?
Answers: doug
Answers: CC BY-SA 4.0
Answers: 2020-06-07T22:16:37.880Z
Answers: thanks iv got it working now from a docker instance still don't know what was wrong with it but it was likely the aws cli as you surjested so thanks!
Answers: doug
Answers: CC BY-SA 4.0
Answers: 2020-06-05T14:21:21.870Z
Answers: 2020-06-05T14:21:21.870Z
Answers: Wesley Rolnick
Body: <p>If I enter: </p>
  
  <pre><code> aws secretsmanager get-secret-value --secret-id  my secret id
  </code></pre>
  
  <p>It says invalid choice.</p>
  
  <blockquote>
    <p>aws: error: argument command: Invalid choice, valid choices are:</p>
  </blockquote>
  
  <p>and doesn't list <code>secretsmanager</code> as one of the choices or any variation on <code>secretsmanager</code>?</p>
  
  <pre><code>aws secretsmanager get-secret-value --secret-id  my secret id
  </code></pre>
  
  <p>was used in a <a href="https://www.youtube.com/watch?v=Y3Gn_iP3FlE" rel="nofollow noreferrer">video from 2018</a> </p>
  
  <p>Similarly, <a href="https://docs.aws.amazon.com/cli/latest/reference/secretsmanager/list-secret-version-ids.html" rel="nofollow noreferrer">this command</a> doesn't work</p>
  
  <p>and AWS help and AWS man don't contain secrets manager?</p>
  
Comments: CC BY-SA 4.0
Comments: 2020-06-05T11:34:26.203Z
Comments: Could you please post which version of aws-cli you are using?
Comments: Karthick Prabu
Comments: CC BY-SA 4.0
Comments: 2020-06-07T16:29:35.107Z
Comments: i tried with a new account with the
Comments: doug
Comments: CC BY-SA 4.0
Comments: 2020-06-07T16:33:07.590Z
Comments: aws-cli/1.14.35 Python/2.7.5 Linux/3.10.0-957.21.2.el7.x86_64 botocore/1.8.39
Comments: doug
Tags: <aws-cli>
Title: Was AWS Secrets Manager removed from AWS CLI commands?
UserDisplayName: doug
ThreadText: # Was AWS Secrets Manager removed from AWS CLI commands?
  
  (Asked by: username_0 on 2020-06-05)
  
  If I enter:
  
  ```
   aws secretsmanager get-secret-value --secret-id  my secret id
  
  ```
  
  It says invalid choice.
  
  > aws: error: argument command: Invalid choice, valid choices are:
  
  and doesn't list `secretsmanager` as one of the choices or any variation on `secretsmanager`?
  
  ```
  aws secretsmanager get-secret-value --secret-id  my secret id
  
  ```
  
  was used in a [video from 2018](https://www.youtube.com/watch?v=Y3Gn_iP3FlE)
  
  Similarly, [this command](https://docs.aws.amazon.com/cli/latest/reference/secretsmanager/list-secret-version-ids.html) doesn't work
  
  and AWS help and AWS man don't contain secrets manager?
  
  **Tags:** aws-cli
  
  > **Comments:**
  > **username_1**: Could you please post which version of aws-cli you are using?  
  > **username_0**: i tried with a new account with the  
  > **username_0**: aws-cli/1.14.35 Python/2.7.5 Linux/3.10.0-957.21.2.el7.x86_64 botocore/1.8.39  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2020-06-05. Score: 4 | Accepted answer
  
  AWS secrets are still accessible via the CLI.
  
  The link you provided goes to an old version of the AWS CLI. Check out the latest version and commands here: <https://awscli.amazonaws.com/v2/documentation/api/latest/reference/secretsmanager/index.html>
  
  > **Comments:**
  > **username_0**: thanks though the first part of the command is still aws secretsmanager and if i do  aws --help it dosn't display secretsmanager as an avalible option?  
  > **username_0**: thanks iv got it working now from a docker instance still don't know what was wrong with it but it was likely the aws cli as you surjested so thanks!  
  
  ---
  
  