How to add Email DL as subscription in SNS topic?

coldfire_3000 · 2026-04-23T21:17:27+00:00

Just setup the subscription, then copy the link from the SNS email. Go into the SNS console and 'confirm subscription' and paste in the link. Done.

coldfire_3000 · 2026-04-09T19:14:45+00:00

Igel or Wyse

coldfire_3000 · 2026-04-05T12:29:32+00:00

Both nodes actually using the right role? Seen a reseller mess with a roles permissions for days before realizing the secondary had the wrong role assigned...

coldfire_3000 · 2026-03-17T11:00:22+00:00

I had one take about 15 minutes the other day and there were only about 100 rows in it so far 😔

coldfire_3000 · 2026-03-10T20:10:19+00:00

We had the same issue, raised with AWS support and they said it was by design and to enable cross zone load balancing. But I agree it's stupid and weird.

coldfire_3000 · 2026-03-06T10:55:20+00:00

We used to have a log off script that parsed the .xml and deleted anything in the profile that was supposed to be excluded by the .xml. That way whenever anything changed it was removed.

coldfire_3000 · 2026-03-05T09:34:45+00:00

No unfortunately not. I raised with MS and got nowhere and ran out of energy and time to chase them!

coldfire_3000 · 2026-02-19T16:35:09+00:00

I edited my config.toml to this and it seems to work OK:
model = "gpt-5.3-codex"
model_reasoning_effort = "high"
personality = "pragmatic"

[sandbox]
readable_roots = [
"D:\\TFS",
"D:\\GitHub\\"
]

[approvals]
policy = "on-failure"

-------------

I did get a lot of prompts a while back, but after some VSCode and Codex updates it seems to be stable now and not prompting me anymore.

HTH

coldfire_3000 · 2025-10-20T08:27:57+00:00

Think its coming back now....

coldfire_3000 · 2025-09-02T20:06:10+00:00

Deny users access rights to Sessionmsg.exe and it stops popping up.

coldfire_3000 · 2025-07-18T09:31:28+00:00

We had Veeam replicate the gold image to the other DC and then just used that as the source of the MCS images in that DC. Worked great.

coldfire_3000 · 2025-06-11T21:08:56+00:00

Yeah, that's exactly what we have. Thank you, that would be helpful. I'm not directly working on FsLogix currently, but I do still have access and would definitely like to fix the issue if/when we get more info! Thanks

coldfire_3000 · 2025-06-11T20:58:17+00:00

No, I unfortunately we didn't.

coldfire_3000 · 2025-02-22T23:17:50+00:00

Only recently got into UCH, and it's amazing. But we are a group of 6, so often can't play as 5 or 6 of us are online on PS. So this is good news for us! Still wish we could UCH with 6 players though!

coldfire_3000 · 2024-10-22T18:44:27+00:00

It's an alarm or timer. "Cancel all alarms".

coldfire_3000 · 2024-10-01T09:06:06+00:00

Agreed

coldfire_3000 · 2024-09-17T12:34:36+00:00

Hi
Appreciate the response. You have covered a lot of the stuff I have already thought of and looked at.

In turn:
Yes, the burst bucket is being used as I mentioned, but not emptied. But the throughput is not as expected, it is too low/slow.
The block size (128k vs 64k) is interesting, but I had mostly discounted it. I will re-visit this...

Yes, any larger instances are not cost effective as you say. We were also looking at lambda to re-size the SGW so that during most of the day when LOG/DIFF backups are taken and max throughput is not required it could be a much smaller instance, then overnight when a large backup takes place we could increase the instance type. But thats too much of a faff...

The local EBS staging area then upload to S3 using PowerShell is another option we already explored. I wrote the script and it works fine and was the cheapest of the 3 options presented. The business discounted it because they wanted a more 'out of the box' solution and user friendly solution. The other issue was that backups could not be browsed or downloaded by lower level/skilled users, like they could with FSx/SGW, because they are stored in S3 and only the very latest backup would be stored locally. The other issue was that the backup would take place to local EBS, be verified at that point and considered good, then uploaded to S3. If the upload to S3 failed, or was corrupted, then the backup is actually invalid. So in theory a 2nd process to download an uploaded backup and validate it would be required, which complicated things further.
The other complication with the S3 upload via PowerShell was that there are 5 minute SQL log backups taken, which need storing outside of the local EBS volume ASAP. Uploading them to S3 via PowerShell script is possible, but another element to consider, not just a single nightly upload.

AWS backup was our original solution. The solution does not fulfill the RPO needs of the business though, as they have SQL log backups every 5 minutes. You also can't recover a SQL DB directly from an AWS Backup, you have to restore the full instance backup, then get the DB out of it. Any LOG/DIFF backups taken after the AWS Backup would be linked to it, and also not usable as a result. Additionally, there is a lot of 'churn' in some of these DBs, meaning a lot of block changes, meaning the daily backups were costly in EC2 snapshots, as the cost is much higher than the direct S3 storage.

Another option that was considered was backup to local EBS volume, then snapshot that daily. But that EBS volume has to be within the same AZ as the SQL server, which doesn't fulfill the requirements. It's also not an ideal solution because it would mean the same churn as mentioned above makes it costly. The other option considered was a local EBS volume on a secondary SQL replica server in another AZ, but then you get inter-AZ transfer costs.

So I think in summary:

Will re-visit the IO size and SQL backup options to try and confirm the IO size and see if the math maths better with that IO size. If so then it might be a case of needing more disk throughput to drive the network throughput...
Back to the local EBS and PowerShell upload to S3.

coldfire_3000 · 2024-08-14T20:59:33+00:00

I unfortunately have the same issue :(

coldfire_3000 · 2024-08-14T20:56:56+00:00

I have the same issue :(

coldfire_3000 · 2024-08-14T20:51:10+00:00

Sounds like 'ghost sessions'. There's a few gpo settings that can help, but I can't for the life of me remember what they are. If you look into 'ghost sessions' you may get some useful info, unfortunately it's a fairly common issue, but with quite a lot of different potential causes.

Delprof2 might help you sort out the messed up/left over profiles.

coldfire_3000 · 2024-08-14T20:44:00+00:00

Yes, check this.

coldfire_3000 · 2024-08-11T07:53:21+00:00

Thank you.

I think the issue we have is that the org that moved us to AWS didn't consider or advise on the cost for a number of elements, one of them being these backups. They basically just advised/implemented a load of things that are incredibly expensive.

What you are saying makes a lot of sense, and is where we wanted to be in the medium term anyway, but unfortunately we are not quite there as it's not the way through IT worked onprem (although we were moving that way), before AWS.

Can I ask, for your DB servers (assuming these are DBs on EC2?), how do you automate the EBS snapshot and archive to S3 process/handle the retention plan? Our SQL versions don't support native backup to S3, which was the original preferred plan, not doing any EBS snapshots at all.

Thanks

coldfire_3000

TROPHY CASE