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.
tCaT stack name prefix unusable as S3 bucket name prefix
See original GitHub issueThe default prefix for stack names is tCaT, which is problematic if the someone uses the stack name as prefix for S3 bucket names because it contains uppercase characters.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
tCaT stack name prefix unusable as S3 bucket name prefix #271
The default prefix for stack names is tCaT, which is problematic if the someone uses the stack name as prefix for S3 bucket...
Read more >Organizing objects using prefixes - AWS Documentation
You can use prefixes to organize the data that you store in Amazon S3 buckets. A prefix is a string of characters at...
Read more >List Objects from AWS S3 bucket using ASP.NET
I'm getting every object from my bucket using this and when I'm trying to use the prefix and delimiter it's not working. AWS...
Read more >Enable Logging to a Cisco-managed S3 Bucket
You can set up Umbrella to log events to an Amazon S3 bucket that Cisco manages. ... <AWS S3 bucket name>-<AWS region>/<AWS S3...
Read more >Exporting data to Amazon S3 by using asset property ...
Each resource's name includes a prefix that you can customize when you create the stack. Resources include the following: An Amazon S3 bucket....
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
@villasv - We’ll discuss internally early next week and circle back. Most of us are traveling today. Just an FYI - we’re not ignoring!
@villasv - Apologies for the latency on this. I’m going through our backlog and trying to sort out issues that need to be fixed in v0.8 versus ones that make more sense to integrate into the v0.9 branch.
The tCaT vs tcat issue aside, can you confirm this works as intended now? I see we’ve added logic to ensure user-provided bucket names are all lowercase, but I want to verify that the signature aside, there’s nothing outstanding here?