deploy: 9e0b2eb

getting-started/index.xml

@@ -1,6 +1,6 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on Docs</title><link>/getting-started/</link><description>Recent content in Getting Started on Docs</description><generator>Hugo</generator><language>en</language><atom:link href="/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Installation</title><link>/getting-started/installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/installation/</guid><description>LocalStack CLI The quickest way get started with LocalStack is by using the LocalStack CLI. It allows you to start LocalStack from your command line. Please make sure that you have a working docker environment on your machine before moving on.
-The CLI starts and manages the LocalStack docker container. For alternative methods of managing the LocalStack container, see our alternative installation instructions.
-MacOS Linux Windows Other You can install the LocalStack CLI using Brew directly from our official LocalStack tap: $ brew install localstack/tap/localstack-cli Alternative: Binary Download Alternatively, you can download the respective binary for your architecture directly:</description></item><item><title>Auth Token</title><link>/getting-started/auth-token/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/auth-token/</guid><description>Introduction The Auth Token is a personal identifier used for user authentication outside the LocalStack Web Application, particularly in conjunction with the LocalStack core cloud emulator. Its primary functions are to retrieve the user&amp;rsquo;s license and enable access to advanced features, effectively replacing the older developer API keys.
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Getting Started on Docs</title><link>/getting-started/</link><description>Recent content in Getting Started on Docs</description><generator>Hugo</generator><language>en</language><atom:link href="/getting-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Installation</title><link>/getting-started/installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/installation/</guid><description>LocalStack CLI The quickest way get started with LocalStack is by using the LocalStack CLI. It allows you to start LocalStack from your command line. Please make sure that you have a working Docker installation on your machine before moving on.
+The CLI starts and manages the LocalStack Docker container. For alternative methods of managing the LocalStack container, see our alternative installation instructions.
+Linux MacOS Windows Other/Python You can download the pre-built binary for your architecture using the link below: x86-64&amp;nbsp;ARM64&amp;nbsp; or use the curl commands below: For x86-64: $ curl --output localstack-cli-3.</description></item><item><title>Auth Token</title><link>/getting-started/auth-token/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/auth-token/</guid><description>Introduction The Auth Token is a personal identifier used for user authentication outside the LocalStack Web Application, particularly in conjunction with the LocalStack core cloud emulator. Its primary functions are to retrieve the user&amp;rsquo;s license and enable access to advanced features, effectively replacing the older developer API keys.
 The Auth Token remains unchanged unless manually rotated by the user, regardless of any license assignment changes. You can locate your Auth Token on the Getting Started page or the Auth Token page in the LocalStack Web Application.</description></item><item><title>Quickstart</title><link>/getting-started/quickstart/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/quickstart/</guid><description>Introduction In this quickstart guide, we&amp;rsquo;ll walk you through the process of starting LocalStack on your local machine and deploying a serverless image resizer application that utilizes several AWS services. This guide aims to help you understand how to use LocalStack for the development and testing of your AWS applications locally. It introduces you to the following key concepts:
 Starting a LocalStack instance on your local machine. Deploying an AWS serverless application infrastructure locally.</description></item><item><title>Frequently Asked Questions</title><link>/getting-started/faq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/faq/</guid><description>LocalStack Core FAQs How to update my LocalStack CLI? If the LocalStack CLI version is heavily outdated, it might lead to issues with container startup and debug commands. If you are using an older version of LocalStack, you can update it by running the following command:
 $ pip install --upgrade localstack localstack-ext If you are running a newer version of LocalStack, you can check the version by running the following command:</description></item><item><title>Help &amp; Support</title><link>/getting-started/help-and-support/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/help-and-support/</guid><description>Introduction We strive to make it as easy as possible for you to use LocalStack, and we are very grateful for any feedback. We provide different levels of support to help you with your queries and issues. The support you receive depends on the plan you are on.

index.xml

