Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove EC2 local daemon #897

Merged
merged 2 commits into from
Nov 8, 2023
Merged

Remove EC2 local daemon #897

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5718fde
Remove EC2 local daemon
viren-nadkarni Nov 8, 2023
9f84ff7
Highlight important notes in alert boxes
viren-nadkarni Nov 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 10 additions & 24 deletions content/en/user-guide/aws/elastic-compute-cloud/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,8 +217,10 @@ Such Docker-backed AMIs bear the resource tag `ec2_vm_manager:docker` and can be
$ awslocal ec2 describe-images --filters Name=tag:ec2_vm_manager,Values=docker
{{< /command >}}

It's important to note that all other AMIs are mocked and originate from the community edition of LocalStack.
{{< alert title="Note" >}}
All other AMIs that do not have the above tag are mocked and originate from the community edition of LocalStack.
Attempting to launch Dockerized instances using these specific AMIs will result in an `InvalidAMIID.NotFound` error.
{{< /alert >}}

### Configuration

Expand All @@ -228,35 +230,19 @@ Keep in mind that these modifications apply to all instances launched within the

## Networking

{{< alert title="Note" >}}
LocalStack daemon is deprecated and will be removed in an upcoming major release.
{{< /alert >}}

LocalStack allocates distinct private IP addresses to Dockerized instances.
To make use of this feature, it's essential to run the LocalStack daemon process on the host.
This daemon process is responsible for handling the creation and administration of networking on the host system.

Before using this command, ensure you've logged in to your `localstack` CLI (using `localstack login`) via your LocalStack Web Application credentials.
To confirm, execute `localstack --help` and check if `daemons` is among the available commands.

{{< command >}}
$ pip install localstack[runtime]
$ export LOCALSTACK_API_KEY=...
$ localstack daemons start
{{< /command >}}

The SSH access address for the instance is displayed in the logs during the instance initialization process.:
Network addresses for Dockerized instances are allocated by the Docker daemon.
These addresses are printed in the logs while the instance is being initialized.

```bash
2022-03-21T14:46:49.540 INFO Instance i-1d6327abf04e31be6 will be accessible via SSH at: 127.0.0.1:55705, 172.17.0.4:22
2022-03-21T14:46:49.540 INFO Instance i-1d6327abf04e31be6 will be accessible via SSH at: 127.0.0.1:55705
```

The LocalStack daemon is supported on Linux and macOS operating systems.
If the LocalStack daemon is inactive, the instance can only be accessed at `127.0.0.1` along with an available port on the host.
To be able to access the instance at additional ports from the host system, you can modify the default security group and incorporate the needed ingress ports.

To make additional ports available to the host system, you can modify the default security group and incorporate the needed ingress ports.
It's important to note that security group ingress rules are applied only during the creation of the Dockerized instance.
{{< alert title="Note" >}}
Security group ingress rules are applied only during the creation of the Dockerized instance.
Modifying a security group will not open any ports for a running instance.
{{< /alert >}}

The system supports up to 32 ingress ports.
This constraint is in place to prevent the host from exhausting available ports.
Expand Down