Managed Cloud Operations · Professional Services

CloudOps & ITSM
AWS Operations,
Run Through Your Tickets

BSG engineers take on your day-to-day AWS operations — changes, incidents, security response, and monitoring — through a ticket workflow you approve and can audit. Add-ons cover Terraform Cloud environments, after-hours P1 response, and audit support.

Request a private offer on AWS Marketplace — BSG reviews your environment with you and sends the final offer.

Changes Only After Approval

Work is estimated on the ticket first; anything over 4 hours starts only after you approve.

P1 Response from 15 min

From 1 hour down to 15 minutes in support hours; 1 hour after hours with the on-call add-on.

Every Hour on Record

Every request, approval, and hour logged on a ticket, with a monthly report.

Why Cloud Operations Break Down

Running AWS day to day takes people, a process, and a record of what was done.

No Dedicated Cloud Operations Team

Hiring and keeping cloud engineers is slow and expensive. Changes and incidents land on whoever is available, and knowledge leaves when they do.

Changes Made Without a Record

When infrastructure is changed by hand without a ticket, nobody can say later who changed what, why, or who approved it.

Hard to See Where the Time Goes

Without effort recorded per request, it is hard to tell what operations work was done each month and what it cost.

Audit Evidence Rebuilt Every Time

When changes aren’t recorded as they happen, every audit means reconstructing the history after the fact.

An Operations Team You Can Approve and Audit

BSG has operated AWS for customers as an AWS Advanced Partner since 2015. This service puts our cloud engineers on your environment, sized to your workload.

CloudOps

Day-to-Day AWS Operations

Engineers who handle the work your team doesn’t have time for.

  • Configuration changes, provisioning, scaling
  • First-line incident analysis and recovery
  • Security response: log investigation, IP blocking, patching, GuardDuty & CloudTrail event analysis
  • Monitoring and alert tuning, runbooks
ITSM

A Workflow on Your Own Tool

Every request runs through a process BSG sets up on your ticketing system.

  • Request intake, approval, change, incident flows
  • Estimate before work; your approval over 4 hours
  • Actual effort logged per ticket
  • Monthly report, including a security event summary
Add-ons

IaC, After-Hours P1, Audits

Added to any model when you need them.

  • IaC Operations for Terraform Cloud environments
  • 24/365 on-call: after-hours P1 response within 1 hour
  • Audit support, per audit: evidence, answers, on-site

AWS services covered

Amazon EC2Amazon VPCAmazon EKSAmazon RDSAmazon S3AWS IAMAWS CloudTrailAmazon GuardDutyAmazon CloudWatchAWS Systems Manager

A Risky Request, Handled by People Who Ask First

Your team asks for something that would open a hole. A console-based operator would just click it through. A BSG engineer asks what you actually need, explains the risk in plain words, writes the safer change as code for a second engineer to review — and waits for your approval.

In your own ITSM toolPeer review in GitHubCheckov as a safety net
CLOUD-1042 · Service deskPR #218 · infra-prod
servicedesk.your-company.com/browse/CLOUD-1042
Service Desk Your work ▾Projects ▾Filters ▾Dashboards ▾ Create Search 2 JP

Projects / Cloud Operations / CLOUD-1042

Open SSH for vendor maintenance on Wednesday

📎 Attach🔗 Link issue···
JP
Waiting for approvalApprover: Jiwon Park (Infrastructure owner)
✓ ApproveDecline

Description

Our vendor needs to patch the order system on Wednesday. Can you open SSH (port 22) so they can connect?

Activity

AllCommentsHistoryWork logOldest first ▾
JPAdd internal note / Reply to customer
Open ▾

Details

Assignee?Unassigned
ReporterJPJiwon Park
Request typeChange · Network access
PriorityMedium

Development

PR #218 · infra-prodOpen
ChecksRunning
Terraform Cloud apply · prodSuccessful

Time tracking

No time logged
your-company / infra-prod

