aws-access | Update an AWS security group with your current IP | AWS library

Based upon the questions' comments, the Python requirements.txt file is located in the API directory. This command is is specifying the Dockerfile using a path in the API directory, but building the container in the current directory.

I use jest-dev-server and then solve it.

For what I checked here, the problem is on your setup job. You set 2 outputs fields for this job, with the same output names, but related to different steps (Set Vars and Set Prod Vars).

You can't have more than o e output field per job.

I separated them into 2 different jobs and it resolved the workflow error. You can check the final implementation here .

Note that I also updated the needs jobs for the subsequent jobs and outputs so it should work as expected.

Until recent update aws actions required aws creds to be configured as github repo secret. After which it sets up as those creds in to env vars which makes them accessible in entire github action.

In your yml file it should be like this

The error message indicates that the given role or keys are not valid to execute the action.

You set access key and secret key in both the 'configure AWS credentials' and 'Run CodeBuild' steps. Looking into the Repository for 'aws-actions/aws-codebuild-run-build@v1' it seems that it only needs to be configured in the first step. Not sure how many environments you are expecting to deploy to but if there is only one, then env is redundant.

https://github.com/aws-actions/aws-codebuild-run-build

Somethink like this I expect:

There is a missing permission for the user user/service-account-ecr-push:

The error shows that you are wrong in Jenkin domain: http://jenkins.example.net:8080/ Replace it with your correct domain

Error message: "socket.gaierror: [Errno -2] Name or service not known" mean your program cannot make a connection to this domain because it does not exist or DNS can not resolve

When you run the command docker run -p 8000:8000 amazon/dynamodb-local the process never exits, so the Github run block doesn't actually know when to move on to the next step—it just hangs there forever.

What I did in my project is simply background it, by using the & after the command:

Turns out the snowflake.connector Python lib we were using has this issue where if an error occurs during an open Snowflake connection, the connection is not properly closed and the process hangs. There is also another issue where certain errors in that lib are being logged and not raised, causing the first issue to occur silently.

I updated our snowflake IO handler to explicitly open/close a connection for every read/execute so that this doesn't happen. Now my scripts run just fine in the container on CircleCI. I still don't know why they ran in the container locally and not remotely, but I'm going to leave that one for the dev ops gods.