ensure s3 objects are coming out of Virginia #151
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -14,7 +14,7 @@ | |||
| class LanguagePack::Base | |||
| include LanguagePack::ShellHelpers | |||
|
|
|||
| VENDOR_URL = "https://s3.amazonaws.com/heroku-buildpack-ruby" | |||
| VENDOR_URL = "https://s3-external-1.amazonaws.com.amazonaws.com/heroku-buildpack-ruby" | |||
There was a problem hiding this comment.
Think you added a bit more amazonaws.com than you needed here: s/s3-external-1.amazonaws.com.amazonaws.com/s3-external-1.amazonaws.com/
|
Are EU deploys built in US east right now? |
|
@schneems yeah, all builds are out of US east. |
From @mfine: S3 objects are sitting in the wrong side of the country, eventual consistency be damned. There is no US East region in S3; there is something called US Standard, and it runs out of Virginia AND Seattle datacenters. It's a legacy artifact and a source of endless operational pain within AWS. Objects are intended to be replicated across the datacenters, but sometimes this doesn't work out, and objects get stuck in one datacenter or the other. Since we run everything out of US East, it's operationally prohibitive to get things stuck in Seattle. This is a per object issue, not a per bucket issue - objects in the same bucket can end up in either Virginia or Seattle. This is really easy to do by accident - upload an object from your laptop in San Francisco, and you get bound to the Seattle datacenter. AWS provides endpoints that will bind objects either to Virginia or Seattle in US Standard. Be safe and prefer using s3-external-1.amazonaws.com. You can read more about it here: https://forums.aws.amazon.com/message.jspa?messageID=185820
hone
added a commit
that referenced
this pull request
Sep 25, 2013
ensure s3 objects are coming out of Virginia
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From @mfine:
S3 objects are sitting in the wrong side of the country, eventual
consistency be damned. There is no US East region in S3; there is
something called US Standard, and it runs out of Virginia AND Seattle
datacenters. It's a legacy artifact and a source of endless operational
pain within AWS. Objects are intended to be replicated across the
datacenters, but sometimes this doesn't work out, and objects get stuck
in one datacenter or the other. Since we run everything out of US East,
it's operationally prohibitive to get things stuck in Seattle. This is a
per object issue, not a per bucket issue - objects in the same bucket
can end up in either Virginia or Seattle.
This is really easy to do by accident - upload an object from your
laptop in San Francisco, and you get bound to the Seattle datacenter.
AWS provides endpoints that will bind objects either to Virginia or
Seattle in US Standard. Be safe and prefer using
s3-external-1.amazonaws.com.
You can read more about it here:
https://forums.aws.amazon.com/message.jspa?messageID=185820