configure-aws-credentials
s3-sync-action
configure-aws-credentials | s3-sync-action | |
---|---|---|
20 | 7 | |
2,287 | 1,006 | |
1.2% | - | |
9.4 | 0.0 | |
11 days ago | about 1 month ago | |
TypeScript | Shell | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
configure-aws-credentials
-
CI/CI deploy a static website to AWS S3 bucket through Github Actions
The AWS configure-aws-credentials Github Action allows the connection to the AWS S3 bucket through an AWS Role. The configuration of this role is explained in the next chapter
-
How to Get Preview Environments for Every Pull Request
In this example, we'll be using the aws-actions/configure-aws-credentials action with GitHub's OIDC provider. Make sure the configured role has the required permissions.
-
Better GitHub AWS Secrets with OIDC
The first step is to set up GitHub Actions as a recognized identity provider in my AWS account. This is also called an "OIDC Trust" relationship. In AWS IAM, create an Identity Provider with GitHub's provider URL and Audience. I am using the open-source action configure-aws-credentials (link) which means I want to use an Audience value of sts.amazonaws.com. Be sure to click the "Get Thumbprint" button to save a copy of the x.509 certificate used by GitHub into the AWS identity provider.
-
Deployment github and aws, how to correctly use secrets?
You can use configure-aws-credentials Github aciton. Which is pretty good. Here is a blog post about it from AWS: https://aws.amazon.com/blogs/security/use-iam-roles-to-connect-github-actions-to-actions-in-aws/
-
AWS SSO & GitHub OpenID Connect Setup
We are now ready to utilize configure-aws-credentials within our GitHub Actions as we move onto deploying our code!
-
AssumeRoleWithWebIdentity WHAT?! Solving the Github to AWS OIDC InvalidIdentityToken Failure Loop
The AssumeRoleWithWebIdentity error manifests itself mostly around parallel access attempts, and how the various AWS interfaces are able to authenticate, as well as run and deploy services. We started encountering this issue when running our pipelines for deployment, and attempting to authenticate our Github account to AWS via the OIDC plugin. This is a well-known (and widely discussed) limitation for authentication to AWS for web application providers. In our case it was Github, but this is true for pretty much any web application integration.
- request critical feedback on the yaml for my first github action, please
-
Deploying to AWS from GitHub actions: is this something Fortune 500 security reviews will cry about?
What you are looking at is totally doable, you MUST use: https://github.com/aws-actions/configure-aws-credentials
-
Trending open source repositories on GitHub
AWS Actions: It's an open source project from AWS which the goal is to get easy to Configure AWS credential and region environment variables for use in other GitHub Actions.
-
App with self-contained infrastructure on AWS
In order to achieve this, AWS credentials need to be properly configured. Here we use a handy Github action called configure-aws-credential, from AWS itself. You can also read more about the many methods of authentication available. This step requires the AWS_REGION and AWS_ROLE_ARN secrets to be properly configured in the repo, both of which that should be shared by the platform team.
s3-sync-action
-
Bringing together Hungarian technology conferences
I cannot ignore the fact that I am an AWS Community Builder, so it was a no-brainer that I would implement this on AWS. Registering a domain and setting it up on Route 53 was the first step. Then I looked at the possibilities of hosting. The site is written in Jeklly and each page is generated separately. Using GitHub Actions, I can regenerate the static pages every time there is a new commit. Hosting a static website on AWS isnβt rocket science. S3 static file hosting is a cheap and easy way. I just needed to find a way how to publish my files to S3. Jake Jarvis created a GitHub Action that can sync your files to S3. All you have to do is to create the appropriate IAM permissions and your files will be pushed to the S3 bucket of your choice. From there, AWS will do the rest. I have created a CloudFront distribution to get HTTPS and fast access from Hungary. Currently there is no AWS region in Hungary, but there is an edge location in Budapest, so serving the site from there gives fast access to Hungarian users. π₯π₯π₯
- Cheap way to host a Javascript project. (e.g. Node APIs & React Apps)
-
request critical feedback on the yaml for my first github action, please
I mean.. I would probably just have used https://github.com/marketplace/actions/s3-sync :)
-
Nestjs + Nextjs Monorepo with AWS
I would consider sending the UI build files to S3 using either cloud formation or Github Actions. For the backend, sounds like a docker container could serve you well and cloudformation or Github Actions can handle this.
-
CI/CD failing for permission... anybody can help me?
The action in GitHub is the following (as per instructions here : https://github.com/jakejarvis/s3-sync-action )
-
How do you implement your Front-end build & deploy process?
You can deploy your frontend build to S3, then point your domain to these files, for example with CloudFlare or Route53. We use a Github action to publish these for each deploy. This makes the frontend and backend effectively two different services.
-
15. CI/CD (Front end)
Git hub actions pushes the source code to my S3 bucket the moment they are pushed to my git repository using a git actions. Git action: https://github.com/jakejarvis/s3-sync-action
What are some alternatives?
kubectl-aws-eks - A Github action for kubectl, the Kubernetes CLI
git-repo-sync - Git Repo Sync enables you to synchronize code to other code management platforms, such as GitLab, Gitee, etc.
buildkit - concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
build-hugo - A GitHub Action to build Hugo site.
setup-buildx-action - GitHub Action to set up Docker Buildx
git-repo-sync - Auto synchronization of remote Git repositories. Auto conflict solving. Network fail resilience. Linux & Windows support. And more.
goss - Quick and Easy server testing/validation
terraform-multienv - A template for maintaining a multiple environments infrastructure with Terraform. This template includes a CI/CD process, that applies the infrastructure in an AWS account.
actions - GitHub Action for Infracost. See cloud cost estimates for Terraform in pull requests. π°π Love your cloud bill!
terraform-security-scan - Run a security scan on your terraform with the very nice https://github.com/aquasecurity/tfsec
Klayers - Python Packages as AWS Lambda Layers
jekyll-action - A GitHub Action to publish Jekyll based content as a GitHub Pages site