Fix AWS secret key environment variable name in docs

[sandratiffin]

Signed-off-by: Sandra Tiffin sandra.tiffin@progress.com

The AWS platform support instructions give the wrong environment variable name for the secret access key, this fixes it.

Description

If you follow the AWS Command Line Interface Docs link on this page, it leads you to https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html which gives the correct variable name -- AWS_SECRET_ACCESS_KEY instead of AWS_SECRET_KEY_ID.

The same info is also in the ruby AWS SDK docs at https://docs.aws.amazon.com/sdk-for-ruby/v3/developer-guide/setup-config.html#aws-ruby-sdk-credentials-environment.

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New content (non-breaking change)
• Breaking change (a content change which would break existing functionality or processes)

Checklist:

• I have read the CONTRIBUTING document.

[netlify]

✔️ Deploy Preview for chef-inspec ready!

🔨 Explore the source changes: 71222c0

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-inspec/deploys/60c9d58e631f9c0007689da2

😎 Browse the preview: https://deploy-preview-5566--chef-inspec.netlify.app/inspec/platforms

[chef-expeditor]

Hello sandratiffin! Thanks for the pull request!

Here is what will happen next:

1. Your PR will be reviewed by the maintainers.
2. Possible Outcomes
   a. If everything looks good, one of them will approve it, and your PR will be merged.
   b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner.
   c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!

[clintoncwolfe]

Good catch, thanks!