This should not affect your issue, but you can reduce some of that code by not constructing the Resource and bucket:
S3::Object.new(bucket_name, key).put(body:’…’, content_type: ‘…')
Also, your issue is that it is “uploading both files to the last environment’s bucket” — in the example you gave above, they list the same bucket name.
regardless of bucket name, it should tell which account by the credentials passed to
Aws::S3::Client, right?
my issue is that the default doesn’t even have a bucket named
my.bucket
I’ve got a test for this:
I have 2 profiles in my ~/.aws/credentials that are completely separate AWS accounts (one is my personal, one for my company)
I created an ran this script. I do not have a bucket named reports in my personal AWS account, but this puts the first object in my company account’s report bucket
require 'rubygems'
require 'aws-sdk'
creds1 = Aws::SharedCredentials.new(profile_name: 'erik')
s3_client1 = Aws::S3::Client.new(region: 'us-east-1', credentials: creds1)
s3_resource1 = Aws::S3::Resource.new(client: s3_client1)
s3_bucket1 = s3_resource1.bucket('reports')
object = s3_bucket1.objects.first
p object
What is Aws::SharedCredentials.new doing if not what you expect? The ability to write to a bucket is not strictly limited to a single account. That is the default, only the bucket owner may write, but you can open the public for public writes, or even white listed users and accounts.
now I’m getting the appropriate AccessDenied exception
The reason being is that I have ec2 instances where ec2config is configured to set a new administrator password on each launch. A reboot counts (apparently), and so i'm in a position where i'm baking an AMI, and need to orchestrate reboots, and therefore need to wait for the the password to both be available and different.
The EC2:GetPasswordData operation helpfully has a timestamp - so I think i just need to know how to create the waiter which takes a date time as a parameter to compare against
instance = Aws::EC2::Resource.new.instances.first
old_timestamp = instance.password_data.timestamp
instance.reboot
instance.wait_until { |i| i.password_data.timestamp != old_timestamp }
one thing i did run into was that
response in the block was nil on at least the first attempt, which seemed odd
i wanted to do
... do |attempts, response|
puts "#{attempts}; timestamp this time: #{response.password_data.timestamp}"
end
but response was
nil
@trevorrowe yes
proc = Proc.new do |attempts, response|
logger.debug "Waiting for password data timestamp to be newer", {pwd_timestamp: instance.password_data.timestamp, newer_than: since}
end
instance.wait_until(max_attempts: 30, delay: 10, before_wait: proc) { |i| i.password_data.timestamp != since }i is an Instance resource
to combat that, i've changed my waiters to look like, for example,
w.max_attempts = 15
w.interval = 0
w.before_attempt do |a, resp|
pause_exponentially n
logger.debug "Waiting for password...", {instance_id: id, attempt_count: a}
end
def pause_exponentially(n, seed=2, exp=1.4)
sleep(seed * (exp ** n))
end
it would be really handy to be able to change that in just a single place (with the capability probably of still being able to configure the seed and exponent-even-if-that's-the-wrong-mathematical-term for each waiter)
There is not an accessible way to change the default waiter value currently. Currently, the waiter provider is a private interface, and is subject to change. If you are comfortable poking into something that may change in the future, you could do the following:
EC2::Client.waiters.instance_variable_get("@waiters")[:instance_running][:delay] = 20I’d be open to suggestions on how to make this more flexible, until then, I left the interfaces marked @api private.
@trevorrowe in v1 of the sdk, I'm reasonably sure AWS::EC2::Image had an
exists? method...? v2 does not. Aws::EC2::Instance does. the API reference doesn't show either Instance or Image to have an attribute that sounds like 'exists' other than maybe state on Instance.
but even that is tenuous
i can use the wait_for_exists instance method on Instance (hehe), but there's no equivalent on Image.
... could there be?
@ShotaKameyama There is a SNS developer guide that goes through the major steps: http://docs.aws.amazon.com/sns/latest/dg/SMSMessages.html - You can use Aws::SNS::Resource from the
aws-sdk gem to make the API calls.
`validate!': parameter validator found 2 errors: (ArgumentError)
- unexpected value at params[:code][:s3_bucket]
- unexpected value at params[:code][:s3_key]
but I am just passing in strings of the bucket name and s3 key to my jar
it works when I pass these values on the console
Hi there, doing more stubbing in my tests and have a question (issue #187)… is it possible to stub a response to a request for a particular DynamoDB table? i.e. can I further specify the table name somehow in this line of code?…
Aws.config[:dynamodb][:stub_responses] = {put_item: 'ProvisionedThroughputExceededException’}
You should rely on your test framework to provide that functionality. If I were using RSpec, I would do it this way:
allow_any_instance_of(Aws::DynamoDB::Client).to receive(:put_item).
with(hash_including(table_name:'my-table').
and_raise(Aws::DynamoDB::Errors::ProvisionedThroughputExceededException)
hey @trevorrowe, just an FYI, I couldn’t get this to work by just raising
Aws::DynamoDB::Errors::ProvisionedThroughputExceededException. I kept getting an ArgumentError returned (ArgumentError: wrong number of arguments (0 for 2)). I finally figured out that this had to do with the constructor of the error. Perhaps, this is expected, but I didn’t realize it. Setting nil for both params made this work.allow_any_instance_of(Aws::DynamoDB::Client).to
receive(:put_item).
with(hash_including(table_name: "Users")).
and_raise(Aws::DynamoDB::Errors::ProvisionedThroughputExceededException.new(nil, nil))