deploy: 4377dd0

index.xml

@@ -11,7 +11,7 @@ Navigate to “Set up single sign on” in your Azure AD Enterpr
 In the Basic SAML Configuration, ensure that the settings match the following details
 Take the correct values for Identifier (Entity ID) and Reply URL from the Identity Provider configuration page.
 In the Attributes &amp;amp; Claims section, add a group claim with the following configuration and save it.</description></item><item><title>Third Party Software Tools</title><link>/legal/third-party-software-tools/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/legal/third-party-software-tools/</guid><description>We build on a number of third-party software tools, including the following:
-Third-Party software License Python/pip modules: airspeed BSD License amazon_kclpy Amazon Software License boto3 Apache License 2.0 coverage Apache License 2.0 docopt MIT License flask BSD License flask_swagger MIT License jsonpath-rw Apache License 2.0 moto Apache License 2.0 requests Apache License 2.0 subprocess32 PSF License Other tools: Elasticsearch Apache License 2.0 kinesis-mock MIT License</description></item><item><title>Application Preview</title><link>/user-guide/cloud-sandbox/application-previews/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/cloud-sandbox/application-previews/</guid><description>Introduction Application Preview generates a preview environment from GitHub Pull Requests (PRs). It allows temporary deployment of AWS powered applications on a LocalStack Ephemeral Instance to preview changes. This feature is currently only available for GitHub repositories that use GitHub Actions.
+Third-Party software License Python/pip modules: airspeed BSD License amazon_kclpy Amazon Software License boto3 Apache License 2.0 coverage Apache License 2.0 docopt MIT License flask BSD License flask_swagger MIT License jsonpath-rw Apache License 2.0 moto Apache License 2.0 requests Apache License 2.0 subprocess32 PSF License Other tools: Elasticsearch Apache License 2.0 kinesis-mock MIT License</description></item><item><title>Application Preview</title><link>/user-guide/cloud-sandbox/application-previews/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/cloud-sandbox/application-previews/</guid><description>Introduction Application Preview generates a preview environment from GitHub Actions workflows. For example, you can create a preview URL for every GitHub Pull Request (PRs). It allows temporary deployment of AWS powered applications on a LocalStack Ephemeral Instance to preview changes. This feature is currently only available for GitHub repositories that use GitHub Actions.
 Note Application Preview is offered as a preview feature and under active development. Getting started This guide is designed for users new to Application Preview and assumes basic knowledge of GitHub Actions.</description></item><item><title>Cloud Pods</title><link>/user-guide/state-management/cloud-pods/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/state-management/cloud-pods/</guid><description>Introduction Cloud pods are persistent state snapshots of your LocalStack instance that can easily be stored, versioned, shared, and restored. Cloud Pods can be used for various purposes, such as:
 Save and manage snapshots of active LocalStack instances. Share state snapshots with your team to debug collectively. Automate your testing pipelines by pre-seeding CI environments. Create reproducible development and testing environments locally. Installation You can save and load the persistent state of Cloud Pods, you can use the Cloud Pods command-line interface (CLI).</description></item><item><title>Deploy a full fledged containerised application using LocalStack</title><link>/academy/localstack-deployment/deploy-app-ls/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/academy/localstack-deployment/deploy-app-ls/</guid><description>In this lesson, we&amp;rsquo;ll guide you through deploying a continer-based application, which mimics the complexity of a real-world application. We are using the following AWS services and their features to build our infrastructure:
 Elastic Container Service to create and deploy our containerized application. DynamoDB as a key-value and document database to persist our data. API Gateway to expose the containerized services to the user through HTTP APIs. Cognito User Pools for user authentication and authorizing requests to container APIs.</description></item><item><title>Deploying Lambda container image locally with Elastic Container Registry (ECR) using LocalStack</title><link>/tutorials/lambda-ecr-container-images/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/tutorials/lambda-ecr-container-images/</guid><description>Lambda is a powerful serverless compute system that enables you to break down your application into smaller, independent functions. These functions can be deployed as individual units within the AWS ecosystem. Lambda offers seamless integration with various AWS services and supports multiple programming languages for different runtime environments. To deploy Lambda functions programmatically, you have two options: uploading a ZIP file containing your code and dependencies or packaging your code in a container image and deploying it through Elastic Container Registry (ECR).</description></item><item><title>Explainable IAM</title><link>/user-guide/security-testing/explainable-iam/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/security-testing/explainable-iam/</guid><description>Introduction The IAM Policy Engine logs output related to failed policy evaluation directly to the LocalStack logs. You can enable DEBUG=1 to gain visibility into these log messages, allowing you to identify the additional policies required for your request to succeed.
