- Le plus récent
- Le plus de votes
- La plupart des commentaires
If you have a private webserver it has no network egress, and as such you must include the additional Python libraries as WHL files:
Alternately, you can specify in URI format in Secrets Manager or SSM:
https://docs.aws.amazon.com/mwaa/latest/userguide/connections-secrets-manager.html
If using a public webserver, check your requirements install webserver logs in CloudWatch for errors.
Thanks John, I set the Web Server Access to public network. From the web server logs I figured out that there was a conflict between the requirements file and the constraints file. I removed the versions from the requirements file and literally everything from inside the constraints file (but still left the empty file there) and tried again. That seems to have worked. I can now get snowflake to show as an option in the connection type drop down.
Contenus pertinents
- demandé il y a un an
- demandé il y a un mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 8 mois
- Comment dépanner mon environnement Amazon MWAA bloqué à l'état « Creating (En cours de création) » ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
I now have the Connection Type showing Snowflake (yay!!), but when I put in all my credentials I get this error:
250001: 250001: Could not connect to Snowflake backend after 0 attempt(s).Aborting
The MWAA environment has web server access set to
Public network
and the new connection has the following configuration:Connection Type: Snowflake
Host: https://abc1234.us-east-2.aws.snowflakecomputing.com
Schema: PUBLIC
Login: my_login_name
Password: my_password
Account: abc1234
Warehouse: COMPUTE_WH
Database: RAW
Region: us-east-2
Role: ACCOUNTADMIN
Any idea what could be causing the connection to fail? I read in stackoverflow that removing the 'https://' from the host input helps but that did not seem to do anything when I tested myself.