Signed URLs are great because it allows you to allow third parties access to a file without them having to authenticate against AWS.
Our primary use case is browser-based uploads. You don't want people uploading anything and everything, like the wordpress upload folder. And it's timed, so you don't have to worry about someone recycling the URL.
The user owns the copyright but grants an exception to Reddit where Reddit can do anything it wants with said content.
Reddit may license public content for commercial or non-commercial use.
Reddit has licensing deals with OpenAI and Google.
Reddit may presume that the user holds the copyright and is legally able to grant a license, but it isn't necessarily so. There are users who set their avatar to "Baby Yoda", or posted 3 paragraphs they transcribed from their print edition of Harry Potter and the Order of the Phoenix, or just copied photos from their classmate's phone camera app without asking.
If you look through Flickr you will find many photos and collections with fake licenses. All those sites you Google that advertise "Free Public Domain Clip Art / Stock Photos" maintain plausible deniability. Look through any wiki on Fandom.com and see whether the film studios go after their most ardent fans who upload dozens of stills and screenshots to promote The Twilight Saga or something.
In 1990 I wrote a configuration file to assist me in using GNU Emacs. I wrote and debugged it from scratch, in my free time, on my family's dime. I decided that it had a broad enough application to be useful to other Emacs users, so I submitted it to the developers. They included the file in a subsequent release of Emacs 18, and it was there for a decade or more.
My submission had been quite informal and, while I'd included some self-attribution at the top of the file, there was no explicit LICENSE or GPL or assignment of copyright. By submitting it to the developers of GNU Emacs for distribution, I had implicitly licensed it via the same GPL.
However, this informality was not enough to pass an audit later. By ca. 2010, they combed through the sources and removed the file I had submitted, along with others, because they were unable to track down the explicit licensing or copyright assignments that were seen as necessary by then.
Terraform is hard because it can be a different way of thinking about deployments and your infrastructure. And since it's declarative you can't do conditionals in normal ways.
What I used to do is create things in my target environment then try to recreate them in terraform (without the import, because import didn't really work so well). Then do an apply/plan and see what changes were listed.
What I would do today is ask ChatGPT for terraform for specific things, then see what it outputs, compare it with the registry, then do the apply.
Terraform is half the battle, the other half is figuring out how the specific provider represents their stuff...which is why ChatGPT is helpful.
Oh, and also look at your provider's examples. You presumably know how things work in your provider, so looking at their terraform registry will help you figure out how they model stuff in terraform so you can model your stuff in terraform.
Our primary use case is browser-based uploads. You don't want people uploading anything and everything, like the wordpress upload folder. And it's timed, so you don't have to worry about someone recycling the URL.
reply