Alexey Zapparov

I think this one is covered by [AmazonSSMManagedInstanceCore](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonSSMManagedInstanceCore.html)

@mikhailshilkov it makes sense, indeed. But then it becomes somewhat weird still. If I create subscription outside of the topic, e.g. with AWS-Classic, as I want that subscription to be...

I mean, it makes sense. But still, I find it confusing. :D

Opened a PR with fixes to the above linting errors.

I'm fine if those checks will be disabled (globally or locally via comments). Just went the lazy approach by doing what SC proposes and making sure tests pass after that...

It's also worth to mention in the README that configuration like: ``` ruby Geocoder.configure( cache: ..., cache_options: { expiration: 1.week }, ... ) ``` Sets prefix to `nil`, not the...

> I'm not sure about the `unit_of_work` in the interface. Maybe a queue name would be enough? I'm just thinking about how it can be done in a bit more...

After giving it another thought, I think we can keep it simple :D just queue name.

> I like the `Sidekiq::JobRecord` idea tho. 😄 I do like it too. But it will involve object creation even when user does not need it (e.g. just caring about...

I'm inclined towards `do |queue, message|` approach.