

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://buraktas.com/</id>
  <title>Burak Aktas</title>
  <subtitle>All about programming</subtitle>
  <updated>2024-10-18T22:53:13+03:00</updated>
  <author>
    <name>Burak Aktas</name>
    <uri>http://buraktas.com/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="http://buraktas.com/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="http://buraktas.com/"/>
  <generator uri="https://jekyllrb.com/" version="4.2.2">Jekyll</generator>
  <rights> © 2024 Burak Aktas </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>API Gateway IAM Authorization for Cross Account Access with AWS CDK</title>
    <link href="http://buraktas.com/api-gateway-iam-auth-cross-account-with-aws-cdk/" rel="alternate" type="text/html" title="API Gateway IAM Authorization for Cross Account Access with AWS CDK" />
    <published>2023-10-03T00:00:00+03:00</published>
  
    <updated>2023-10-03T00:00:00+03:00</updated>
  
    <id>http://buraktas.com/api-gateway-iam-auth-cross-account-with-aws-cdk/</id>
    <content src="http://buraktas.com/api-gateway-iam-auth-cross-account-with-aws-cdk/" />
    <author>
      <name>buraktas</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="aws-cdk" />
    
    <category term="authorization" />
    
  

  
    <summary>
      





      In my previous articles, we saw how to implement OAuth flows for implementing protected APIs. In this tutorial, we will implement a protected API served through an API Gateway configured with IAM Authorization that doesn’t
require a JWT token and supports access from different AWS accounts. I had a use case to implement an internal API for a couple of teams within the same AWS Organization.
IAM...
    </summary>
  

  </entry>

  
  <entry>
    <title>API Gateway Websocket API Example with AWS CDK</title>
    <link href="http://buraktas.com/api-gateway-websocket-api-example-aws-cdk/" rel="alternate" type="text/html" title="API Gateway Websocket API Example with AWS CDK" />
    <published>2023-04-03T00:00:00+03:00</published>
  
    <updated>2023-04-04T13:00:35+03:00</updated>
  
    <id>http://buraktas.com/api-gateway-websocket-api-example-aws-cdk/</id>
    <content src="http://buraktas.com/api-gateway-websocket-api-example-aws-cdk/" />
    <author>
      <name>buraktas</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="aws-cdk" />
    
    <category term="network" />
    
  

  
    <summary>
      





      In this tutorial, we will learn how to create a basic application for publishing real-time notifications via websocket api from API Gateway. Before having API Gateway support for websockets we had to
have a separate websocket server to publish notifications or sending messages to the available connections at that point of time. API Gateway literally simplifies this process and fits it into the ...
    </summary>
  

  </entry>

  
  <entry>
    <title>API Gateway Add Base Path Mapping into Existing Custom Domain with AWS CDK</title>
    <link href="http://buraktas.com/api-gateway-add-base-path-mapping-into-existing-custom-domain-aws-cdk/" rel="alternate" type="text/html" title="API Gateway Add Base Path Mapping into Existing Custom Domain with AWS CDK" />
    <published>2023-03-22T00:00:00+03:00</published>
  
    <updated>2023-03-23T12:55:10+03:00</updated>
  
    <id>http://buraktas.com/api-gateway-add-base-path-mapping-into-existing-custom-domain-aws-cdk/</id>
    <content src="http://buraktas.com/api-gateway-add-base-path-mapping-into-existing-custom-domain-aws-cdk/" />
    <author>
      <name>buraktas</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="aws-cdk" />
    
    <category term="network" />
    
  

  
    <summary>
      





      In this tutorial we will learn how to add base path mappings into an existing custom domain on API Gateway. Managing shared infrastructure in a separate stack is one of the most common ways in software world. We generally create this
stack for provisioning resources like databases, VPCs, domains etc. which are most likely to be referenced from another stacks belonging to different teams. And on...
    </summary>
  

  </entry>

  
  <entry>
    <title>API Gateway Lambda Custom Authorizer with AWS CDK</title>
    <link href="http://buraktas.com/api-gateway-custom-lambda-authorizer-aws-cdk/" rel="alternate" type="text/html" title="API Gateway Lambda Custom Authorizer with AWS CDK" />
    <published>2023-03-11T00:00:00+03:00</published>
  
    <updated>2023-04-03T16:58:08+03:00</updated>
  
    <id>http://buraktas.com/api-gateway-custom-lambda-authorizer-aws-cdk/</id>
    <content src="http://buraktas.com/api-gateway-custom-lambda-authorizer-aws-cdk/" />
    <author>
      <name>buraktas</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="aws-cdk" />
    
    <category term="authorization" />
    
  

  
    <summary>
      





      In this tutorial we will learn how to build and attach a Lambda Custom Authorizer for our Lambda Rest Api by provisioning required resources with AWS CDK. Though, before moving forward lets talk about what is it and when we need to use it.
A Lambda authorizer is a Lambda function to authenticate incoming requests before hitting our integration resources. It can also be used for both authenticat...
    </summary>
  

  </entry>

  
  <entry>
    <title>OAuth 2.0 Client Credentials Flow with AWS Cognito in AWS CDK</title>
    <link href="http://buraktas.com/oauth-client-credentials-flow-aws-cdk/" rel="alternate" type="text/html" title="OAuth 2.0 Client Credentials Flow with AWS Cognito in AWS CDK" />
    <published>2022-06-03T00:00:00+03:00</published>
  
    <updated>2023-04-03T16:58:08+03:00</updated>
  
    <id>http://buraktas.com/oauth-client-credentials-flow-aws-cdk/</id>
    <content src="http://buraktas.com/oauth-client-credentials-flow-aws-cdk/" />
    <author>
      <name>buraktas</name>
    </author>

  
    
    <category term="aws" />
    
    <category term="aws-cdk" />
    
    <category term="authorization" />
    
    <category term="oauth" />
    
  

  
    <summary>
      





      We learned how to implement OAuth Authorization Code Flow which provides client facing apps to access protected resources in my previous tutorial. Now what if there are external companies, clients, devices etc.
wants to integrate with our resources? We generally have been provided some sort of credentials which can be a basic username password tuple, api key, even a unique string to make a call...
    </summary>
  

  </entry>

</feed>


