Skip to content

Commit 96fc43b

Browse files
committed
Add CTAs to new blog posts
1 parent 631ec7d commit 96fc43b

File tree

7 files changed

+60
-56
lines changed

7 files changed

+60
-56
lines changed

package-lock.json

Lines changed: 45 additions & 45 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
-1.08 KB
Loading
-1.43 KB
Loading
-31.6 KB
Loading

src/assets/blog/mountaineering.jpg

-11.5 KB
Loading

src/content/blog/claude-code-using-aws-bedrock.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ and
9595

9696
## Attach the Policy
9797

98-
A policy on its own does nothing, you need to attach it to the identity that
98+
A policy on its own does nothing; you need to attach it to the identity that
9999
developers use to authenticate.
100100

101101
**If you use AWS SSO (recommended)**, attach the policy to your SSO permission
@@ -343,3 +343,6 @@ for setup instructions.
343343
- [AWS Service Quotas](https://docs.aws.amazon.com/servicequotas/latest/userguide/request-quota-increase.html)
344344
- [Claude for Enterprise on AWS Marketplace](https://aws.amazon.com/blogs/awsmarketplace/claude-for-enterprise-premium-seats-with-claude-code-now-available-in-aws-marketplace/)
345345
- [No Account Left Behind: Automating Cross-Account Observability in AWS](/en/blog/no-account-left-behind)
346+
347+
**Interested in running your own Claude Code?** Check out our
348+
[Pragmatic AI Adoption](https://bespinian.io/en/services/pragmatic-ai-adoption?utm_source=bespinian_blog&utm_medium=blog&utm_campaign=claude_code_using_aws_bedrock).

src/content/blog/cloud-migration-ascent.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ image: ../../assets/blog/mountaineering.jpg
1919

2020
# Cloud Migration: What Mountains Can Teach Us About Digital Transformation
2121

22-
When I started my adventure with mountaineering, I've learned that reaching the
22+
When I started my adventure with mountaineering, I learned that reaching the
2323
summit isn't about strength and technical details alone—it's about preparation,
2424
mindset, strategy, and the right team. The same is true for cloud migration.
2525
It’s crucial to split the work into phases, plan carefully, face changing
@@ -30,7 +30,7 @@ Those that approach it like an expedition—with careful planning, staged
3030
progress, and expert guidance—reach their goals successfully and succeed in a
3131
cloud environment.
3232

33-
## Preparation and planning
33+
## Preparation and Planning
3434

3535
Every successful expedition starts with a detailed plan. Your cloud migration
3636
should too:
@@ -45,12 +45,12 @@ should too:
4545
to be done Will you lift-and-shift for speed, re-platform for optimization, or
4646
refactor for maximum cloud-native benefits?
4747

48-
## Start the ascent
48+
## Start the Ascent
4949

5050
Mountaineers ascend gradually, allowing time to adapt. Apply the same approach
5151
to your migration:
5252

53-
- **Migrate incrementally** - Move non-critical workloads first to build
53+
- **Migrate incrementally** - Move noncritical workloads first to build
5454
confidence and learn the terrain
5555
- **Run parallel systems** - During the transition state, run the workloads in
5656
hybrid mode, gradually turning into cloud to minimize risks
@@ -60,7 +60,7 @@ to your migration:
6060
## Acclimatize to Your New Environment
6161

6262
Reaching altitude isn't enough—you need time to rest and adapt. In mountains, we
63-
need to optimize how our body reacts for less oxygen. With migration, we need to
63+
need to optimize how our body reacts to less oxygen. With migration, we need to
6464
adapt to the new cloud environment. Once your first workloads are in the cloud,
6565
it’s time to optimize.
6666

@@ -69,7 +69,7 @@ it’s time to optimize.
6969
Revise your services and their possibilities.
7070
- **Strengthen security** - Used to have everything locked in your on-premise
7171
world, you have to realize what threats await you in the cloud world. But
72-
there is nothing to worry about, with the implementation of best practices,
72+
there is nothing to worry about with the implementation of best practices,
7373
cloud-specific security controls and compliance measures you can reach the
7474
secure environment.
7575
- **Control costs** - We can just move everything to the cloud and make it work,
@@ -82,16 +82,16 @@ it’s time to optimize.
8282
The summit push requires focus. This migration step also requires special
8383
attention to details and can bring new challenges.
8484

85-
- **Build resilience** - Your services are overall stable, however we need to
85+
- **Build resilience** - Your services are overall stable; however, we need to
8686
prepare for surprises like, for example, service downtime. Make sure you align
8787
with redundancy strategies and keep your resources highly available.
8888
- **Monitoring and scaling** - Real-time visibility into performance and costs
89-
is essential for your success as well as scalable archotecture.
89+
is essential for your success as well as scalable architecture.
9090
- **Continuously refine** - to gain as much benefit from your migration as
9191
possible, refine regularly your cloud environment and explore deeper the
9292
possibilities the cloud gives you.
9393

94-
## Enjoy the views!
94+
## Enjoy the Views!
9595

9696
After months of hard work, you finally reached your goal and are standing on the
9797
top of a high mountain with your head in the clouds. The feeling of great
@@ -102,4 +102,5 @@ scalability, and reduced infrastructure overhead. But these benefits require
102102
commitment to the journey—not just reaching the cloud, but optimizing
103103
continuously once there.
104104

105-
**Are you ready to begin your cloud expedition?**
105+
**Are you ready to begin your cloud expedition?** Check out our
106+
[Cloud Native Empowerment](https://bespinian.io/en/services/cloud-native-empowerment?utm_source=bespinian_blog&utm_medium=blog&utm_campaign=cloud_migration_ascent).

0 commit comments

Comments
 (0)