How can I connect S3 protcol via http? - open-source

[Client] Cyberduck ver 5.3.7 on Mac(Serria)
[Host] QNAP TS853A (application) Object Storage Server
I would like to connect Object Storage Server of QNAP by S3(Amazon simple storage service).
I made he "hdd01" of a storage account name and added user to it.
Then I'll try to connect it by Cyberduck application.
But I can't set URL : "http://...".
How can I set up http protcol?
By the way, I have no experience of connecting.

You will have to install a generic S3 HTTP profile from wich is available in two variants
Authentication with signature version AWS4-HMAC-SHA256
Authentication with signature version AWS2

Related

How to securely connect to a database in Next.js app (using Prisma and MySQL) deployed to Vercel (serverless)

My MySQL database on DigitalOcean is locked down to only be accessible via local connection.
I'd strongly prefer to keep it secure like that (i.e. not to open it up).
I'm used to using SSH tunnels to connect to it (such as ssh -L 3306:localhost:3306 -i ~/.ssh/id_rsa myusername#myhost).
Now that I'm deploying a Next.js app (with Prisma) to Vercel, I'm trying to figure out the appropriate DATABASE_URL environment variable.
How can I set the DATABASE_URL environment variable (or whatever other relevant setting) such that my Next.js backend is able to securely connect to my remote database that is only open to local connections?
I couldn't tell from the docs.

Azure web app with MySQL cannot connect to database through Virtual Network Service Endpoints

I have a PHP web app (Snipe-IT) that was previously working.
We went through a security review, and the recommendation was made to enable service endpoints (Microsoft.Sql) on the application subnet so that web apps connect to databases over the Azure backbone. Everything is working fine for the other MSSQL apps, except for our Snipe-IT application, which connects to a GP_Gen5_2 MySQL instance.
The error message says:
D'oh! Looks like we can't connect to your database. Please update your database settings in your .env file. Your database says:
SQLSTATE[HY000] [9009] Client connections to Basic tier servers through Virtual Network Service Endpoints are not supported. Virtual Network Service Endpoints are supported for General Purpose and Memory Optimized severs. (SQL: select 2 + 2)
This error message doesn't match the environment configuration because the database in question is a General Purpose, 2 vCore(s), 50 GB database.
There is no networking tab on the MySQL server, but in the Connection security tab we have tried enabling access to Azure resources, allowing the full public internet (0.0.0.0 - 255.255.255.255), enabling and disabling forced SSL, but nothing changes the result.
Azure won't let us create a Private Endpoint on the MySQL database because 'the subnet contains external resources'
I am hoping there is a way to resolve this without having to rebuild both the app and database in a different App Service Environment and subnet.
Thanks

Connect to snappy data with aws external IP address

I am using Tibco ComputeDB, which is new to me. It uses sparkDB and snappyData. I can start both Spark and SnappyData and connect to snappydata using command connect client '127.0.0.1:1527' or with internal IP of aws server. But when I try to connect it with aws external IP using above command it do not work. Also I am not able to connect to snappyData from client like sql workbench/J. I have all required drives installed on local machine and server and also all ports are open on aws server. I can access dashboard using http://externalip:5050.
I also edited conf/locators and conf/servers file as explained in below link and also hostfile entry seems fine.
=> https://snappydatainc.github.io/snappydata/howto/connect_to_the_cluster_from_external_clients/
Lines were as below
=> "Private IP" -client-bind-address="Private IP" -hostname-for-clients="Public IP"
=> "Private IP" -client-bind-address="Private IP" -client-port=1555 -hostname-for-clients="Public IP"
I follow below document to connect with JDBC.
=> https://snappydatainc.github.io/snappydata/howto/connect_using_jdbc_driver/
But still not able to connect with external IP.
=> connect client 'externalIP:1527'; should work before I can connect to snappydata from any client using external IP?
Can someone guide that what setting should be made to connect snappydata from aws external IP and with any sql client.
Are the ports open for the public IP of the AWS instance itself? Right now that is needed if you connect using the public IP, even if you are trying to connect from the same AWS instance via connect client ... command.
Thumb rule is that ports (e.g. 1527-1528) must be open for the client's IP in the security group. So, if the client is in the same AWS instance, then ports must be open for it's public IP.
If this doesn't help, can you paste the content of files locators, servers and leads which are present under conf/ directory? You can remove/strike sensitive information in them, if any.
Also please paste the error messages you see.
We have refined the steps to set up the cluster on AWS here that could clear a few things: https://snappydatainc.github.io/snappydata/install/setting_up_cluster_on_amazon_web_services/#usingawsmgmtconsole

Amazon RDS Mysql Databse with TLS 1.2 and ASP.NET Application

We are trying to access our MySql RDS instance which is tls1.2 enabled. Our AWS asp.net application server also has tls1.2 protocol enabled. But Application is not able to make connection to database with the error.
We have tried with enabling various Ciphers and also applying .pem files with asp.net connection string. But still can not connect to it. However no connection string is working out for us.
Error: The handshake failed due to an unexpected packet format.
After few changes in the server cipher settings we are now able to connect to the RDS instance using our C# console application (mysql connector latest version)
Below are the findings :
application level (code) changes : None
Server Crypto settings ( using Nartac ) : Best Practices
machine (currently tested from DB server to RDS instance ) TLS version : v1.2 enforced
RDS TLS version : v1.2 enforced
My connection string :
**<add key="conns" value="SERVER=asdf.asdfasdfa.eu-west-1.rds.amazonaws.com;database=FFF;user=FFFF;PASSWORD=p#5sword;SslMode=REQUIRED;"/>**
Output : connection successful

Have connected to other website but am having trouble connecting to a AWS webpage via sim900 using arduino

I have connected to other websites but have been able to connect to AWS I have seen others had this issue before me but none of the threads I found were answered. I am hoping someone has suggestion I can post the code if necessary. Is there a special way to connect to the AWS website? The goal of the project is to send data to a web page which was created using Amazons AWS services. We are using an Access point and are using a Json format.
To establish a connection with AWS you must need a secured connection (https TLS 1.2) but the SIM900 firmware only provide TLS 1.0 (see the doc here : https://simcom.ee/documents/SIM900/SIM900_HTTPS%20AT%20Command%20Set_V1%2000.pdf)
I think I see somebody with the same configuration than yours (Arduino + sim900) who used a lib to connect to AWS.
Or you can establish a TCP connection with AWS and then use a lib to handshake and send data with TLS 1.2 protocol. More informations about TCP and TLS : https://medium.facilelogin.com/nuts-and-bolts-of-transport-layer-security-tls-2c5af298c4be