CLOUD-1042: vendor SSH from 203.0.113.24, Wed 10–14 #218

⇄ Openminho-bsg wants to merge 1 commit into main from cloud-1042
ConversationCommits 1ChecksFiles changed 1
modules/network/sg_app.tf
41 resource "aws_security_group_rule" "vendor_ssh" {
42+ description = "Vendor patch (CLOUD-1042)"
43+ type = "ingress"
44+ from_port = 22
45+ to_port = 22
46+ cidr_blocks = ["203.0.113.24/32"]
SK

sora-bsg · Senior engineer

IP and port look right. Let’s also schedule the removal so it closes at 14:00 even if nobody remembers.

ML

minho-bsg

Good call — removal is scheduled as PR #219 for Wed 14:00.

47+ security_group_id = aws_security_group.app.id
48 }
Some checks haven’t completed yet
✓Terraform Cloud / infra-prodPlanned: 1 to add
•Checkov / terraformIn progress…
✓ CKV_AWS_24 · SSH not open to 0.0.0.0/0
•Review: sora-bsgRequested
•ITSM / change approvalWaiting for CLOUD-1042
Waiting for review and approvalA peer review and the customer’s change approval are required.
Merge pull request
✓

Example tools: an ITSM service desk, GitHub, and Checkov. Sample project and data; times are compressed.

1

Your Terraform Cloud Workflow

Changes go through the workflow in your Terraform Cloud: pull request, plan, then apply.

2

Drift Brought Back Into Code

When Terraform Cloud detects drift, BSG responds and brings console changes back into the code.

3

Code and Policies Maintained

Existing code and modules are maintained, and policy sets (Sentinel or OPA) are managed.

4

Estimate and Approval First

Planned effort is posted on the ticket; work over 4 hours starts only after your approval.

IaC Operations is an add-on

For environments you run on Terraform Cloud. The TFC license is yours, and code changes count against your contracted hours. Without the add-on, BSG works through the console only. Not on Terraform yet? Introducing IaC is contracted separately.

IaC-based Cloud Security Consulting →

When Production Breaks at 2 p.m.

Your on-duty contact raises a P1 incident in your ITSM tool. Your engineer responds within the agreed target, keeps you updated in plain words, asks before rolling anything back, and explains afterwards what happened and how it won’t happen again.

In your own ITSM toolP1 raised by your teamDedicated model · 15-min P1 target
CLOUD-1050 · Service desk
servicedesk.your-company.com/browse/CLOUD-1050
Service Desk Your work ▾Projects ▾Filters ▾Dashboards ▾ Create Search 2 JP

Projects / Cloud Operations / CLOUD-1050

Checkout failing for customers — P1

📎 Attach🔗 Link issue···
JP
Waiting for approvalApprover: Jiwon Park (Infrastructure owner)
✓ ApproveDecline

Description

Customers have been reporting payment errors since about 14:00, and our 5XX alarm on the order load balancer is firing.

HTTPCode_ELB_5XX rate · orders-alb · last 1 hour

5%

Activity

AllCommentsHistoryWork logOldest first ▾
JPAdd internal note / Reply to customer
Open ▾

Details

Assignee?Unassigned
ReporterJPJiwon Park
Request typeIncident
PriorityHighest

SLAs

Time to first response15m left
Time to resolution4h left

Time tracking

No time logged
✓

Shown in an example ITSM service desk. Sample project and data; times are compressed. P1 targets: 1 hour (Shared), 30 minutes (Semi-dedicated), 15 minutes (Dedicated), within support hours. After hours: 1 hour with the on-call add-on.

Audit Support

For each audit or inspection — ISMS-P, Korea’s Electronic Financial Supervisory Regulation, and similar — a standard 32-hour package, separate from your operations hours.

1

Before the Audit

Evidence organized, collected, and submitted.

2

Auditor Questions

Written answers to the auditors’ questions.

3

On Site

Support during on-site review.

How Engagement Works

