WinScp SFTP -no supported authentication methods available google cloud [closed] - google-cloud-platform

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
While connecting google cloud with WinScp SFTP Connwction gives the no supported authentication methods available google cloud error (Server Sent:public key) Any Solution ?

If you could make a clearer question, it would help you to obtain a good response. Nonetheless, let me provide mine.
Google Cloud Platform documentation has a section to connect to your VM instances through the WinScp client. The most probable cause of your issue is the absence or a wrong configuration of your public or private key.
If you already have a pair of keys try to look for them, this link can help you. But if not, your should create a pair of private-public keys, for example to create such keys in Linux this command is normally used:
ssh-keygen -t rsa -f ~/.ssh/[KEY_FILENAME] -C [USERNAME]
be aware of leaving blank the passphrase to ensure a straightforward connection and no other password will be required during the connection from WinScp. Here you can find the complete steps to do that.
Afterwards, you have to be able to configure your private key in you WinScp client in the Authentication section, just like it is explained here.
Hope it helps you!

Related

Cannot login to ssh through web browser in Google Cloud [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 months ago.
Improve this question
One particular user logs in to the console(logs in fine) and he clicks on SSH from the web browser. However he is getting the below error
enter image description here
then he tried logging in from the cloud console using the below command
gcloud compute ssh instance-name --zone ZONE
then getting the below error.
error
He is able to login to the console using the organization credentials and the password is not expired.
Google machines have password auth disabled by default.
I would suggest deploying a fresh machine.
Or ask the person who changed the auth configs about what they did.
Here are the steps to check out when you were not able to SSH VM.
Firewall open port 22 and check network tag.
Check CPU utilization to avoid high CPU usage.
SSH key is correct?
You can check the error logs in the serial console.
Likely you'd have to disable OSLogin. Don't use password authentication; it's just insecure ...GCE permits to provision RSA private keys with project/machine meta data. Only because someone didn't understand how it works, this doesn't justify tearing down the default security measures.

MariaDB Key Management options [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Having some trouble finding a workable solution for MariaDB key management.
In the words of one of our devops guys - "File key management is somewhat akin to taping your car's key to the windscreen". So, we are looking for a secure way to implement data-at-rest encryption, but we are having trouble with both of the other options listed in the documentation.
AWS KMS
The MariaDB documentation states the following:
The AWS Key Management plugin depends on the AWS SDK for C++, which uses the Apache License, Version 2.0. This license is not compatible with MariaDB Server's GPL 2.0 license, so we are not able to distribute packages that contain the AWS Key Management plugin. Therefore, the only way to currently obtain the plugin is to install it from source.
Our servers are managed, and the response we received from the devops team was:
Building things from source is quite an anti-pattern within the
context of a Puppet-managed environment, so we need to figure out if
this is doable in a sane and sustainable way
Eperi Key Management
The MariaDB documentation states the following:
It reads encryption keys from eperi Gateway for Databases.
I contacted Eperi to get information about their Gateway for Databases solution, and this was the response I received from their sales team:
We will not be able to serve you. Please look for another way.
So Im at a bit of a dead end here :(
Has anybody in a similar situation been able to find a workable solution?

Managed Service Provider on Google Cloud Platform [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
If a Managed Service Provider (MSP) wants to monitor existing GCP projects of a client that are associated to a client billing account ( meaning the client is directly paying to Google for it ) , how can the MSP start monitoring those ? What are the strategies around IAM that enable the MSP to start monitoring the client projects?
Using the Cloud IAM(Identity and Access Management), any member can be assigned with the access/control over the GCP resources/projects. You can check this documentation for various roles that can be given to a member.
For your specific concern over 'monitoring the billing', a member (in your case a MSP provider) can be given any specific role under “Cloud Billing Roles”. It will help that member to view/manage various billing scenarios over the GCP project/resources.
Apart from your use case scenario, you can also check this blog for various updates over MSP partners. You can make valuable suggestion by commenting there as well.

AWS and PuTTy. bad service request ssh-connection [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
The community reviewed whether to reopen this question 24 days ago and left it closed:
Original close reason(s) were not resolved
Improve this question
When I tried to access my EC2 instance using Putty, I got as error saying "bad service request ssh-connection". What did I do wrong and how can I fix this problem?
Here is what I did.
Created a new instance with new key pair.
PuTTy gen converted pem file into ppk file.
In PuTTy, I set host name ec2-user#Public DNS(IPv4).
Under Connection-SSH-Auth, I browsed for the ppk file I got earlier.
I unchecked Display pre-authentication banner and checked Bypass authentication entirely.
Then hit open
I should be able to access Amazon Linux Terminal but I got error, "bad service request ssh-connection"
EDIT:
I am sorry if this question was off topic. Since AWS, AWS-EC2, and PuTTy were all legit categories, I thought I could ask questions about them.
In step 3, remove ec2-user# and only keep your public DNS.
In step 5, check pre-authentication and uncheck Bypass authentication.

How to use one website with several amazon S3 buckets as a path suffixes?

Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 days ago.
Improve this question
Could you please advise - I would like to host multiple S3 Amazon buckets under one site in next way:
Access to bucket1 - http://example.com/bucket1(bucket2...) and so on.
What now Amazon allows is access with links like http://s3-ap-northeast-1.amazonaws.com/bucket1 , but this is not allowed in my case (production server). Note that site DNS is hosted also at Amazon Route53.
Thanks ahead