Skip to content
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions hazelcast-integration/aws-autoscaling/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ As the next step we need to create AWS image which will be used for the Autoscal
unzip hazelcast.zip && rm -f hazelcast.zip
wget https://raw.githubusercontent.com/hazelcast/hazelcast-code-samples/master/hazelcast-integration/aws-autoscaling/hazelcast.yaml

4. Update Hazelcast configuration `/opt/hazelcast/hazlecast.yaml` with `YOUR_AWS_ACCESS_KEY` and `YOUR_AWS_SECRET_KEY` (alternatively you can assign the needed IAM Role to the EC2 Instance)
4. Update Hazelcast configuration `/opt/hazelcast/hazelcast.yaml` with `YOUR_AWS_ACCESS_KEY` and `YOUR_AWS_SECRET_KEY` (alternatively you can assign the needed IAM Role to the EC2 Instance)
5. Download [lifecycle_hook_listener.sh](lifecycle_hook_listener.sh)

sudo apt install -y jq
Expand Down Expand Up @@ -152,4 +152,4 @@ Such solution may work correctly, however is definitely not recommended for the

* [AWS Auto Scaling documentation](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html) does not specify the instance termination process, so you can’t rely on anything
* [Some sources](https://stackoverflow.com/questions/11208869/amazon-ec2-autoscaling-down-with-graceful-shutdown) specify that it’s possible to gracefully shut down the processes, however after 20 seconds AWS can kill them anyway
* The [Amazon’s recommended way](https://docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html) to deal with graceful shutdowns is to use Lifecycle Hooks
* The [Amazon’s recommended way](https://docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html) to deal with graceful shutdowns is to use Lifecycle Hooks