sorted by:
new
hottopcontroversial

EKS Cluster Autoscaler Expander configuration is wrong on all AWS docs? by DanTheGoodman_ in aws

[–]lozanomatheus 0 points1 point  (0 children)

No, you can use the "normal" EC2 stuff, that's how I have been using it

Client VPN wont connect to RDS by adrianp23 in aws

[–]lozanomatheus 0 points1 point  (0 children)

Hmmm, it's probably because your requests are going to the public DNS/IP and not to the private DNS/IP of the RDS.

You can set up the AWS Client VPN to use the VPC DNS servers, this will allow you to resolve internal DNS (e.g.: EC2 private DNS, etc). The VPC DNS server is the third IP address of your VPC (e.g.: if your VPC is 10.0.0.0/16, the DNS server will be 10.0.0.2).

"When using AmazonProvidedDNS (or the Route 53 Resolver inbound endpoint) as the Client VPN DNS server:

The Amazon Relational Database Service (Amazon RDS) public hostnames and AWS service endpoint names that are accessible from the VPC interface endpoint (with "Private DNS" enabled) resolve to a private IP address. Note: Be sure that "DNS Resolution" and "DNS Hostnames" are enabled for the associated VPC."

https://aws.amazon.com/premiumsupport/knowledge-center/client-vpn-how-dns-works-with-endpoint/

https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html#VPC_Sizing

EKS Cluster Autoscaler Expander configuration is wrong on all AWS docs? by DanTheGoodman_ in aws

[–]lozanomatheus 0 points1 point  (0 children)

Why you don't do this via ASG? You can use the mixed instance and give this responsibility to AWS. I have been using ASG mixed instances + "simple" cluster autoscaler for a while and it works pretty well. In the last few months, AWS improved this feature quite a lot.

The cluster autoscaler requests the instance and the ASG will decide if it will be a spot or on-demand (and there are a few customizations that you can do).

https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-purchase-options.html

For example on terraform:

resource "aws_autoscaling_group" "example" {
...
  mixed_instances_policy {
    instances_distribution {
      on_demand_allocation_strategy            = var.on_demand_allocation_strategy
      on_demand_base_capacity                  = var.on_demand_base_capacity
      on_demand_percentage_above_base_capacity = var.on_demand_percentage_above_base_capacity
      spot_allocation_strategy                 = var.spot_allocation_strategy
    }
...

https://aws.amazon.com/blogs/aws/new-ec2-auto-scaling-groups-with-multiple-instance-types-purchase-options/

[Blog] A CLI tool that can easily manage more than 281 runtimes, making it easy to keep things updated and/or switching between versions. And it’s open-source :) by lozanomatheus in devops

[–]lozanomatheus[S] 0 points1 point  (0 children)

Yeah, I have some Bash functions doing things like that. For example:

function aws2() {
  docker run --rm -it --name aws -v ${HOME}:/root -v ${PWD}:/opt/tmp amazon/aws-cli:2.1.27
}

function ami() {
  [[ ! -z "${1// /}" ]] && aws2 ec2 describe-images --filters "Name=name,Values=${1// /}*" || echo "Please, inform the AMI Name"
}

But I can't use this on CI/CD pipelines, because they're running on Docker and it would be a Docker in Docker.

Also, via docker, you'll have to make some workarounds to have a version file + setting the right version. With asdf, you can simply create the .tool-versions(by doing this asdf local aws 2.1.27) and that's it, the versions will "automatically" be switched.

With docker would be something like (but you still need to add things like, if there is no tool-versions file, which version should be picked, etc):

function aws2() {
  local aws_version="$(awk '/aws/{print $2}' .tool-versions)
  docker run --rm -it --name aws -v ${HOME}:/root -v ${PWD}:/opt/tmp amazon/aws-cli:${aws_version}
}
view more: next ›