12 ms·
A lot of Go code using the Go AWS SDK that's useful as a non-trivial example in and of itself. Is this IaC "light" for purposes of setting up and tearing down
by r00tanon 4y ago
A lot of Go code using the Go AWS SDK that's useful as a non-trivial example in and of itself.
Is this IaC "light" for purposes of setting up and tearing down small applications for experiments or demos?
Obviously a lot of effort spent. Of course, once you know AWS well enough to "make it easy", by that time, you've found the need for tooling which supports the harder stuff. And, frankly, someone new to AWS needs a lot of context just to understand the canonical ways to wire stuff together in AWS to even comprehend which pattern will be useful.
For example, S3 events are really backed by SQS under the covers, with implied retries on failure, but no DLQ support, and a lambda that triggers on an arriving S3 event may need to account for "duplicate" events, etc. That's just one wrinkle that even a simplified configuration might require more complex understanding of the underlying AWS ecosystem.