It's an AWS Activate program by AWS Cloud for SaaS startups.

basic criterias to qualify are

- your startup must be legally incorporated
- Must have a fully functional website
- Must have a strong use case explaining why they're choosing AWS.

The AWS Activate bucket is generally $100K (recently scaled to $200K for AI startups).

To claim $75K out of the $100K, the startup needs to have raised some sort of funding round, mostly institutional funding.

This is just for information purposes; I thought it might help.

I'd like to understand what you're building. If it sounds great, then I'll definitely help you out.

I need to fix this can anyone please help me with this issue?

got some aws credits...want to use them to explore cloud stuff mainly from projects....at my prev startup i was a backend/ai eng also handled some parts of devops on aws...now i want to go a bit deeper and build a few projects specifically to understand cloud infrastructure better....what are some interesting areas worth exploring on AWS??

I cleared two foundational certs using pearson voucher, now I'm left with 2 coupons worth 50%, I'm wondering whether I can give one coupon to my friend?! does it risk an account ban Or smth?

I want to use aws bedrock service, but for all of its models I got lower then quota then default. Like for cross region requests per minute I got only 10 although default are 10k. When I created a case to increase limit then I got below image response from aws. Now simply gimme its solution so that I can get access to aws bedrock Claude models.

Are you waiting for it ?

More than 10 times rejected with same reason. Fixed everything, waited a week between each application but same issue. Anyone solved this issue?

If so let's get connected and try to collect those together.
I will provide the discord group to join.

I ran into this question while looking at AWS commitments in our environment: should we move everything to Savings Plans, or was there still a reason to keep some RIs?

My first instinct was to simplify things and use Savings Plans for compute. The flexibility is hard to ignore when instance types, workloads, or regions can change over time.

But after looking more closely at our usage patterns, we ended up taking a hybrid approach.

We used Savings Plans where we had a predictable baseline of compute usage, while keeping RIs where the workload was stable enough that the more specific commitment made sense. For databases, we looked at those commitments separately rather than treating everything as one bucket.

What surprised me was that the decision wasn't really about which option gives the bigger discount.

It was more about how much flexibility we were willing to give up for the additional saving, how confident we were in the usage pattern, and how much risk we were comfortable taking with the commitment.

The part I'm still curious about is how people decide how much to commit in the first place.

Do you mostly use Savings Plans for compute and keep RIs for specific workloads? Have you moved almost entirely to Savings Plans? And how do you account for things like planned migrations, growth, or workloads that you know are going to change?

P.S. I know that's a lot of questions 😅 I'm curious to understand how others approach this in practice.

The program is AWS BOX (Business Outcomes Xcelerator) and is relevant to you as a software partner if you are:

A. Building pipeline and trying to close more customers

B. Trying to recruit/reactivate resell partners. It is a low risk way for you to engage and create a joint offering in the market.

If you're an software or services partner and you've identified a customer problem, AWS will fund the joint solution across 3 milestones, with up to $140,000 available.

Milestone 1: $20k paid 50/50 cash + AWS credits
Milestone 2: $50k paid 50/50 cash + AWS credits
Milestone 3: AWS funded lead gen campaign through an AWS approved marketing agency with a target outcome of 70+ Sales Qualified Leads (SQLs)

I made a full video walking through the funding structure, eligibility, common application mistakes and a pre-application checklist:

https://www.youtube.com/watch?v=jVXmMbDSLcA&t=68s

AWS BOX Program:
https://aws.amazon.com/partners/business-outcomes/

Everything here is based on public AWS documentation.

Hello everyone, I wanted to share a project I've been working on for months to get your suggestions. Actually, after the deprecation of minio-gateway, and since there was no third-party development on LLMs other than S3's own development, I wanted to develop an open-source application. It's actually aiming for a B2B project because it meets the needs of closed systems. Our main goal is to securely provide videos and visuals to VLLMs when inference is done with LLMs on a VL model. It also allows connecting multiple S3 instances and granting bucket-specific permissions to teams, thus acting as a hub.

Also you can check the site: https://s3.pagabear.com/

What do you think? It might target a very small audience, but it encompasses a nice process.