• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off

Card Range To Study



Play button


Play button




Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

17 Cards in this Set

  • Front
  • Back

What is S3 defined as?

Storage for the internet

What are the two players in S3?

Object and buckets

What are the two attributes of an object?

  • The file itself
  • The meta-data associated with the file

What would be determined by bucket-level permissions?

Who can create objects

Who can delete

Who can list

What is a corollary of the extent of those permissions?

Objects are immutable, they are not updated.

What else can I control about a bucket?

Which region it sits in

What restrictions are there on bucket creation?

  • The name cannot be changed once set
  • It must be DNS compliant
  • It must be unique across all existing bucket names in S3

What options do I have when uploading an object to a bucket to keep it safe?

Encryption at rest

If upload an object aircon.pdf to a bucket called cricket-fixtures in the Sydney Region (Asia Pacific 2, what would the url be?


Why would you empty rather than delete a bucket?

Stop someone allocating it if you want to use it in the future

What is the default bucket limit for an account?


What is the limit for objects in a bucket?


How can I change the region of a bucket once it's created?

You can't

What is an important design consideration wrt bucket creation and updates?

The create and delete operations are slow, and should therefore be done in a 'background' operation, not as part of a user interaction

Why are bucket create and delete operations slow?

Because they have to check 'globally' for the bucket name, or update all regions when it's deleted.

Which operations are appropriate for 'use-case' level operations?

Operations on the objects, rather than the buckets themselves

What is an important consideration when my application creates bucket names on the fly?

That is has logic to handle the name already being taken and can retry with a new name