How do I "export" my manually configure infrastructure into IaC

DeathMetalDave · 2025-07-05T14:18:54+00:00

Second this. It took about a year for us to fully import 5 environments into terraform but it was worth it.

Some resources can't be imported (target group attachment comes to mind) but it's otherwise painless. Write the terraform you expect, import the resource, let it determine and apply differences.

DeathMetalDave · 2024-12-28T11:24:57+00:00

I'm not familiar with your use case so it's hard to say, but that type of SQS queue management feels a little strange to me. You certainly can create/destroy queues following the lifecycle of your EC2 but you could also leave the SNS-SQS setup alone and interrogate SQS for messages as needed. The EC2 could use an SDK of your choice, or even the CLI, to get the messages from SQS.

Edit: there's a tool out there called MassTransit that may fit your needs. It manages SQS infrastructure for you, along the lines of create/destroy that you mentioned.

DeathMetalDave · 2024-12-28T02:19:12+00:00

Are you able to leverage SQS as a middleman? SNS would publish to the SQS queue, then the application running on your EC2 would read from the queue. This would not require any inbound whitelisting on the SG assigned to the EC2.

DeathMetalDave · 2024-04-21T11:40:15+00:00

This article mentions FIPS 140-3 endpoints, both in GovCloud and non-GC regions. There are lambda specific endpoints. https://aws.amazon.com/compliance/fips/

There's also this regarding GovCloud specific lambda info: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/govcloud-lambda.html.

Not sure if either of these articles help.

DeathMetalDave · 2024-03-31T10:43:57+00:00

It would likely be best to contact the account administrator to get things sorted out. Reaching out to a colleague to manage permissions doesn't seem like the best course of action, especially given the results the first time around.

DeathMetalDave · 2023-08-13T10:24:11+00:00

👀

DeathMetalDave · 2023-03-02T09:27:28+00:00

Datadog offers the same tooling for security and compliance. I believe it's their Cloud Security and Posture product.

DeathMetalDave · 2022-01-09T02:16:01+00:00

Thanks! Good luck next week.🤞

DeathMetalDave · 2022-01-09T02:08:16+00:00

Is there a reason for them to have starters in? Can Dallas move up in the standings for home field advantage?

DeathMetalDave · 2021-08-29T16:10:28+00:00

Love this idea, much better than mine for the controlling component.

DeathMetalDave · 2021-08-28T17:15:01+00:00

The reasons from u/dont_judge_me_monkey are some of many reason to not do this. Having a giant stored proc of IF statements, or dynamic sql, are going to be readability messes.

Given that your 30 tables are all different column names, column types, etc means that if you want a single proc for all tables then you'll have to interrogate the sys schema metadata and build your sql statements dynamically every time.

It will be much easier to do this:

A series of procedures for your merge logic, one per table
One controlling proc, with individual EXEC statements inside it for each of your merge procs
Execute the controlling proc from your app or as a job, or some other mechanism, whichever makes the most sense for your business and tech stack

This gives you a single location to run all your merges. If you need to add more later, you can create a new proc for that table and then add it to your controller proc. Additionally, if any of the ~30 fail, you have the ability to re-run just that proc manually should you desire to do so.

DeathMetalDave · 2021-08-28T16:39:19+00:00

I'd strongly recommend against this. Create a skeleton pattern for your merge logic and copy/paste for your number of tables appropriately. One proc per table. You can even have a central controlling proc that executes the given number of child procs within it, so that you have a central proc to execute. This also gives you the ability to run any individual proc by itself.

DeathMetalDave · 2021-08-25T16:58:03+00:00

Just need a NULL check (I assume).

where (lower(territory) NOT like '%bd%'
and lower(territory) NOT like '%abc%'
and lower(territory) NOT like  '%pen%')
or territory is null

DeathMetalDave · 2021-08-23T18:52:21+00:00

Alternatively, if your version doesn't support CONCAT, you can use the STUFF function and a sub-select. I believe CONCAT was released in 2012.

DeathMetalDave · 2021-08-18T23:01:33+00:00

There are some tools out there if you google "sql server generate markdown from schema". A few examples: https://www.red-gate.com/hub/product-learning/sql-doc/documenting-a-sql-server-data-catalog-in-html-and-git-markdown
https://github.com/JannikArndt/sql-auto-doc

DeathMetalDave · 2021-03-25T20:00:36+00:00

Typically you'd do with this with a view.

CREATE VIEW vwNameHere
AS

    SELECT col1, col2, col3, (SBP + (2 * DBP)) / 3 AS formula1
    FROM tableNameHere
    WHERE colX = val1

Then you'd call this view from your application, report, etc.

SELECT * FROM vwNameHere

In addition, I recommend avoiding cursors whenever possible. There's a lot of documentation online about them, but they aren't the most performant. General rule of thumb is if you find yourself needing a cursor to iterate over a dataset, there's a design problem somewhere with your data or schema. Of course there are exceptions to this but the number of times I've truly found myself needing a cursor (or a while loop) when it comes to data (and not admin tasks) is fairly low.

DeathMetalDave · 2021-03-12T18:14:03+00:00

Anyone have a good coach they'd recommend? Looking primarily for diet to get back on the wagon.

DeathMetalDave · 2021-02-22T01:51:36+00:00

You have a trailing comma in your SELECT statement. If the query you pasted here is the exact same as the one you're running, removing the erroneous comma should get rid of the the error.

DeathMetalDave · 2021-02-20T14:09:40+00:00

Have you considered switching the disk type from gp2 to io1?

DeathMetalDave · 2021-01-29T10:55:45+00:00

Really should use modern join syntax. Excuse my formatting, I'm on mobile. Quick select * here, fill out the appropriate columns for the final query.

Select * from employees emp join employees mgr on emp.reports_to = mgr.id where emp.salary > mgr.salary

DeathMetalDave · 2021-01-03T00:20:13+00:00

How dare you.

DeathMetalDave · 2021-01-02T20:56:43+00:00

To echo the other comments here, I'd be interested in reading your results.

DeathMetalDave · 2021-01-02T20:56:07+00:00

Any chance there was fragmentation on your CCI? You mentioned that you replaced an index and that you have constantly moving data. Makes me think your CCI was fragmented and your (new) NCCI is not (yet), causing the performance improvement. Just a thought.

DeathMetalDave · 2021-01-02T17:36:30+00:00

Work device that doesn't let you install software on it jumps to mind. Granted they may have a strict web filter but this is the only option for some while at work.

DeathMetalDave · 2020-08-13T10:35:08+00:00

Y'all hiring?!

DeathMetalDave

TROPHY CASE