Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
AWS Fargate S3 Bucket name issue
See original GitHub issueBug description
S3 bucket names should be unique but the base-setup.yml file contains hardcoded BucketName: game-ci-storage line which makes the template creation fail.
https://raw.githubusercontent.com/game-ci/unity-builder/main/dist/cloud-formations/base-setup.yml
How to reproduce Follow the builder steps here.
We should either state this in the document or automate this process in code, maybe through build step parameters?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
aws-fargate-s3 - AWS Solutions Constructs
This AWS Solutions Construct implements an AWS Fargate service that can write/read to an Amazon S3 Bucket. Here is a minimal deployable pattern...
Read more >Can't access S3 bucket from within Fargate container (Bad ...
I'm able to access the same s3 bucket with boto3 on an EC2 instance without providing any kind of credentials and only using...
Read more >Install on AWS Fargate (ECS) - Athens proxy server
note: it is a good idea to use environment, region, and/or account ID as components to the bucket name due to their globally...
Read more >How to automatically process data with AWS fargate when ...
Go to the AWS console, in S3 service and click on “Create Bucket”. It will ask you for a bucket's name that must...
Read more >Tracking license usage on AWS ECS Fargate - IBM
Go to the AWS Console. Configure the S3 bucket to store the license usage data. The name of the bucket must follow the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@frostebite could you please have a look at this issue?
In the release branch
cloud-runner-develophttps://game.ci/docs/github-cloud-runner/configuration#release-branch-configurationThis has been resolved. The S3 bucket was never explicitly needed, so it’s been removed. This happened if you deleted the “base cloud formation” and tried to re-run cloud runner, which reinstalls the base stack if it’s missing. And AWS doesn’t delete the S3 bucket to protect your data by default.
So this can also be fixed by just forcing the S3 bucket to delete and running again.
This will be in the main release branch when either of these are merged #459 #437.
Please feel welcomed to reopen a ticket @edencakir if you have any more questions or issues. 🙏
Sorry it took a little while to get back to you!