Reputation
3,307
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
17 39
Newest
 Revival
Impact
~168k people reached

May
8
revised Spot instances frequently terminated in AWS auto scaling group (failing system health check)
Updated regarding additional reasons for spot instance termination and resp. monitoring options.
May
8
revised Spot instances frequently terminated in AWS auto scaling group (failing system health check)
Quoted message in question; added tag.
May
8
answered Spot instances frequently terminated in AWS auto scaling group (failing system health check)
May
1
awarded  amazon-ec2
Apr
1
awarded  Necromancer
Apr
1
revised Set TTL for CloudFront files to 1 year
Shortened/Formatted overly verbose suggested edit; added hints on Cache-Control max-age preference and minimum TTL effects.
Mar
19
comment AWS IAM user access issues for S3
According to Sid, it is is an optional identifier that you provide for the policy statement, which must be unique within a policy. Given it seems to work fine w/o (but see below), I tend to remove it here for brevity and when versionizing policies, but do not bother when generating policies automatically for example - however, as per the subsequent Note: Some AWS services (for example, Amazon SQS or Amazon SNS) might require this element [...].
Mar
19
answered AWS IAM user access issues for S3
Mar
17
answered Restrict the visibility of EC2 instances using IAM accounts
Mar
17
comment Restrict the visibility of EC2 instances using IAM accounts
When you say 'IAM accounts', I presume you mean multiple 'IAM users' within a single 'AWS account'?
Feb
11
awarded  Announcer
Jan
21
revised IAM policy to restrict access to one VPC
Inlined/Added links.
Jan
21
answered IAM policy to restrict access to one VPC
Jan
20
awarded  Revival
Jan
14
answered What algorithm does Amazon ELB use to balance load?
Dec
9
revised MogileFS/GlusterFS/etc + Amazon EBS + Amazon EC2
Removed link to dormant/parked domain,
Dec
4
awarded  Popular Question
Nov
25
comment AWS Cloud Formation.Requires capabilities : [CAPABILITY_IAM] (Child Stack)
Thanks for following up with your discoveries - this seems to match previous observations of mine, but ironically we seem to encounter the inverse behavior as of recently, i.e. CAPABILITY_IAM is now always required once a sub stack resource is involved, even if it doesn't create IAM resources (e.g. the Nesting a Stack in a Template example exposes this behavior, and this happens at the API level). Unfortunately this obstructs other use cases now - has AWS contacted you about this change?
Nov
25
answered How can I give an AWS IAM user permissions to manage his own security credentials?
Nov
11
awarded  Announcer