add --no-verify-ssl flag for ufo commands
#89
Comments
aaronlippold
changed the title
--no-verify-ssl flag for ufo commands
|
Wondering if we should try this instead: Aws.use_bundled_cert! |
|
That might work as well. I'm happy to test it out.
…On Fri, Sep 27, 2019, 5:05 PM Tung Nguyen ***@***.***> wrote:
Wondering if we should try this instead:
Aws.use_bundled_cert!
amazon-archives/aws-sdk-core-ruby#166
<amazon-archives/aws-sdk-core-ruby#166>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#89>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALK42EYKBAPW7ZDKUUXI43QLZYSNANCNFSM4I3KYMYQ>
.
|
|
Cool. Unsure when will take a look at this. Will consider PRs. No sweat either way though. Thanks! |
|
I will start poking at where in the code now. |
- added docs to help explain and safe the user time and research Fixes boltops-tools#89 Signed-off-by: Aaron Lippold <lippold@gmail.com>
- added docs to help explain and safe the user time and research Fixes boltops-tools#89 Signed-off-by: Aaron Lippold <lippold@gmail.com>
|
It turns out the real solution is to work out which certs were missing from the ruby and openssl certificate chains and fold them into the PEM. The |
- added docs to help explain and safe the user time and research Fixes boltops-tools#89 Signed-off-by: Aaron Lippold <lippold@gmail.com>
- added docs to help explain and safe the user time and research Fixes boltops-tools#89 Signed-off-by: Aaron Lippold <lippold@gmail.com>
|
I still having trouble starting the service even on EC2
…On Sat, Sep 28, 2019, 3:00 PM Tung Nguyen ***@***.***> wrote:
Closed #89 <#89> via #91
<#91>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#89>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALK42A4X2IM2DRSOJNXH43QL6SVZANCNFSM4I3KYMYQ>
.
|
|
Like ECS service 🤔 If so, wondering what the EC2 console events tab say? Or is it the ufo init command? |
|
I'll send some screenshots or I'll send you a zoom. Out to dinner with my
daughter at the moment ;)
…On Sat, Sep 28, 2019, 7:21 PM Tung Nguyen ***@***.***> wrote:
Wondering what the EC2 console events tab say?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#89>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALK42EIPURM6WR2D6MSAS3QL7RF7ANCNFSM4I3KYMYQ>
.
|
|
f800e563-24dc-4b03-967c-72a2cc7dddae |
|
|
The repo is here : https://github.com/mitre/heimdall/tree/ufo-deploy/.ufo |
|
Does that give you what you were looking for? |
|
Not really. Think this issue is specific to the ECS cluster setup, not ufo itself. So will close out. Here are some ideas to help though. Have seen the "missing an attribute required by your task" error before. There can be many reasons, it really depends on the setup.
Hope that helps. |
|
Ok. I will look into that. Anything pop out at you in the way I have the |
|
These look like the default VPC settings https://github.com/mitre/heimdall/blob/ufo-deploy/.ufo/settings/network/default.yml That’s why am thinking that the ECS Container Instance that is register to the ECS cluster is probably running on a different VPC or Subnets. Unsure though because it can be a different reason. Would double check the EC2 instances themselves. |
|
Thanks for taking a look. I will look into that and see if I can get things
working.
Thanks again
…On Wed, Oct 2, 2019, 9:19 AM Tung Nguyen ***@***.***> wrote:
These look like the default VPC settings
https://github.com/mitre/heimdall/blob/ufo-deploy/.ufo/settings/network/default.yml
That’s why am thinking that the ECS Container Instance that is register to
the ECS cluster is probably running on a different VPC or Subnets. Unsure
though because it can be a different reason. Would double check the EC2
instances themselves.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#89>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALK42B5MNVHPASSQMIBYULQMSNW7ANCNFSM4I3KYMYQ>
.
|
Would it be possible to add a
--no-verify-sslflag to the cli so that use of ufo behind ssl proxies in corporate environments would be much more useful.This is the error that I am getting when I have the proxy turned.
The text was updated successfully, but these errors were encountered: