s3upload | Upload multiple files to AWS S3 | Cloud Storage library

I've migrated my react app to react-scripts 5.0.0 and now I get this error:

We have several lambda functions, and I've automated code deployment using the gradle-aws-plugin-reboot plugin.

It works great on all but one lambda functions. On that particular one, I'm getting this error:

I'm using the Serverless Framework to create a lambda that saves a CSV to a S3 bucket.

I already have a similar lambda that does this with another bucket.

This is where it gets weird: I can upload the CSV to the first S3 bucket I created (many months back), but I'm getting an AccessDenied error when uploading the same CSV to the new S3 bucket which was, as far as I can tell, created in the exact same way as the first via the serverless.yml config.

The error is:

I have 2 apps I have re-written from older versions of Rails (3.2 and 4.2.1) to Rails v6.1.4.1 and they both use the s3_direct_upload gem.

On Both apps I do not get any errors in the Webdev console or in the Rails console or in the log or ANYPLACE I can find. The buckets are displaying just fine in the case of Both Apps.
I checked the CORS Setup and it is fine. Both of these apps are currently running on Heroku with the code the same way it is now but are working.

Does anyone know if the s3_direct_upload gem actually works with Rails 6?

I get the file select window, I choose the filename, it shows the filename but instead of it starting the upload and showing the progress bar it just acts as if I did nothing at that point. No errors no nothing anyplace I can find. When I have the original app side by side at that point I should see a quick progress bar come up and then go away, the page refreshes and shows the new file. IN the 2 Apps I have re-written, it never gets past the file select and showing the file name of what I have selected. I will show the general files so at least that can be seen:

So that is question 1, does the s3_direct_upload gem work in Rails 6?

Here are the basic files that are required:

s3_direct_upload.rb

I'm following the automate_model_retraining_workflow example from SageMaker examples, and I'm running that in AWS SageMaker Jupyter notebook. I followed all the steps given in the example for creating the roles and policies.

But when I try to run the following block of code to creat a Glue job, I ran into an error:

I have a basic knowledge of await/async in Angular 2 following this exemple:

I have a dockerized postgres running locally, to which I can connect to via pgAdmin4 and via psql.

Using the same connection details, I set up an airflow connection on the UI

However, when trying to load a DAG that uses that connection, it throws an error:

Broken DAG: [/usr/local/airflow/dags/s3upload.py] Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/airflow/providers/postgres/hooks/postgres.py", line 113, in get_conn self.conn = psycopg2.connect(**conn_args) File "/usr/local/lib/python3.7/site-packages/psycopg2/init.py", line 127, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) psycopg2.OperationalError: could not connect to server: Connection refused Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 54320?

As mentioned, the postgres instance is running, and the port forwarding is active, as proven by successful pgAdmin and psql logins.

Any ideas?

I've installed below Plugins on Jenkins 2.249.3 version

1. https://plugins.jenkins.io/pipeline-aws/
2. https://plugins.jenkins.io/aws-codepipeline/
3. https://plugins.jenkins.io/aws-credentials/

My JenkinsFile is as below

Question: util.promisify converts an async function that uses the error-first callback style to a Promise. However it doesn't seem to work with AWS' S3.upload (scroll down to .upload) which is an async function that uses the error-first callback format.

Original format: