Re:Show HN: An API to provision custom hostnames with SSL
by subway on Wednesday August 30, 2017 @06:46PM
(#15136762)
You don't need AWS keys at all. This enrollment flow flies in the face of best practices.
Intead, you should be providing your users with instructions to create an IAM role for cross-account utilization. Ideally in addition to the instructions, you'd provide a minimal CloudFormation template defining such a role, with your minimum required permissions.
Asking a customer to create a user and ship you a secret is asking for trouble.
Re:Show HN: An API to provision custom hostnames with SSL
by schlarpc on Wednesday August 30, 2017 @09:07PM
(#15137389)
And when you use a role like this, you really should use an external ID to avoid confused deputy attacks.
http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_cre...
Re:Show HN: An API to provision custom hostnames with SSL
by samstave on Wednesday August 30, 2017 @09:30PM
(#15137472)
DING DING DING
The problem is that a junior level of exposure may result in access+secrets being mistakenly given out.
Yeah - they should be looking into say, cloudability, or any number of thousands of offerings ding just this.
Re:Show HN: An API to provision custom hostnames with SSL
by theossuary on Wednesday August 30, 2017 @06:01PM
(#15136466)
One thing I really appreciate from companies is when they give me a policy with just the permissions they absolutely need to function (or a reference to a cross-account policy). That way I can review it and I'm not dicking around with trying to figure out the right permissions, and I know what all you may have access to. Getting s3 objects may be a deal breaker for example, unless the action is properly scoped to a bucket.
Re:Show HN: An API to provision custom hostnames with SSL
by mrkurt on Wednesday August 30, 2017 @06:19PM
(#15136597)
Yeah agreed. We should make that explicit, or even give people a CloudFormation template to set up a restricted policy.
And to be clear, we don't need s3 access unless you want to serve files from a private s3 bucket. Most sites don't use that at all.
It should be obvious when and what we need AWS keys for. We only need those for private S3 buckets and to invoke Lambda functions. We don't want full access keys, just scoped IAM stuff!