It starts with a private offer request on AWS Marketplace. BSG reviews your environment with you, sizes the team and hours, and sends the final private offer.

1
You · AWS Marketplace

Request a Private Offer

Send a private offer request from our AWS Marketplace listing.

2
BSG

Environment Assessment

BSG contacts you to review accounts and workloads, change and incident volume, Terraform Cloud use, and audit needs.

3
BSG → You

Proposal & Quote

Recommended engagement model, team composition, monthly hours, add-ons, and SOW.

4
AWS Marketplace

Final Private Offer

BSG sends the agreed terms as a private offer. Accepting it is your subscription.

5
BSG + You

Onboarding

Access set up with IAM roles and MFA, ITSM workflow configured, runbooks written.

6
BSG

Operate & Review

Monthly reports, and a usage review every quarter to adjust the engagement.

Why we size it with you

How many engineers, at what level, and for how many hours depends on your environment — not on a price list. The assessment gives both sides a baseline the quote is built on.

  • Number of AWS accounts, workloads, and environments
  • Monthly volume of changes, releases, and incidents
  • Required response times and after-hours coverage
  • Whether infrastructure runs on Terraform Cloud
  • Audit and compliance requirements

Engagement Models

The assessment points to one of three models. Every model covers the same scope; they differ in how engineers are assigned and how fast they respond. Hours and team are finalized in your proposal.

Shared

Pooled Team

Stable services with routine requests — permissions, alerts, periodic checks.

EngineersSenior lead + rotating team
Typical sizeFrom 20 h / month
P1 response1 hour
Other requests1 business day
ReportingMonthly report
After hoursP1 within 1 hour with on-call add-on
Dedicated

Dedicated Team

Launches, audits, or migrations — engineers who take priorities from you directly.

EngineersDedicated engineer(s) + cover
Typical sizeFull-time per engineer
P1 response15 minutes
Other requests2 hours
ReportingWeekly & monthly + weekly meeting
After hoursP1 within 1 hour with on-call add-on
Add-on · Monthly

IaC Operations

Your Terraform Cloud environment operated through its PR, plan, and apply workflow, with drift response and code and policy upkeep. Code changes count against contracted hours.

Add-on · Monthly

24/365 On-call

After-hours P1 alerts received and first response within 1 hour. Alert-based, not continuous monitoring; after-hours work counts 1.5× against hours.

Add-on · Per audit

Audit Support

A standard 32-hour package per audit: evidence, written answers, and on-site support. Separate from operations hours.

Need a 15-minute P1 response around the clock? Dedicated 24/365 shift coverage is quoted separately.

Contract terms

  • 12-month term via AWS Marketplace private offer
  • Monthly installments, or 6 / 12-month prepayment; monthly add-ons get the same discount
  • Support hours Mon–Fri 09:00–18:00 KST; after hours through the on-call add-on
  • Add-ons, hours, or tier changes through a new offer during the term

Not included — contracted separately

  • 24×7 NOC monitoring, security operations center (SOC), and breach response
  • New application development or code changes
  • Large migrations, redesigns, or first-time IaC adoption
  • AWS infrastructure and Terraform Cloud license charges

Built for Teams That Must Prove Control

Especially where a misconfiguration is a regulatory event, not just an outage.

Financial Services

  • Every change requested and approved on a ticket
  • Change history and runbooks kept current
  • Audit support for ISMS-P and financial regulation (add-on)

Enterprises Without a Cloud Ops Team

  • Experienced AWS engineers without hiring
  • Knowledge kept in runbooks, not in one person
  • Predictable monthly hours and reporting

Digital Services with Frequent Releases

  • Scaling and changes handled around launches
  • Fast first response when releases go wrong
  • Terraform code kept accurate (add-on)

Request a private offer on AWS Marketplace.

Send a request from our listing. BSG will reach out to review your environment, recommend an engagement model and team, and send the final private offer.

Available in AWS Marketplace