Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Point-by-point:</p> <ol> <li>"<strong>Can the user have a Password set?</strong>" The user can have a password set, though for API access I do not believe a password can be used directly. Nothing about having a password set <em>prevents</em> API access.</li> <li>"<strong>should I use a group or user policy to grant access?</strong>" The distinction between user vs group policies is just a matter of organisation. If several of your users require access "for the same reason", then it makes sense to create a group policy. If every user has a specific set of requirements, for reasons which do not overlap, then individual user-policies make more sense. It's basically a question of future administration: If the policy requirements changed in the future, would you be more likely to need to make the same change across multiple users, or to make various individual changes?</li> <li>"<strong>I only want this user to be able to write objects</strong>" The policy generator can help with this, but the key things you need to know are: <ul> <li>The type of action you're looking for is "s3:PutObject". Depending on what you actually mean by "write", you may need a couple of other permissions as well: "s3:DeleteObject" and "s3:ListBucket" are common extras.</li> <li>The "arn" would be: ""arn:aws:s3:::bucketNameGoesHere/*", or replace the asterisk with something more-specific to limit "puts" to a given prefix"</li> </ul></li> </ol> <p>Below, I have included a basic policy which might do what you want. I expect it will require some tweaking to be exactly what you need:</p> <pre><code>{ "Statement": [ { "Sid": "AnyUniqueIdentifierForThePolicyStatementGoesHere", "Action": [ "s3:PutObject" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::YourBucketNameGoesHere/*" ] } ] } </code></pre> <p>Hopefully that is at least enough to point you in the right direction.</p> <p>useful links:</p> <ul> <li><a href="http://awspolicygen.s3.amazonaws.com/policygen.html" rel="nofollow">http://awspolicygen.s3.amazonaws.com/policygen.html</a></li> <li><a href="http://docs.amazonwebservices.com/AmazonS3/latest/dev/UsingBucketPolicies.html" rel="nofollow">http://docs.amazonwebservices.com/AmazonS3/latest/dev/UsingBucketPolicies.html</a></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POAmazon IAM User + Granting Access to S3
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USWill Palmer
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload