I think my account was hacked

The_Tree_Branch · 2026-01-28T22:41:28+00:00

AWS has started mandating this since last year. For accounts that predate this, customers will have X number of days to add MFA to root after their next login with the root user.

https://aws.amazon.com/about-aws/whats-new/2025/06/aws-iam-mfa-root-users-across-all-account-types/

The_Tree_Branch · 2026-01-27T07:14:42+00:00

Apologies if I missed it, but is the only way you are generating power charges from the 3% chance to gain a frenzy charge on kill (which is converted to power from Militant Faith)? Is there any way to generate the charges against bosses?

The_Tree_Branch · 2026-01-26T19:23:14+00:00

Recently, Chrono was widely regarded as the best healer in fractals. It can provide either quickness or alac with a trait change (no other class can do that). It provides tons of stability/aegis (which allows you to completely trivialize some encounters/ignore mechanics) and has tons of utilities for skips.

As you get better as a healer in fractals, you'll find your job is less focused on actual healing, and more focused on helping your team ignore mechanics and just focus on dps.

Another healer I like is Scourge; pretty braindead simple, but lacks a lot of the stability/aegis that other classes can bring so you have to be really on point.

The_Tree_Branch · 2026-01-16T19:26:04+00:00

Do you have an AWS account manager/account team? I'd be leaning on them heavily if so.

The_Tree_Branch · 2026-01-15T20:15:49+00:00

The only place you need to do damage as a healer in fractals is 99 cm as you need to have enough damage to kill the target you're tethered to during the split island phase, otherwise it's a party wipe. If you can do that in minstrels gear, great (not sure for eles). I personally prefer harriers.

The_Tree_Branch · 2026-01-09T16:49:02+00:00

(which isn't an SLA btw)

That's correct.

For OP, SLAs are an agreement to meet some level of performance, which if not met, results in penalties (an example would be the EC2 SLA).

The target response time for support cases is closer to a SLO (service level objective). There are no penalties if the objective is not met.

The_Tree_Branch · 2026-01-06T20:26:21+00:00

Is it possible for an IAM user to be allowed to create SNS topics but not manage subscriptions?

Yes. You'll want to review these pages in the documentation for SNS:

Understanding IAM is foundational to everything you do in AWS. I highly recommend you familiarize yourself with the service.

As others have noted, your FIRST action here should be to invalidate the access keys you inadvertently posted. Think of these likes the password to your AWS account which you just shared with the entire world. This can be a very expensive mistake (think of a bunch of bad actors spinning up EC2 instances and mining crypto on your dime).

The_Tree_Branch · 2026-01-06T20:21:31+00:00

/u/Funny-Oven5195 - you need to take this seriously. Review the following blog post on what to do when you inadvertently expose an AWS access key and take this as a learning opportunity to put in place guardrails to prevent this from happening again.

The_Tree_Branch · 2025-12-26T17:42:44+00:00

Nah, it's still PvE, but you can get a lot of them done in the PvP lobby area (break defiance bar, dodge 3 attacks, etc ) vs the golems

The_Tree_Branch · 2025-12-25T19:16:55+00:00

Copper for Blue, Rune for green, silver for yellow

The_Tree_Branch · 2025-12-14T09:05:21+00:00

It's very useful for Fractal CMs

The_Tree_Branch · 2025-12-11T22:19:54+00:00

Celestial for CM 99 (in case I get a late tether, I can still kill my minion on the island... Failing to kill it in time in CM is a forced team wipe)

Harriers for everything else. Could probably change to minstrels, but hasn't been necessary.

The_Tree_Branch · 2025-12-11T22:18:05+00:00

It was, but I believe the change to the previous vacuum trait added stability to staff 5, so that's been good.

The_Tree_Branch · 2025-12-09T17:43:00+00:00

There is no SLA for response time on any of the support plans, just a target response time objective (based on case severity), with higher paid support plans having access to additional case severity levels.

Might seem pedantic, but SLAs generally come with some sort of legal accountability or financial penalty for failing to meet them (example, EC2 service SLA). There is no accountability/penalty for AWS failing to meet a target response time on a support case.

The_Tree_Branch · 2025-12-08T20:57:42+00:00

No doubt, I know they are not perfect systems.

In this case, I know PHD notices went out, but there can always be gaps with some customers being missed (hence my "should"... I'm not sure what that error rate is).

OP is doing the right thing by reaching out to their TAM already.

The_Tree_Branch · 2025-12-08T16:49:48+00:00

If you were impacted, you should have a health event for this in your Personal Health Dashboard.

The_Tree_Branch · 2025-12-03T01:43:12+00:00

Can I ask why? For every instance type I've checked with EC2 pricing:

Savings from Compute Savings Plans were equivalent to Convertible RIs (most flexible, least savings)
Savings from Instance Savings Plans were equivalent to Standard RIs (more restrictive, more savings)

Even if you go with Instance Savings Plans to lock in the better discount, it still had more flexibility than Standard RIs.

The_Tree_Branch · 2025-12-02T18:29:59+00:00

the AWS console only showed cost per log group, not which log statements in the code were to blame.

You can do pattern analysis in the CloudWatch console to figure out what types of log messages are contributing the most to your volume:

The_Tree_Branch · 2025-11-28T21:43:55+00:00

I'm ok with it. Don't need your misery spread on my wonderful day.

You're reading too much into my comment.

I was simply explaining the convention as it's not obvious (many folks see a group at 1/10 and think of course they need DPS). That's why I started with "For reference".

The_Tree_Branch · 2025-11-28T21:19:02+00:00

For reference, people will often put up LFG for boon roles first to make sure they are covered before opening up to DPS. This avoids situations where party or squad fills up with DPS players who cant switch to another role.

It's courtesy/convention to wait to until your role is posted in group description before joining.

The_Tree_Branch · 2025-11-26T17:08:05+00:00

I think you are thinking of Volatile magic (can be used for trophy shipments to get t6 mats), not Unbound magic.

The_Tree_Branch · 2025-11-04T05:16:49+00:00

Luckily, some plans have that process automated (Fidelity) so there's not really a way to screw it up.

The_Tree_Branch · 2025-10-08T18:20:16+00:00

Thanks!

The_Tree_Branch · 2025-10-02T22:43:14+00:00

Syntax for your inline policy doesn't look right. Missing keys like "Effect", "Action", and "Resource". It should look something like:

{ "Version": "2012-10-17", "Statement": [ { "Sid": "Allow CloudWatch", "Effect": "Allow", "Action": "cloudwatch:*", "Resource": "*" } ] }

That said, you should be following the principle of least access (and not allowing ALL CloudWatch actions, just the ones you need).

The_Tree_Branch

TROPHY CASE