@@ -75,9 +75,9 @@ Updating Account Info and Settings To update your account info, password and set
 These options can be passed to LocalStack as environment variables like so:
 $ DEBUG=1 localstack start To facilitate interoperability, configuration variables can be prefixed with LOCALSTACK_ in docker. For instance, setting LOCALSTACK_PERSISTENCE=1 is equivalent to PERSISTENCE=1.
 You can also use Profiles.
-Configurations marked as Deprecated will be removed in the next major version. You can find previously removed configuration variables under Legacy.</description></item><item><title>Installation</title><link>/getting-started/installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/installation/</guid><description>LocalStack CLI The quickest way get started with LocalStack is by using the LocalStack CLI. It allows you to start LocalStack from your command line. Please make sure that you have a working docker environment on your machine before moving on.
-The CLI starts and manages the LocalStack docker container. For alternative methods of managing the LocalStack container, see our alternative installation instructions.
-MacOS Linux Windows Other You can install the LocalStack CLI using Brew directly from our official LocalStack tap: $ brew install localstack/tap/localstack-cli Alternative: Binary Download Alternatively, you can download the respective binary for your architecture directly:</description></item><item><title>Transparent Endpoint Injection</title><link>/user-guide/tools/transparent-endpoint-injection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/transparent-endpoint-injection/</guid><description>LocalStack provides Transparent Endpoint Injection, which enables seamless connectivity to LocalStack without modifying your application code targeting AWS. The DNS Server resolves AWS domains such as *.amazonaws.com including subdomains to the LocalStack container. Therefore, your application seamlessly accesses the LocalStack APIs instead of the real AWS APIs. For local testing, you might need to disable SSL validation as explained under Self-signed certificates.
+Configurations marked as Deprecated will be removed in the next major version. You can find previously removed configuration variables under Legacy.</description></item><item><title>Installation</title><link>/getting-started/installation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/installation/</guid><description>LocalStack CLI The quickest way get started with LocalStack is by using the LocalStack CLI. It allows you to start LocalStack from your command line. Please make sure that you have a working Docker installation on your machine before moving on.
+The CLI starts and manages the LocalStack Docker container. For alternative methods of managing the LocalStack container, see our alternative installation instructions.
+Linux MacOS Windows Other/Python You can download the pre-built binary for your architecture using the link below: x86-64&amp;nbsp;ARM64&amp;nbsp; or use the curl commands below: For x86-64: $ curl --output localstack-cli-3.</description></item><item><title>Transparent Endpoint Injection</title><link>/user-guide/tools/transparent-endpoint-injection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/transparent-endpoint-injection/</guid><description>LocalStack provides Transparent Endpoint Injection, which enables seamless connectivity to LocalStack without modifying your application code targeting AWS. The DNS Server resolves AWS domains such as *.amazonaws.com including subdomains to the LocalStack container. Therefore, your application seamlessly accesses the LocalStack APIs instead of the real AWS APIs. For local testing, you might need to disable SSL validation as explained under Self-signed certificates.
 Motivation Previously, your application code targeting AWS needs to be modified to target LocalStack.</description></item><item><title>DNS Server</title><link>/user-guide/tools/dns-server/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/user-guide/tools/dns-server/</guid><description>LocalStack includes a DNS server that enables seamless connectivity to LocalStack from different environments using localhost.localstack.cloud. The DNS server is available on all IPv4 addresses within the LocalStack container (i.e., listening to 0.0.0.0) and resolves localhost.localstack.cloud to the LocalStack container. Therefore, containers that are configured to use the DNS server can reach LocalStack using localhost.localstack.cloud. This configuration happens automatically for containers created by LocalStack, including compute resources such as Lambda, ECS, and EC2.</description></item><item><title>Changelog</title><link>/references/changelog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/references/changelog/</guid><description>Introduction This page documents the release notes for official LocalStack major and minor releases since LocalStack v1.0.0. If you are looking for information about nightly releases, preview features, or experimental features, pull the latest Docker image. The changelog is updated with every release. Updates that affect only LocalStack Web Application or features in preview or limited release may not be reflected.
 Features under Development LocalStack uses the following terminology to communicate features under development:</description></item><item><title>IAM Coverage</title><link>/references/iam-coverage/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/references/iam-coverage/</guid><description>Supported Services In principle, LocalStack supports all operations. However, not all services and their operations have been tested yet. The table below lists all IAM services and operations that have been tested, noting if they were ever denied or allowed during testing. It only includes operations performed with a principal, not as root, so test setups are excluded.
 Name operation Access denied Access allowed acm ListCertificates Yes Yes apigateway DeleteRestApi No Yes apigateway CreateRestApi Yes Yes backup DescribeBackupVault Yes Yes batch CreateComputeEnvironment No Yes cloudformation ListStacks Yes Yes cloudwatch PutMetricData Yes Yes dynamodb DescribeTable No Yes dynamodb CreateTable Yes Yes dynamodb DeleteTable No Yes ecr DescribeImages Yes No efs DescribeFileSystems Yes Yes es DescribeElasticsearchDomains Yes Yes events DeleteEventBus No Yes events PutEvents Yes Yes events CreateEventBus Yes Yes kinesis CreateStream Yes Yes kinesis DeleteStream No Yes kms CreateKey Yes Yes kms DescribeKey Yes Yes lambda DeleteFunction No Yes lambda Invoke Yes Yes lambda GetLayerVersion Yes Yes lambda CreateFunction Yes Yes logs CreateLogGroup Yes Yes logs PutLogEvents No Yes logs CreateLogStream No Yes logs DeleteLogGroup No Yes redshift DescribeClusters Yes Yes redshift-data ListDatabases Yes Yes s3 UploadPart No Yes s3 GetObject Yes Yes s3 DeleteBucket No Yes s3 CreateBucket Yes Yes s3 ListBuckets Yes Yes s3 CreateMultipartUpload Yes Yes s3 CompleteMultipartUpload No Yes s3 DeleteObject No Yes s3 ListObjects Yes Yes s3 PutObject Yes Yes secretsmanager CreateSecret Yes Yes secretsmanager GetSecretValue Yes Yes secretsmanager DeleteSecret No Yes sns Publish No Yes sqs GetQueueAttributes Yes No sqs CreateQueue Yes Yes sqs SendMessage Yes Yes sqs ReceiveMessage Yes Yes sqs DeleteQueue No Yes stepfunctions DeleteStateMachine No Yes stepfunctions CreateStateMachine Yes Yes sts GetCallerIdentity No Yes Inter Service Enforcement Source Service Target Service Feature Operation Implemented Tested sns sqs SNS subscription sqs.</description></item><item><title>End-to-End Testing in Gitlab CI with Testcontainers and LocalStack: Understanding Runners and Docker in Docker</title><link>/tutorials/gitlab_ci_testcontainers/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/tutorials/gitlab_ci_testcontainers/</guid><description>Introduction: Testcontainers &amp;amp; LocalStack Testcontainers is an open-source framework that provides lightweight APIs for bootstrapping local development and test dependencies with real services wrapped in Docker containers. Running tests with Testcontainers and LocalStack is crucial for AWS-powered applications because it ensures each test runs in a clean, isolated environment, providing consistency across all development and CI machines. LocalStack avoids AWS costs by emulating services locally, preventing exceeding AWS free tier limits, and eliminates reliance on potentially unstable external AWS services.</description></item><item><title>Auth Token</title><link>/getting-started/auth-token/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/getting-started/auth-token/</guid><description>Introduction The Auth Token is a personal identifier used for user authentication outside the LocalStack Web Application, particularly in conjunction with the LocalStack core cloud emulator. Its primary functions are to retrieve the user&amp;rsquo;s license and enable access to advanced features, effectively replacing the older developer API keys.