@@ -67,8 +67,7 @@ Snippets CodeBuild has the capability to use LocalStack&amp;rsquo;s GitHub Actio
 For developing AWS applications locally, the tool of choice is LocalStack, which can sustain a full-blown comprehensive stack. However, when issues appear, and engineers need a second opinion from a colleague, recreating the environment from scratch can leave details slipping through the cracks. This is where Cloud Pods come in, to encapsulate the state of the LocalStack instance and allow for seamless collaboration.</description></item><item><title>LocalSurf</title><link>/user-guide/tools/localsurf/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/localsurf/</guid><description>Introduction LocalSurf is a Chrome browser plugin to repoint AWS service calls to LocalStack. While developing and testing AWS cloud Web applications locally with LocalStack, we need to make the browser connect to the local endpoint (http://localhost:4566) instead of the AWS production servers (*.amazonaws.com). LocalSurf enables you to use the production code without changes, and have the browser make requests to LocalStack instead of AWS directly by explicitly setting the endpoint attribute in the AWS JavaScript SDK.</description></item><item><title>Replicating cloud resources locally with LocalStack's AWS Replicator extension</title><link>/tutorials/replicate-aws-resources-localstack-extension/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/tutorials/replicate-aws-resources-localstack-extension/</guid><description>Introduction LocalStack&amp;rsquo;s core cloud emulator enables you to emulate various cloud services on your own local machine. This allows you to work on and test your cloud-based solutions without needing to connect to a remote cloud. However, sometimes you might need to smoothly switch between your local setup and actual cloud resources, especially in hybrid scenarios. This could be useful, for example, if you want to share a database with your local Lambda function, or if you require access to S3 files stored remotely while running a Glue ETL job locally.</description></item><item><title>Setup GitHub Action workflow that starts up LocalStack and deploys the infrastructure</title><link>/academy/localstack-deployment/github-action-ls/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/academy/localstack-deployment/github-action-ls/</guid><description>LocalStack allows organizations to automate their application testing and integration process using continuous integration (CI). You can seamlessly integrate LocalStack with your current CI platform. LocalStack offers native plugin for CircleCI &amp;amp; GitHub Actions, and a universal driver for other CI platforms. This integration enables you to include LocalStack&amp;rsquo;s local AWS cloud emulation in your CI pipelines, leverage advanced features such as Cloud Pods and CI analytics, and execute your test and integration suite before deploying to production.</description></item><item><title>Travis CI</title><link>/user-guide/ci/travis-ci/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/ci/travis-ci/</guid><description>This guide shows how to start and use LocalStack in your Travis CI jobs.
 Setting up the Travis CI job When you want to integrate LocalStack into your job configuration, you just have to execute the following steps:
 Install the LocalStack CLI (and maybe also awslocal). Make sure your LocalStack docker image is up-to-date by pulling the latest version. Use the LocalStack CLI to start LocalStack. Make sure to use the -d flag to start the LocalStack docker container in detached mode.</description></item><item><title>Cloud pods - Team Collaboration</title><link>/academy/localstack-deployment/cloud-pods/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/academy/localstack-deployment/cloud-pods/</guid><description>LocalStack is an ephemeral environment by nature. It means that when you stop your LocalStack instance, all data is removed. However, by using Cloud Pods, you can preserve the LocalStack state. Cloud Pods are snapshots of your LocalStack instance&amp;rsquo;s state that can be saved, versioned, shared, and restored.
-In this video, we&amp;rsquo;ll follow the quickstart to import Cloud Pods shared by our team member into our LocalStack instance and observe how this process supports local development and deployment of cloud applications.</description></item><item><title>Creating ephemeral application previews with LocalStack and GitHub Actions</title><link>/tutorials/ephemeral-application-previews/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/tutorials/ephemeral-application-previews/</guid><description>Introduction LocalStack&amp;rsquo;s core cloud emulator allows you set up your cloud infrastructure on your local machine. You can access databases, queues, and other managed services without needing to connect to a remote cloud provider. This speeds up your Software Development Life Cycle (SDLC) by making development and testing more efficient. Despite this, you still need a staging environment to do final acceptance tests before deploying your application to production.
-In many cases, staging environments are costly and deploying changes to them takes a lot of time.</description></item><item><title>LocalStack Desktop</title><link>/user-guide/tools/localstack-desktop/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/localstack-desktop/</guid><description>LocalStack Desktop is a desktop client that allows users to easily control and interact with their LocalStack instance. Using LocalStack Desktop, users can start and stop their LocalStack instance with a single click, create a new container, view logs, interact with LocalStack container via cli and use our resource browser.
+In this video, we&amp;rsquo;ll follow the quickstart to import Cloud Pods shared by our team member into our LocalStack instance and observe how this process supports local development and deployment of cloud applications.</description></item><item><title>Creating ephemeral application previews with LocalStack and GitHub Actions</title><link>/tutorials/ephemeral-application-previews/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/tutorials/ephemeral-application-previews/</guid><description>Introduction LocalStack&amp;rsquo;s core cloud emulator allows you to set up your cloud infrastructure on your local machine. You can access databases, queues, and other managed services without needing to connect to a remote cloud provider. This speeds up your Software Development Life Cycle (SDLC) by making development and testing more efficient. Despite this, you still need a staging environment to do final acceptance tests before deploying your application to production.</description></item><item><title>LocalStack Desktop</title><link>/user-guide/tools/localstack-desktop/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/localstack-desktop/</guid><description>LocalStack Desktop is a desktop client that allows users to easily control and interact with their LocalStack instance. Using LocalStack Desktop, users can start and stop their LocalStack instance with a single click, create a new container, view logs, interact with LocalStack container via cli and use our resource browser.
 Note LocalStack Desktop replaces the previous LocalStack Cockpit application. Cockpit isn&amp;rsquo;t available or maintained anymore and we recommend you to use LocalStack Desktop instead.</description></item><item><title>LocalStack Docker Extension</title><link>/user-guide/tools/localstack-docker-extension/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/localstack-docker-extension/</guid><description>Introduction The LocalStack Extension for Docker Desktop enables developers working with LocalStack to operate their LocalStack container via Docker Desktop, including checking service status, container logs, and configuring profiles. To install the LocalStack Extension for Docker Desktop, you need to have Docker Desktop installed on your machine.
 Installation To utilize LocalStack&amp;rsquo;s Docker Extension, it is necessary to have a recent version of Docker Desktop (v4.8 or higher) installed on the local machine.</description></item><item><title>Accounts</title><link>/user-guide/web-application/accounts/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/web-application/accounts/</guid><description>A LocalStack account is required to access features in the web app, and to access any of our paid offerings.
 Creating an Account Visit app.localstack.cloud/sign-up to create a user account for LocalStack. You can sign up with your email address or one of our supported social identity providers (such as GitHub).