aws-amplify / aws-amplify/amplify-cli
Ideas for implementation of ignoring self-signed certs.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
**Is your feature request related to a problem? Please describe.**
We need the ability to ignore self-signed certs. This is mainly found when companies have a self-signed proxy.
**Describe the solution you'd like**
Have the option to ignore self-signed certs. What we will need to discuss is how to configure that option.
- Use a CLI flag. Something like `--ignore-self-signed` or `--no-verify-ssl`
- Add a config flag in the `$HOME/.aws/credentials` file
- Add it to each individual project
**Describe alternatives you've considered**
None
**Additional context**
I already have a bug report/request at #1452.
This fix will likely have to wait until PR #869 is finished.
My thought is to pass the config'd option to the AWS object config within the lib.
```
// We'd have to decide on the best way to configure it for each project/command/environment
const noVerifySsl = <>
if (httpProxy) {
const proxyAgent = require('proxy-agent');
aws.config.update({
httpOptions: {
rejectUnauthorized: noVerifySsl , // This is where we would set the correct option
agent: proxyAgent(httpProxy)
},
});
}
```
Contributor guide
Research direction
Start by reviewing issue #1452 and PR #869, then inspect the CLI and project configuration entry points and the AWS object setup in lib. Resolve where the option should be configured and how it should affect proxy connections; done requires an agreed configuration approach, implementation, and coverage for the supported CLI or project settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cli, cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100