4 ms·

> AWS doesn't even have a way to report a bug... what "on top of the list" are you talking about? Who else is on that list? You gotta love these assertions at

by primax 3y ago

> AWS doesn't even have a way to report a bug... what "on top of the list" are you talking about? Who else is on that list? You gotta love these assertions at the top of a post that flag people who confidently are saying they have no idea what they're talking about. You can report bugs via your solution architect, via support, or via the Re:Post bug report tool. > AWS support is atrocious, unless you cozy up to them somehow to get special treatment. If you are a "regular" customer, you get zilch. AWS offers best performance for the best price, that and they are the largest service provider is what makes them succeed. They don't need to spend anything on support -- it's not cost effective. Even basic support is great, I've had most of my issues fixed within 8 hours. If you pay for business or enterprise support you'll have a dedicated person you deal with. Try comparing that to GCP... > My personal experience: we provided a service through AWS marketplace related to storage. So, we are not your "regular" customer, had to pay them some for accreditation... and here's the thing: it's probably something about how we create EBS snapshots, but about every thousand or so snapshots creation stalls. Doesn't fail, doesn't succeed, just hangs forever. There's nobody to talk to in AWS about this. People who "certified" us (what a joke...) cannot do anything about this problem. If you were a solution partner you would have had a partner solution architect who would take point on this problem for you. This sounds like your organisation didn't accurately share access to this resource with the right people. > And there's more stuff like that. Sometimes some resources won't delete first 1-2-3 times you try. Some other resources are created, but don't work once in a blue moon. And all you can do about it is just curse and try again. I've been AWS facing for 11 years and I can count on one hand the times this has happened. Did you file a support ticket? Source: Work in an AWS consultancy, before that was running tech for a startup on AWS

Aeolun 3y ago
> I can count on one hand the times this has happened You must never have worked with CloudFormation/CDK. What a shitshow. If you need to do anything non-trivial you are basically guaranteed to need a whole ream of dirty hacks and workarounds. To be fair, that’s during creation. I’ve never had resources not work after creation.
- pfych 3y ago
  I work with CloudFormation scripts extremely often in my line of work and while confusing at first they're extremely clean once you wrap your head around them. Like any tool or language there are multiple ways to approach issues, your solution can be clean and efficient or "a ream of dirty hacks", it really depends on how familiar you are with the tools.
- ovao 3y ago
  CDK itself relies on a good number of hacks and workarounds, some of which are not well-vetted at all in my experience. Some of the workarounds are really a symptom in my opinion of certain resources not being part of CloudFormation itself, when if they were, it feels like it’d be almost entirely a non-issue. It’s a little odd that at this point in the game, the prospect of “make a thing that depends on another thing” is still not an entirely solved problem within AWS.
tylergetsay 3y ago
it's also worth noting that AWS has support reps split out based on your business sector. working in education related space we have an edtech rep.
VectorLock 3y ago
Every year, managing 4000-5000 instances at least a handful of instances will fail to transition states for me. Support ticket usually clears it up.
crabbone 3y ago
> You can report bugs via your solution architect, via support, or via the Re:Post bug report tool. My solution architect? Do you realize that most AWS customers don't have an assigned solution architect? Also, yes. We did talk to our solution architect. That's the part where "what a joke" comes in. Solution architect owes you nothing. Not even an acknowledgement that the development team on the other end received the information. You will never see the ticket in any kind of a bug tracker, no indication that any work on your problem has been done. Like I said, zilch. Support in AWS doesn't exist. That is not a thing. There's support of financial issues. There's no such thing as tech support in AWS. Re:Post is dead. Nobody ever replies there. No developer within AWS has a duty to look into that board. It looks like it's mostly intended for customers to help each other out. It's more like a place you can go to vent, if you feel very frustrated. Nobody owes you any follow up, nobody notifies you if things are fixed. It's not a substitute for bug tracker or customer support.

by primax 3y ago

Aeolun 3y ago

> I can count on one hand the times this has happened You must never have worked with CloudFormation/CDK. What a shitshow. If you need to do anything non-trivial you are basically guaranteed to need a whole ream of dirty hacks and workarounds. To be fair, that’s during creation. I’ve never had resources not work after creation.

pfych 3y ago
I work with CloudFormation scripts extremely often in my line of work and while confusing at first they're extremely clean once you wrap your head around them. Like any tool or language there are multiple ways to approach issues, your solution can be clean and efficient or "a ream of dirty hacks", it really depends on how familiar you are with the tools.
ovao 3y ago
CDK itself relies on a good number of hacks and workarounds, some of which are not well-vetted at all in my experience. Some of the workarounds are really a symptom in my opinion of certain resources not being part of CloudFormation itself, when if they were, it feels like it’d be almost entirely a non-issue. It’s a little odd that at this point in the game, the prospect of “make a thing that depends on another thing” is still not an entirely solved problem within AWS.

tylergetsay 3y ago

it's also worth noting that AWS has support reps split out based on your business sector. working in education related space we have an edtech rep.

VectorLock 3y ago

Every year, managing 4000-5000 instances at least a handful of instances will fail to transition states for me. Support ticket usually clears it up.

crabbone 3y ago

> You can report bugs via your solution architect, via support, or via the Re:Post bug report tool. My solution architect? Do you realize that most AWS customers don't have an assigned solution architect? Also, yes. We did talk to our solution architect. That's the part where "what a joke" comes in. Solution architect owes you nothing. Not even an acknowledgement that the development team on the other end received the information. You will never see the ticket in any kind of a bug tracker, no indication that any work on your problem has been done. Like I said, zilch. Support in AWS doesn't exist. That is not a thing. There's support of financial issues. There's no such thing as tech support in AWS. Re:Post is dead. Nobody ever replies there. No developer within AWS has a duty to look into that board. It looks like it's mostly intended for customers to help each other out. It's more like a place you can go to vent, if you feel very frustrated. Nobody owes you any follow up, nobody notifies you if things are fixed. It's not a substitute for bug tracker or customer support.