REST API creation in AWS - Step-by-Step Execution

Process Flow - REST API creation

Define API Gateway REST API

↓

Create Resources (paths)

↓

Define Methods (GET, POST, etc.)

↓

Integrate Methods with Backend (Lambda, HTTP)

↓

Deploy API to Stage

↓

API is Ready to Receive Requests

This flow shows the steps to create a REST API using AWS API Gateway: define the API, add paths, set methods, connect to backend, deploy, then use.

Execution Sample

AWS

aws apigateway create-rest-api --name MyAPI
aws apigateway create-resource --rest-api-id <id> --parent-id <root> --path-part users
aws apigateway put-method --rest-api-id <id> --resource-id <users> --http-method GET --authorization-type NONE
aws apigateway put-integration --rest-api-id <id> --resource-id <users> --http-method GET --type MOCK
aws apigateway create-deployment --rest-api-id <id> --stage-name prod

This sequence creates a REST API named MyAPI with a /users GET method using a mock integration, then deploys it to the prod stage.

Process Table

Step	Action	Input	Result	Notes
1	Create REST API	Name=MyAPI	API ID=abc123	API created with unique ID
2	Create Resource	rest-api-id=abc123, path-part=users	Resource ID=res456	Resource /users added under root
3	Put Method	rest-api-id=abc123, resource-id=res456, method=GET	Method GET created	GET method added to /users
4	Put Integration	rest-api-id=abc123, resource-id=res456, method=GET, type=MOCK	Integration set	GET method linked to mock backend
5	Create Deployment	rest-api-id=abc123, stage=prod	Deployment ID=dep789	API deployed to prod stage
6	Test API	Invoke GET https://abc123.execute-api.region.amazonaws.com/prod/users	Response 200 OK	API responds as expected
7	Exit	N/A	End	API creation and deployment complete

💡 API is deployed and ready to receive requests at the prod stage

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
API ID	None	abc123	abc123	abc123	abc123	abc123	abc123
Resource ID	None	None	res456	res456	res456	res456	res456
Method GET	None	None	None	Created	Created	Created	Created
Integration	None	None	None	None	Set to MOCK	Set to MOCK	Set to MOCK
Deployment	None	None	None	None	None	dep789	dep789

Key Moments - 3 Insights

Why do we need to create a resource before adding a method?

Because methods like GET or POST belong to specific paths (resources). Step 2 creates the /users path, then step 3 adds GET to it.

What does the integration step do?

It connects the method to a backend service. In step 4, the GET method is linked to a MOCK integration, meaning it returns a fixed response.

Why is deployment necessary after creating methods and integrations?

Deployment (step 5) publishes the API configuration to a stage so it becomes accessible. Without deployment, the API changes are not live.

Visual Quiz - 3 Questions

Look at the execution table, what is the Resource ID after step 2?

A abc123

B res456

C dep789

D None

💡 Hint

Check the 'Result' column in row for step 2 in the execution_table.

At which step is the GET method created?

A Step 1

B Step 4

C Step 3

D Step 5

💡 Hint

Look for 'Method GET created' in the execution_table rows.

If we skip the deployment step, what happens when we try to call the API?

A API returns an error or is not reachable

B API responds with 200 OK

C API returns a mock response

D API automatically deploys

💡 Hint

Refer to the exit_note and step 5 about deployment necessity.

Concept Snapshot

AWS REST API creation steps:
1. Create API Gateway REST API
2. Add resources (paths)
3. Define methods (GET, POST)
4. Integrate methods with backend (Lambda, MOCK)
5. Deploy API to a stage
6. Use the deployed API endpoint
Deployment is required to make API live.

Full Transcript

To create a REST API in AWS, first define the API Gateway REST API. Then add resources which represent URL paths. Next, define HTTP methods like GET or POST on those resources. After that, integrate these methods with backend services such as Lambda functions or mock responses. Finally, deploy the API to a stage like 'prod' to make it accessible. Without deployment, the API is not live. This process ensures your API is structured, connected, and ready to handle requests.