DEV Community: Rebase

How to Release Unused Elastic IPs on AWS with One Prompt

Mubbashir Mustafa — Mon, 21 Jul 2025 21:10:10 +0000

👉🏽 Try Rebase for free, no credit card needed

If you have used AWS, you know about Elastic IPs. These are public IPs you can stick to your EC2 instances, load balancers, or NAT gateways. They let you keep the same public IP, even if you stop and start your resources. This comes in handy if you want to keep your DNS or firewall rules simple.

The thing is, Elastic IPs are not free if you leave them unused. AWS will charge you for any Elastic IP that is not attached to a running resource. If you forget to clean up, your bill goes up for no good reason. Removing unused IPs is one of those things people put off, especially if you have a bunch of them across different regions.

With Rebase, you do not have to mess around in the console or write a script for it. You just give it a prompt and it handles everything for you. Here is how it looks in action.

First, just ask the agent to show you the VPCs and Elastic IPs you have.

Now, ask the agent to release all the unassociated Elastic IPs.

That is all it takes.

You can check in the AWS Console to confirm they are gone.

How to Set Up AWS VPC Peering for Private Connectivity - Effortlessly

Mubbashir Mustafa — Fri, 18 Jul 2025 13:44:18 +0000

👉🏽 Try Rebase for free, no credit card needed

If you work with multiple VPCs in AWS, sooner or later you’ll want them to talk to each other. Sometimes you split workloads into different VPCs to keep things separate, or your team is working across different AWS accounts. AWS lets you connect those VPCs with something called VPC peering. That way, the traffic stays private, never hitting the public internet. But if you’ve ever tried to set this up by hand, you know it can be a hassle. You have to make sure the CIDR blocks do not overlap, the route tables are right, and both sides accept the connection. Missing one step means your setup just doesn’t work.

With Rebase, you can do all of this just by telling the agent what you want. Here’s how it works from start to finish.

We’ll start by spinning up two VPCs, both with private subnets and non-overlapping CIDR blocks. This is important, because VPC peering won’t work if the address ranges clash.

The AI agent will put together a plan and show you exactly what it’s about to do. If it needs more info, it’ll ask before moving ahead.

Once you answer, the agent finalizes the plan for you.

The agent asks for a quick confirmation to make sure everything looks right.

After you confirm, the agent goes ahead and provisions everything.

When it’s done, you’ll get a summary of everything it created. You can see all the details here.

Now grab those VPC and subnet IDs. Let’s try connecting to an EC2 instance in one of these VPCs using AWS SSM (Session Manager).

When you tell the agent you want to access EC2 via SSM, it will ask for confirmation and take care of the setup.

After it’s done, it will let you know that everything is set up and ready.

You’ll see the exact commands you need to connect through AWS SSM.

If you hit any errors, just tell the agent and it will troubleshoot and fix things for you.

It’ll walk you through any follow-up steps if you need more help.

Now, grab the private IPs of both instances in each VPC. You’ll need them for the next step.

If you’re not sure how to test the setup, just ask the agent and it’ll help out.

When you log in with SSM and try to ping the other instance from the first one, it won’t work yet. That’s because VPC peering isn’t enabled.

Now, let the agent know you want to enable VPC peering. It will handle everything needed for that.

The agent figures out all the steps, including updating route tables, so traffic can flow between the VPCs.

If there’s anything else needed, the agent will suggest it and ask for your go-ahead.

When it’s all done, you’ll get a summary of what was changed.

If you want to double-check, you can confirm everything from the AWS console.

Here’s the VPCs:

And here’s the EC2 instances:

Now, if you try pinging from one EC2 instance to the other over their private IPs, it works. You’re all set.

That’s it. VPC peering, start to finish, without having to mess with the AWS console or memorize all the steps.

How to Set Up a VPC with Public and Private Subnets, Multi-AZ, IGW, and NAT Gateway on AWS in Seconds

Mubbashir Mustafa — Mon, 14 Jul 2025 22:21:50 +0000

👉🏽 Try Rebase for free, no credit card needed

Every app on AWS needs a network setup that just works. You want your web servers out in the open, but your databases safe and locked away. That’s why people set up a VPC with both public and private subnets, spread across a few zones, with the right gateways so traffic moves how it should.

Setting this up in AWS is harder than it sounds. You miss one step, pick the wrong subnet, or forget a route, and things break. Your servers might not talk to the internet, or worse, you end up exposing your database.

Rebase makes this part easy. Instead of clicking through AWS or messing with templates, you just say what you want, and Rebase handles the rest. Here’s what it looks like.

Once you’re logged in and done with onboarding, you’ll land on the homepage.

We have a few prompts ready to go, and we’re adding more. If you pick “VPC with public and private subnets”, the prompt fills in for you.

The agent will check with you before doing anything.

If you want something specific, just say so. You can mention a CIDR block or any detail you care about. If you want Rebase to figure it out, just leave it to the agent.

Rebase will share what it plans to do and will ask you to approve it.

Once you give the green light, it gets started.

For every action that changes something, Rebase will always ask you first. You get three options:

Yes: Proceed
No: Cancel
Feedback: Tell the agent to change something or do it differently. For example, you might say, actually use just one AZ.

You can turn off these permission checks anytime from the workspace settings.

Rebase will build out everything, and if it hits something new, it will check with you first.

When it’s done, you’ll see a summary of what the agent did, step by step.

That’s it. The stuff that usually eats up hours or days, Rebase does it for you in a few seconds.

You can always double check in AWS to see everything is there.

The tags are there too, just like you asked for.

You can also ask Rebase what this setup is going to cost you every month. The agent will break down all the main parts that AWS charges for, show you what’s free, and give you a ballpark number. You can even get a detailed estimate based on how much traffic or data you expect.

This is useful if you’re trying to keep your AWS bill in check or just want to know what to expect before you hit deploy.