<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Webstep - Medium]]></title>
        <description><![CDATA[Webstep is an IT consultant company composed of 500 employees located in Sweden and Norway. We have consultants who are experts within, System Development, Business Intelligence, IoT, Data Science (ML/AI) and IT-Management. We love to learn new things and share it with others. - Medium]]></description>
        <link>https://medium.com/webstep?source=rss----10da08403cfd---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Webstep - Medium</title>
            <link>https://medium.com/webstep?source=rss----10da08403cfd---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:33:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/webstep" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Type Aliases FTW!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/type-aliases-ftw-59aee25ca511?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/1792/1*dmjbvsdjHKzaE2E9fMJZIQ.png" width="1792"></a></p><p class="medium-feed-snippet">A few Kotlin type aliases recipes that can make your code shine</p><p class="medium-feed-link"><a href="https://medium.com/webstep/type-aliases-ftw-59aee25ca511?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/type-aliases-ftw-59aee25ca511?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/59aee25ca511</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[jvm]]></category>
            <category><![CDATA[dev]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Tue, 07 May 2024 09:17:47 GMT</pubDate>
            <atom:updated>2024-05-07T09:17:47.731Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Suppressenator]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/the-suppressenator-3bbb807fc018?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/1536/1*GvsAE5Zww-ZA5zvSTbAIPg.jpeg" width="1536"></a></p><p class="medium-feed-snippet">A way to visualize the usage of your @Suppress annotations</p><p class="medium-feed-link"><a href="https://medium.com/webstep/the-suppressenator-3bbb807fc018?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/the-suppressenator-3bbb807fc018?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/3bbb807fc018</guid>
            <category><![CDATA[static-code-analysis]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[code-style]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Thu, 16 Nov 2023 08:02:21 GMT</pubDate>
            <atom:updated>2023-11-16T08:02:20.926Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Use Terraform to create an AWS CloudFront distribution from S3 secured with Cognito, Signed Cookie…]]></title>
            <link>https://medium.com/webstep/use-terraform-to-create-an-aws-cloudfront-distribution-from-s3-secured-with-cognito-signed-cookie-26cdfddb306c?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/26cdfddb306c</guid>
            <category><![CDATA[aws-cloudfront]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-cognito]]></category>
            <dc:creator><![CDATA[Madeleine von Hausswolff]]></dc:creator>
            <pubDate>Wed, 24 May 2023 08:44:38 GMT</pubDate>
            <atom:updated>2023-05-24T08:44:37.998Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Use Terraform to create an AWS CloudFront distribution from S3 secured with Cognito, Signed Cookie and Lambda@Edge</strong></h3><blockquote>This is a complete solution to use <strong>Amazon CloudFront</strong> as a CDN to serve images or other content saved in an <strong>S3 bucket</strong> and distributed on the web. The content is protected with signed cookies authorized through <strong>Amazon Cognito</strong>. To be able to keep the solution secure in the long run, it also includes automatic key rotation. The private key for the signed cookie is kept safe in <strong>AWS Secrets Manager. </strong>The public key is configured in CloudFront and <strong>AWS Lambda@Edge </strong>is used to verify the token from Cognito and create a signed cookie. For rotation of the RSA key pair the Secrets Manager is configured to execute an <strong>AWS Lambda</strong> periodically. The whole setup is created in <strong>Terraform</strong> and can be found at the link below. <br><a href="https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform">https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform</a>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UBISP8AuZZcn1AKh" /><figcaption>Photo by <a href="https://unsplash.com/@moneyphotos?utm_source=medium&amp;utm_medium=referral">regularguy.eth</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Example use case</h3><p>So why would we do this? Well, imagine you have a hybrid or mobile app that you want to serve with images. They could of course reside within the application. That would do for those that come shipped with the app, but what if the app needs to have photos uploaded by different users to be shared to all users? Then we could use an S3 bucket in AWS to store the images. If we also want the images to be cached for better performance, CloudFront is perfect for the purpose of serving them back to the app!</p><p>We have just one more requirement, and it is a crucial one; You don’t want the images to be public. Only logged in users should be able to retrieve the images. Since the identity provider for the app is <strong>Cognito User Pool</strong>, it should also be used for the images to achieve single sign on. However, there is no way in AWS to just add it in front of CloudFront. What we have is the option to protect content with a signed cookie. To be able to use Cognito we will need to exchange an access token for a signed cookie. This is a simplified overview:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/559/1*nfDBPLyopNbkfo6KNaQI-A.png" /></figure><h3>User flow</h3><ol><li>The user authenticates from some app that is configured to use the Cognito User Pool instance as its identity provider.</li><li>The app adds an Authorization header with the user’s bearer token and makes a request to the cookie endpoint in CloudFront.</li><li>The Lambda@Edge executes on Viewer request. It verifies the token and responds with the signed cookie if the check was successful.</li><li>Et voilà! The cookie will be attached to every request sent back from the users app. This works since all cookies automatically are sent back to the domain that has set it and the cookie endpoint and images reside on the same domain. So, all images added by a link to the source in CloudFront will show in the app and continue to do so while the cookie is valid.</li></ol><h3>Walkthrough</h3><p>This walkthrough will hopefully explain enough for you to understand the setup. There are things intentionally left out, with the assumption that it is possible to look it up on your own. Please give feedback if this doesn’t work out for you.</p><h4>Cognito login with OAuth2</h4><p>The Cognito User Pool and Client configured in Terraform can be used by any frontend application as an identity provider. A frontend app can’t use a secret, therefore the <em>generate_secret</em> is set to “false”. The parameter <em>allowed_oauth_flows</em> in the client setup has “code” as one of the values. This setting will allow users to sign in with the <a href="https://oauth.net/2/grant-types/authorization-code/"><em>Authorization Code</em></a> grant type. The logged in user will then be able to retrieve an access token from Cognito and use it to get the signed cookie needed.</p><pre>resource &quot;aws_cognito_user_pool&quot; &quot;user_pool&quot; {<br>  name                = &quot;Signed cookie example&quot;<br>  username_attributes = [&quot;email&quot;]<br>  username_configuration {<br>    case_sensitive = false<br>  }<br>  auto_verified_attributes = [&quot;email&quot;]<br>  password_policy {<br>    minimum_length                   = 8<br>    require_uppercase                = true<br>    require_lowercase                = true<br>    require_symbols                  = true<br>    require_numbers                  = true<br>    temporary_password_validity_days = 7<br>  }<br><br>  email_configuration {<br>    email_sending_account = &quot;COGNITO_DEFAULT&quot;<br>  }<br><br>  verification_message_template {<br>    default_email_option = &quot;CONFIRM_WITH_CODE&quot;<br>  }<br><br>  schema {<br>    attribute_data_type      = &quot;String&quot;<br>    developer_only_attribute = false<br>    mutable                  = true<br>    name                     = &quot;email&quot;<br>    required                 = true<br><br>    string_attribute_constraints {<br>      min_length = 5<br>      max_length = 50<br>    }<br>  }<br>}<br><br>resource &quot;aws_cognito_user_pool_client&quot; &quot;client&quot; {<br>  name                   = &quot;Signed cookie example&quot;<br>  user_pool_id           = aws_cognito_user_pool.user_pool.id<br>  generate_secret        = false<br>  refresh_token_validity = 30<br>  access_token_validity  = var.cookie_and_token_expiration_time_in_minutes<br>  id_token_validity      = 10<br>  token_validity_units {<br>    id_token      = &quot;minutes&quot;<br>    refresh_token = &quot;days&quot;<br>    access_token  = &quot;minutes&quot;<br>  }<br><br>  prevent_user_existence_errors = &quot;ENABLED&quot;<br>  explicit_auth_flows = [<br>    &quot;ALLOW_CUSTOM_AUTH&quot;,<br>    &quot;ALLOW_USER_SRP_AUTH&quot;,<br>    &quot;ALLOW_REFRESH_TOKEN_AUTH&quot;<br>  ]<br>  enable_token_revocation              = true<br>  callback_urls                        = [var.cognito_client_callback_url]<br>  logout_urls                          = [var.cognito_client_logout_url]<br>  allowed_oauth_flows_user_pool_client = true<br>  allowed_oauth_flows                  = [&quot;code&quot;, &quot;implicit&quot;]<br>  allowed_oauth_scopes                 = [&quot;phone&quot;, &quot;email&quot;, &quot;openid&quot;, &quot;aws.cognito.signin.user.admin&quot;, &quot;profile&quot;]<br>}</pre><h4>Use an<strong> Identity</strong> Pool and attach IAM policies</h4><p>If the logged in user will need to access other resources in the AWS account, an <strong>Identity Pool</strong> is needed. In our case, the user should be able to upload files to an S3 account. The Identity Pool configured in Terraform is connected to the Cognito User Pool. <em>The web identity roles</em> for <em>authenticated</em> and <em>unauthenticated</em> are configured to be attached to it.</p><p>More about web identity federation on Amazon:<br><a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_oidc.html">https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_oidc.html</a></p><pre>resource &quot;aws_cognito_identity_pool&quot; &quot;identity_pool&quot; {<br>  identity_pool_name               = &quot;Signed cookie example&quot;<br>  allow_unauthenticated_identities = false<br>  allow_classic_flow               = true<br><br>  cognito_identity_providers {<br>    client_id               = aws_cognito_user_pool_client.client.id<br>    provider_name           = aws_cognito_user_pool.user_pool.endpoint<br>    server_side_token_check = false<br>  }<br>}</pre><pre>resource &quot;aws_cognito_identity_pool_roles_attachment&quot; &quot;roles_attachment&quot; {<br>  identity_pool_id = aws_cognito_identity_pool.identity_pool.id<br>  roles = {<br>    &quot;authenticated&quot;   = aws_iam_role.authenticated.arn<br>    &quot;unauthenticated&quot; = aws_iam_role.unauthenticated.arn<br>  }<br>}</pre><p>So, we have attached the IAM roles to our identity pool instance. The next step is to grant access to the S3 bucket for the authenticated role. We can do this by configuring the bucket’s policy and CORS (Cross-Origin Resource Sharing) settings. The policy should include the following actions: “s3:GetObject”, “s3:ListBucket”, “s3:PutObject” and “s3:DeleteObject”. These actions will allow the user to upload, retrieve, and delete objects in the bucket. Additionally, the <em>cors_rule</em> parameter, with the <em>allowed_origins</em> set to “*”,<em> </em>will enable requests from any origin to be sent to the bucket over the internet<em>.</em> However, it is recommended to replace the “<em>*” </em>with specific origin values to restrict access to desired origins.</p><p>The bucket also needs to be accessed by our CloudFront instance. The following Terraform script configures the bucket’s policy:</p><pre>resource &quot;aws_s3_bucket&quot; &quot;photo_bucket&quot; {<br>  bucket = &quot;${var.project_prefix}-photos&quot;<br>}<br><br>resource &quot;aws_s3_bucket_acl&quot; &quot;photo_bucket_acl&quot; {<br>  bucket = aws_s3_bucket.photo_bucket.id<br>  acl    = &quot;private&quot;<br>}<br><br>resource &quot;aws_s3_bucket_policy&quot; &quot;authenticated_access&quot; {<br>  bucket = aws_s3_bucket.photo_bucket.id<br>  policy = data.aws_iam_policy_document.authenticated_access.json<br>}<br><br>data &quot;aws_iam_policy_document&quot; &quot;authenticated_access&quot; {<br>  statement {<br>    principals {<br>      type        = &quot;AWS&quot;<br>      identifiers = [aws_iam_role.authenticated.arn]<br>    }<br><br>    actions = [<br>      &quot;s3:GetObject&quot;,<br>      &quot;s3:ListBucket&quot;,<br>      &quot;s3:PutObject&quot;,<br>      &quot;s3:DeleteObject&quot;<br>    ]<br><br>    resources = [<br>      aws_s3_bucket.photo_bucket.arn,<br>      &quot;${aws_s3_bucket.photo_bucket.arn}/*&quot;,<br>    ]<br>  }<br><br>  statement {<br>    actions = [<br>      &quot;s3:GetObject&quot;,<br>      &quot;s3:ListBucket&quot;<br>    ]<br>    resources = [<br>      aws_s3_bucket.photo_bucket.arn,<br>      &quot;${aws_s3_bucket.photo_bucket.arn}/*&quot;,<br>    ]<br><br>    principals {<br>      type        = &quot;AWS&quot;<br>      identifiers = [&quot;${aws_cloudfront_origin_access_identity.origin_access_identity.iam_arn}&quot;]<br>    }<br>  }<br>}<br><br>resource &quot;aws_cloudfront_origin_access_identity&quot; &quot;origin_access_identity&quot; {<br>}<br><br>resource &quot;aws_s3_bucket_cors_configuration&quot; &quot;photo_bucket_cors&quot; {<br>  bucket = aws_s3_bucket.photo_bucket.id<br><br>  cors_rule {<br>    allowed_headers = [&quot;*&quot;]<br>    allowed_origins = [&quot;*&quot;]<br>    allowed_methods = [&quot;HEAD&quot;, &quot;GET&quot;, &quot;PUT&quot;, &quot;POST&quot;, &quot;DELETE&quot;]<br>    expose_headers  = [&quot;ETag&quot;]<br>    max_age_seconds = 3000<br>  }<br>}</pre><h4>Configure a Trusted Key Group.</h4><p>To protect a distribution in CloudFront, you can just add a <strong>Trusted Key Group</strong> to the cache behavior and the content is no longer publicly accessible. Then, to let the authenticated users access the content, we need to configure the trusted key group to contain at least one valid <strong>Public Key</strong>. That key needs to be the public part of a <strong>2048-bit RSA Key Pair</strong>, since it is the only key type accepted by CloudFront. The <strong>Private Key</strong> from the key pair is kept safe in <strong>Secrets Manager</strong> and used to create the signed cookie. CloudFront will automatically validate all requests by checking the cookies. This way requests with correctly signed cookies will have access to the content.</p><p>You can find more info about signed cookies in CloudFront on Amazon: <a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PrivateContent.html">https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PrivateContent.html</a><br><a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-cookies.html">https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-signed-cookies.html</a></p><h4>Cookie endpoint in Cloudfront</h4><p>For a cookie to be accepted by the browser it will need to be created from the same domain as where the content resides, in this case it will be a <strong>Lambda@Edge </strong>executed in CloudFront. It is possible to set up an endpoint as a part of the cache behavior. We have one with the <em>path-patten</em> “cookie/*” and the lambda associated with it will execute at every request to the address: https://[xxx].cloudfront.se/cookie.</p><p>This is a detailed overview of the whole setup:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOr9e582BJ-8AaViVcqMPw.png" /></figure><p>It is required that every cache behavior has an origin configured. However, in this case the lambda will shortcut the request and return the response to the user, so the request will never reach the origin. So the origin “www.google.com” will never be hit but it still needs to be there.</p><pre>resource &quot;aws_cloudfront_public_key&quot; &quot;VerifySigningPublicKey&quot; {<br>  encoded_key = var.public_key_pem<br>  name        = &quot;${var.project_prefix}-DUMMY_KEY&quot;<br>  # remove below if you have changed the value of the encoded_key <br>  lifecycle {<br>    ignore_changes        = [encoded_key]<br>    create_before_destroy = true<br>  }<br>}<br><br>resource &quot;aws_cloudfront_key_group&quot; &quot;VerifySigningKeyGroup&quot; {<br>  items = [aws_cloudfront_public_key.VerifySigningPublicKey.id]<br>  name  = &quot;${var.project_prefix}-group&quot;<br>  lifecycle {<br>    ignore_changes = [items]<br>  }<br>}<br><br>resource &quot;aws_cloudfront_distribution&quot; &quot;ImageDistribution&quot; {<br>  enabled         = &quot;true&quot;<br>  http_version    = &quot;http2&quot;<br>  is_ipv6_enabled = &quot;true&quot;<br><br>  ordered_cache_behavior {<br>    allowed_methods = [&quot;HEAD&quot;, &quot;GET&quot;, &quot;OPTIONS&quot;]<br>    cache_policy_id = &quot;4135ea2d-6df8-44a3-9df3-4b5a84be39ad&quot; # CachingDisabled<br>    cached_methods  = [&quot;HEAD&quot;, &quot;GET&quot;]<br>    compress        = &quot;true&quot;<br>    default_ttl     = &quot;0&quot;<br>    path_pattern    = &quot;cookie/*&quot;<br><br>    lambda_function_association {<br>      event_type   = &quot;viewer-request&quot;<br>      include_body = &quot;false&quot;<br>      lambda_arn   = &quot;${aws_lambda_function.EdgeCacheRequestSigner.arn}:${aws_lambda_function.EdgeCacheRequestSigner.version}&quot;<br>    }<br><br>    max_ttl          = &quot;0&quot;<br>    min_ttl          = &quot;0&quot;<br>    smooth_streaming = &quot;false&quot;<br>    # Could be any value, since this target never will be hit<br>    target_origin_id       = &quot;www.google.com&quot;<br>    viewer_protocol_policy = &quot;redirect-to-https&quot;<br>  }<br><br>  default_cache_behavior {<br>    allowed_methods    = [&quot;HEAD&quot;, &quot;GET&quot;]<br>    trusted_key_groups = [aws_cloudfront_key_group.VerifySigningKeyGroup.id]<br>    cached_methods     = [&quot;HEAD&quot;, &quot;GET&quot;]<br>    compress           = &quot;true&quot;<br><br>    forwarded_values {<br>      query_string = false<br><br>      cookies {<br>        forward = &quot;none&quot;<br>      }<br>    }<br>    min_ttl     = &quot;0&quot;<br>    max_ttl     = &quot;86400&quot;<br>    default_ttl = &quot;3600&quot;<br><br>    smooth_streaming       = &quot;false&quot;<br>    target_origin_id       = aws_s3_bucket.photo_bucket.bucket_regional_domain_name<br>    viewer_protocol_policy = &quot;redirect-to-https&quot;<br>  }<br><br>  origin {<br>    connection_attempts = &quot;1&quot;<br>    connection_timeout  = &quot;10&quot;<br><br>    custom_origin_config {<br>      http_port                = &quot;80&quot;<br>      https_port               = &quot;443&quot;<br>      origin_keepalive_timeout = &quot;5&quot;<br>      origin_protocol_policy   = &quot;https-only&quot;<br>      origin_read_timeout      = &quot;30&quot;<br>      origin_ssl_protocols     = [&quot;TLSv1.2&quot;]<br>    }<br><br>    domain_name = &quot;www.google.com&quot;<br>    origin_id   = &quot;www.google.com&quot;<br>  }<br><br>  origin {<br>    connection_attempts = &quot;3&quot;<br>    connection_timeout  = &quot;10&quot;<br><br>    s3_origin_config {<br>      origin_access_identity = aws_cloudfront_origin_access_identity.origin_access_identity.cloudfront_access_identity_path<br>    }<br>    domain_name = aws_s3_bucket.photo_bucket.bucket_regional_domain_name<br>    origin_id   = aws_s3_bucket.photo_bucket.bucket_regional_domain_name<br>  }<br>}</pre><p>You can find more information how Cognito and Lambda@Edge work together on the following links.<br><a href="https://cloudonaut.io/authentication-at-the-edge-with-lambda-edge-cognito/">https://cloudonaut.io/authentication-at-the-edge-with-lambda-edge-cognito/</a><br><a href="https://github.com/disney/terraform-aws-lambda-at-edge-cognito-authentication">https://github.com/disney/terraform-aws-lambda-at-edge-cognito-authentication</a></p><h4>Lambda@Edge to create cookies.</h4><p>To enable CloudFront to respond with correctly signed cookies we must add some custom code. In our case, we use a Lambda@Edge that will verify the user’s token and create the signed cookie. The <a href="https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform/tree/main/edge-cache-request-signer">edge-cache-request-signer</a> lambda will execute on the specified endpoint at every viewer request. We use the same lambda both to create a new cookie and to remove an earlier created cookie. The code for the two tasks is so similar, so there was no need to duplicate it into two lambdas. We simply check if the user’s request path and if it ends with “/remove” it expires an existing cookie instead of creating a new one.</p><p>Lambda@Edge differs a bit from the ordinary Lambdas. Since there is a need for high performance it is saved on different edge locations close to the user. One thing is that it can’t have environment variables. So, a way to use variables despite this is to use <strong>AWS Systems Manager (SSM) Parameter Store</strong>. Then the key-value pairs are saved at one place and just referenced to by all the copies of the lambda saved on edge locations.</p><p>As mentioned above, the private key used to create the cookie is kept in the secrets manager. However, in the signer lambda, we use the ssm parameter store to retrieve it. We could have accessed it directly, but Amazon has made the option to get it through the parameter store available. This helps us to simplify the lambda code.</p><p>Read more about the difference between secrets manager and parameter store below.<br><a href="https://medium.com/awesome-cloud/aws-difference-between-secrets-manager-and-parameter-store-systems-manager-f02686604eae">https://medium.com/awesome-cloud/aws-difference-between-secrets-manager-and-parameter-store-systems-manager-f02686604eae</a></p><h4>Template to enable multiple stacks</h4><p>To be able to set up multiple stacks in the same account (e.g. dev and stage), we make use of a prefix to the parameter name in<strong> </strong>SSM Parameter Store<strong> </strong>that is a changeable variable in the Terraform solution. To be able to inject the value of the variable into the Lambda we use a template for the <em>index.js</em> file. In our case the Terraform template will replace all `${ssm_prefix}` with the value of the variable set in a <em>.tfvars file</em>. For example, `${ssm_prefix}-cloudfront-domain` will be transformed into `devsignauth-cloudfront-domain`. If “devsignaut” was the value of <em>ssm_prefix</em>. This allows us to inject the ssm parameter names into the <em>index.js</em> file on Terraform apply. The process copies the original file and saves it to a new local file.</p><p>When a Lambda is used in a <em>lambda_function_association </em>in CloudFront (see Terraform code above), it needs to refer to a specific version of the lambda. This is why we need to set the parameter <em>publish </em>to “true” so that the version is created.</p><p>The region for the Lambda function is hardcoded to “us-east-1”. While you can choose the region for most resources, Lambda@Edge is an exception. It must be deployed specifically in the “us-east-1&quot; region.</p><pre>resource &quot;local_file&quot; &quot;templated&quot; {<br>  content = templatefile(&quot;${path.module}/edge-cache-request-signer/index.js&quot;, {<br>    ssm_prefix = var.project_prefix,<br>  })<br>  filename = &quot;${path.module}/edge-cache-request-signer/deploy/index.js&quot;<br>}<br><br>data &quot;archive_file&quot; &quot;EdgeCacheRequestSignerArchive&quot; {<br>  depends_on = [<br>    local_file.templated<br>  ]<br>  type        = &quot;zip&quot;<br>  source_dir  = &quot;${path.module}/edge-cache-request-signer/deploy&quot;<br>  output_path = &quot;${path.module}/edge-cache-request-signer/deploy/edge-cache-request-signer.zip&quot;<br>}<br><br>resource &quot;aws_lambda_function&quot; &quot;EdgeCacheRequestSigner&quot; {<br>  architectures                  = [&quot;x86_64&quot;]<br>  description                    = &quot;Signing requests to cache&quot;<br>  function_name                  = &quot;edge-cache-request-signer&quot;<br>  handler                        = &quot;index.handler&quot;<br>  filename                       = data.archive_file.EdgeCacheRequestSignerArchive.output_path<br>  memory_size                    = &quot;128&quot; # max size allowed for &quot;viewer-request&quot; event type<br>  package_type                   = &quot;Zip&quot;<br>  reserved_concurrent_executions = &quot;-1&quot;<br>  role                           = aws_iam_role.EdgeCacheRequestSignerFunctionRole.arn<br>  runtime                        = &quot;nodejs16.x&quot;<br>  timeout                        = &quot;5&quot;<br>  provider                       = aws.us-east-1<br>  # publish will publish a new version of the lambda.<br>  publish                        = true<br>  source_code_hash               = data.archive_file.EdgeCacheRequestSignerArchive.output_base64sha256</pre><h3>Key rotation</h3><p>To keep up the security of the signed cookie solution, we need to ensure that the RSA key pair in use is rotated regularly. In this solution, we have that process automated by the <strong>Secrets Manager.</strong> It will rotate the key by executing a lambda according to a specified schedule. In our case it will generate a new RSA key pair and save it to Secrets Manager (private) and CloudFront (public).</p><p>To be able to setup and deploy the complete solution in Terraform we use a dummy RSA Key pair to begin with. But don’t worry, this one won’t be used since it is rotated immediately after deployment.</p><pre>resource &quot;aws_secretsmanager_secret&quot; &quot;SigningPrivateKey&quot; {<br>  name        = var.signing_key_name<br>  description = &quot;Private key for CloudFront trusted keygroup&quot;<br>  provider    = aws.us-east-1<br>}<br><br>resource &quot;aws_secretsmanager_secret_version&quot; &quot;SigningPrivateKeyVersion&quot; {<br>  secret_id     = aws_secretsmanager_secret.SigningPrivateKey.id<br>  secret_string = var.private_key_pem<br>  provider      = aws.us-east-1<br>}<br><br>resource &quot;aws_secretsmanager_secret_rotation&quot; &quot;RsaKeypairRotation&quot; {<br>  secret_id           = aws_secretsmanager_secret.SigningPrivateKey.id<br>  rotation_lambda_arn = aws_lambda_function.KeyRotator.arn<br>  provider            = aws.us-east-1<br><br>  rotation_rules {<br>    automatically_after_days = var.automatically_after_days<br>  }<br>}</pre><p>To do the rotation without interfering with any logged in users, the old public key is not removed immediately from the key group. It is kept there until the next key rotation. This works fine since there can be multiple private keys in a key group. After key rotation is done, there will always be two public keys in the key group. Every key uploaded will get an id generated by cloudfront. This id must be used by the <a href="https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform/tree/main/edge-cache-request-signer">edge-cache-request-signer</a> lambda (see description above) to create the signed cookie. So to enable the signer lambda above to access the new id, the SSM parameter that holds it will be updated with the id as the new value.</p><p>Here are all steps the <a href="https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform/blob/main/key-rotator/index.js">key-rotater</a> lambda in this solution takes to manage the rotation:</p><ol><li>Creates a new Key Pair.</li><li>Identify which key to keep, if any.</li><li>Removes all other keys from the key group, which can be the initial dummy key or the one rotated on last execution.</li><li>Deletes all identified other keys.</li><li>Adds the newly created public key to CloudFront.</li><li>Adds the public key to CloudFront Key Group.</li><li>Updates the private key in Secrets Manager.</li><li>Updates value for public keyId in SSM parameter store with the id of the newly created CloudFront key.</li></ol><h3><strong>Final words</strong></h3><p>This article explains the crucial parts on how to set up a CDN distribution of images or other content with AWS services and Terraform. The repo is ready to be deployed and will create all pieces needed. What you need to do is add your own variables in a “.tfvars” file. If you want to deploy more than one copy of the solution, you can add another “.tfvars” with different values and use it instead. If you want to add one that automatically loads on Terraform apply, name it “terraform.tfvars”.</p><p>If you want to spice up this distribution with resizing images on the fly before caching them check out the following blog post. <a href="https://aws.amazon.com/blogs/storage/modify-images-cached-in-amazon-cloudfront-using-amazon-s3-object-lambda/">https://aws.amazon.com/blogs/storage/modify-images-cached-in-amazon-cloudfront-using-amazon-s3-object-lambda/</a></p><p>This is a complete backend solution. To use it you will have to create a frontend to it. This can be done with the technique of your choice. It will need a possibility for users to login with the Cognito User Pool created by this Terraform script. If you would like to see an example on how this can be done with Ionic/Angular, stay tuned for my next blog post.</p><p>Remember to follow the instructions in the readme file in the github repo:<br><a href="https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform">https://github.com/madvonh/cloudfront-cognito-signed-cookies-terraform</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26cdfddb306c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webstep/use-terraform-to-create-an-aws-cloudfront-distribution-from-s3-secured-with-cognito-signed-cookie-26cdfddb306c">Use Terraform to create an AWS CloudFront distribution from S3 secured with Cognito, Signed Cookie…</a> was originally published in <a href="https://medium.com/webstep">Webstep</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we use mitosis to split the monolith]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/how-we-use-mitosis-to-split-the-monolith-8b73a437f749?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/600/0*vxDUSO-CuBnj-utY.jpg" width="600"></a></p><p class="medium-feed-snippet">Using a cell division metaphor as a way to extract fractions of the monolith into microservices</p><p class="medium-feed-link"><a href="https://medium.com/webstep/how-we-use-mitosis-to-split-the-monolith-8b73a437f749?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/how-we-use-mitosis-to-split-the-monolith-8b73a437f749?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/8b73a437f749</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Wed, 29 Mar 2023 06:52:01 GMT</pubDate>
            <atom:updated>2023-03-29T07:24:06.193Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Pre-mortem workshop: guide your team through a dystopic nightmare]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/pre-mortem-workshop-guide-your-team-through-a-dystopic-nightmare-b6d426d9ab05?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/768/1*-j6YaWAqB-ARNFz8ET_GYg.png" width="768"></a></p><p class="medium-feed-snippet">Tired of risk analysis? Try a different approach!</p><p class="medium-feed-link"><a href="https://medium.com/webstep/pre-mortem-workshop-guide-your-team-through-a-dystopic-nightmare-b6d426d9ab05?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/pre-mortem-workshop-guide-your-team-through-a-dystopic-nightmare-b6d426d9ab05?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/b6d426d9ab05</guid>
            <category><![CDATA[pre-mortem]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[methodology]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[workshop-facilitation]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Wed, 11 Jan 2023 08:42:40 GMT</pubDate>
            <atom:updated>2023-01-11T08:42:40.792Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Being an AWS CB, what do I get?]]></title>
            <link>https://medium.com/webstep/being-an-aws-cb-what-do-i-get-d065ad7f350b?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/d065ad7f350b</guid>
            <category><![CDATA[aws-community]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Saif]]></dc:creator>
            <pubDate>Tue, 25 Oct 2022 09:26:05 GMT</pubDate>
            <atom:updated>2022-10-25T09:26:05.200Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Y2V1nIqCxSOZeNPkk3BEg.jpeg" /><figcaption>Johannes Koch</figcaption></figure><p>After my Cloud Evangelist promotion at <a href="https://www.linkedin.com/company/webstep-ab/">Webstep AB</a>, I got a couple of questions about what an AWS Community Builder is. The questions were mainly about the benefits, and I can say if it’s only the benefits you are asking for, then maybe you are thinking of it from the other way around, but as many have asked, here is a little drill down.</p><h3>What is AWS Community Builders?</h3><p>It is a program organized by AWS, a unique opportunity that offers sessions including technical and non-technical knowledge sharing, networking with other AWS builders, insights into upcoming products, contact with the AWS service/product team, and much more.</p><h3>Out of my personal experience</h3><p>Working with different services makes you wonder why a particular feature is similar to another, missing, or placed somewhere. Regardless, it is empowering to ask that question about the said feature and get it answered by that service/product team. It feels like you have access to information that could change the course of designing a solution based on facts you’ve got from the service developers themselves.</p><p>Having that access does it for me! But hey, there is more!</p><p>Like this fun thing: seek minute 1:30 for a bit of surprise ;)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fdms7RlAPNDs%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ddms7RlAPNDs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fdms7RlAPNDs%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4a7d5c2ce0159e512c52bcfdb4a63fdc/href">https://medium.com/media/4a7d5c2ce0159e512c52bcfdb4a63fdc/href</a></iframe><p>And no, I didn’t have any paper to read from at the end :)</p><h3>Anything else?</h3><p>They are plenty of benefits besides these that are copied directly from the community builder page (linked below):</p><ul><li>Access to AWS product teams and information about new services and features via weekly webinars</li><li>Learning from AWS subject matter experts on a variety of non-technical topics, including content creation and support for submitting CFPs and securing speaking engagements</li><li>AWS Promotional Credits and other helpful resources to support content creation and community-based work</li><li>Some surprises!</li></ul><p>For instance, that t-shirt you saw me wearing at the beginning of this article, for instance, was sent to me after some meetings with the community, a subscription to cloud tutorials, and yes, you read about the AWS Credits, but how about re:Invent? :)</p><p>Having your name listed on AWS, maybe?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KnsXOTuTLGQTn1B_" /></figure><p>Ask me or look into the <a href="https://aws.amazon.com/developer/community/community-builders/">AWS Community Builders program page</a> for some FAQs &amp; application submissions</p><p>Did this help you?</p><p>— <a href="https://twitter.com/saifalzo">Saif</a>;</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d065ad7f350b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webstep/being-an-aws-cb-what-do-i-get-d065ad7f350b">Being an AWS CB, what do I get?</a> was originally published in <a href="https://medium.com/webstep">Webstep</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kotlin scope function mnemonics]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/kotlin-scope-function-mnemonics-624a53b98730?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/2600/0*lcN_Qei6FwQi1hPG" width="6000"></a></p><p class="medium-feed-snippet">Kotlin&#x2019;s scope functions: apply, run, also and let are great, but how do I know which is which and when to use them?</p><p class="medium-feed-link"><a href="https://medium.com/webstep/kotlin-scope-function-mnemonics-624a53b98730?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/kotlin-scope-function-mnemonics-624a53b98730?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/624a53b98730</guid>
            <category><![CDATA[kotlin-scope-functions]]></category>
            <category><![CDATA[schrödinger]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Tue, 14 Jun 2022 06:55:49 GMT</pubDate>
            <atom:updated>2022-12-11T18:53:26.156Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[WeekFields to the rescue!]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/weekfields-to-the-rescue-fb2769e02091?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/2600/0*QYDoSUK-bmVNh53s" width="6240"></a></p><p class="medium-feed-snippet">Java&#x2019;s endless number of ways of calculating week numbers</p><p class="medium-feed-link"><a href="https://medium.com/webstep/weekfields-to-the-rescue-fb2769e02091?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/weekfields-to-the-rescue-fb2769e02091?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/fb2769e02091</guid>
            <category><![CDATA[calendar]]></category>
            <category><![CDATA[sweden]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[adtech]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Fri, 27 May 2022 04:34:06 GMT</pubDate>
            <atom:updated>2022-12-11T18:58:17.029Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[State of the Discriminated Union]]></title>
            <link>https://medium.com/webstep/state-of-the-discriminated-union-148d128d8de6?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/148d128d8de6</guid>
            <category><![CDATA[monads]]></category>
            <category><![CDATA[oneof]]></category>
            <category><![CDATA[discriminated-union]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[c-sharp-programming]]></category>
            <dc:creator><![CDATA[Erik Svensson]]></dc:creator>
            <pubDate>Tue, 22 Mar 2022 07:47:30 GMT</pubDate>
            <atom:updated>2022-03-23T09:08:45.355Z</atom:updated>
            <content:encoded><![CDATA[<h4>Third party goodness for C#, as the state of the (native) discriminated union is still unclear.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x79twktEpEGqzBJi6hyH3A.png" /></figure><p><strong>You might have heard of the discriminated union type</strong>, as it’s called in F#. It’s a special type that’s available in a range of statically-typed multi-paradigm languages, including Rust, Swift, Scala and Typescript. But C# developers are still missing out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/889/1*I9-I-fttdQjOnSIcksPasQ.png" /><figcaption><a href="https://twitter.com/MadsTorgersen/status/1387079125676875776">https://twitter.com/MadsTorgersen/status/1387079125676875776</a></figcaption></figure><p>Design discussions are still ongoing in <a href="https://github.com/dotnet/csharplang/issues/113">dotnet/csharplang/issue#113</a>, and it seems unlikely that it will make it into C# 11.</p><h4>So what is it and why do people want it?</h4><p>The discriminated union type simply states that data can be one of a range of pre-defined types. Like this:</p><pre>type SaveCustomerResult =<br>   | CustomerCreated<br>   | CustomerUpdated<br>   | SaveFailed</pre><p>SaveCustomerResult is compile-time guaranteed be of either type CustomerCreated, CustomerUpdated or SaveFailed. It can also be inferred from any of the union’s child types. Which allows you do write (pseudo) code like this:</p><pre>var status = save(customerData)<br>   match<br>      | CustomerCreated =&gt; &quot;customer was created&quot;<br>      | CustomerUpdated =&gt; &quot;customer was updated&quot;<br>      | SaveFailed =&gt; &quot;could not save customer&quot;</pre><pre>SaveCustomerResult save(customer) {<br>   try {<br>       if (exists(customer.id)) {<br>           update(customer)<br>           return CustomerUpdated<br>       }</pre><pre>       create(customer)<br>       return CustomerCreated<br>   }<br>   catch {<br>       return SaveFailed<br>   }<br>}</pre><p>If you’re doing something that has a range of outcomes, discriminated unions help you describe it simply and with type safety, leaving no stone unturned — discouraging logic based on null cases or polymorphism.</p><h4>Harry McIntyre to the Rescue</h4><p>Harry and a range of open-source contributors provide the <a href="https://github.com/mcintyre321/OneOf">OneOf library</a> for dotnet. Which brings <em>F# style d̶i̶s̶c̶r̶i̶m̶i̶n̶a̶t̶e̶d̶ unions for C#. </em>The library has been available since 2016 and is ever-increasing in popularity. Harry is also an active voice in the design discussions for a potential C# native implementation.</p><p><strong>On the d̶i̶s̶c̶r̶i̶m̶i̶n̶a̶t̶e̶d̶ part<br></strong>For a union to be <em>discriminated </em>it must consist only of <em>different</em> types. But due to limitations of C#’s generic type constraints, OneOf&lt;string, string&gt; will compile. This type check limitation might be related to why we don’t have native discriminated unions in C# yet.</p><p><strong>Let’s look at some OneOf code<br></strong>First off, OneOf brings exhaustive pattern matching with<strong> </strong>Match and Switch. Meaning that you must explicitly declare all outcomes or else it won’t compile. Compare to the built-in switch which let’s you compile and forget that you have unmanaged cases.</p><pre>OneOf&lt;Yes, No, Maybe&gt; union ... ;</pre><pre>// Use Switch when you don&#39;t want to return anything<br>union.Switch(<br>    yes =&gt; Console.WriteLine(&quot;yes&quot;),<br>    no =&gt; Console.WriteLine(&quot;no&quot;),<br>    maybe =&gt; Console.WriteLine(&quot;maybe&quot;));</pre><pre>// Use Match to return a value<br>string response = union.Match(<br>   yes =&gt; &quot;yes&quot;,<br>   no =&gt; &quot;no&quot;,<br>   maybe =&gt; &quot;maybe&quot;);</pre><p>Using the pseudo code example above we can write it with C# and OneOf instead. For more and better examples checkout the <a href="https://github.com/mcintyre321/OneOf">GitHub repo of OneOf</a>.</p><pre>var status = Save(customerData)<br>                .Match(<br>                    created =&gt; &quot;customer was created&quot;,<br>                    updated =&gt; &quot;customer was updated&quot;,<br>                    failed =&gt; &quot;could not save customer&quot;);</pre><pre>OneOf&lt;CustomerCreated,<br>      CustomerUpdated,<br>      SaveFailed&gt; Save(CustomerData customer)<br>{<br>   try<br>   {<br>       if (_repository.Exists(customer.id)) {<br>           _repository.Update(customer);<br>           return new CustomerUpdated(customer);<br>       }</pre><pre>       _repository.Create(customer);<br>       return new CustomerCreated(customer);<br>   }<br>   catch<br>   {<br>       return new SaveFailed(customer);<br>   }<br>}</pre><h4>Other Types Derived from Discriminated Unions</h4><p>While this post focused on the union type itself, there is a whole functional world of possibilities opening up just by having the option to say that something is one-of some other things. I’m thinking about certain monads that help remove if and else branching logic in your code, making it more readable and less error prone.</p><p>I will write a follow-up post on this, where I talk about my <a href="https://github.com/svan-jansson/OneOf.Monads">OneOf.Monads library</a>.</p><p>Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=148d128d8de6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/webstep/state-of-the-discriminated-union-148d128d8de6">State of the Discriminated Union</a> was originally published in <a href="https://medium.com/webstep">Webstep</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Innocent integration, haunted by ghosts]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/webstep/innocent-integration-haunted-by-ghosts-115e2f9bb5d?source=rss----10da08403cfd---4"><img src="https://cdn-images-1.medium.com/max/2600/0*RVb7AQPVkWAql8Ri" width="5184"></a></p><p class="medium-feed-snippet">How a simple service became a ghostly nightmare</p><p class="medium-feed-link"><a href="https://medium.com/webstep/innocent-integration-haunted-by-ghosts-115e2f9bb5d?source=rss----10da08403cfd---4">Continue reading on Webstep »</a></p></div>]]></description>
            <link>https://medium.com/webstep/innocent-integration-haunted-by-ghosts-115e2f9bb5d?source=rss----10da08403cfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/115e2f9bb5d</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Uzi Landsmann]]></dc:creator>
            <pubDate>Wed, 05 Jan 2022 07:56:26 GMT</pubDate>
            <atom:updated>2022-12-11T19:01:01.311Z</atom:updated>
        </item>
    </channel>
</rss>