#elasticbeanstalk — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #elasticbeanstalk, aggregated by home.social.
-
#AWS #AppRunner - цікав інтеграція #GitHub, яка дозволяє за 5 хвилин налаштувати збірку та деплой додатків в клауд.
Це PaaS схожий на #ElasticBeanstalk, але з інтеграцією з гітом, коли збірка та деплой проходять автоматично при пуше в гілку.
Саме то, що треба для розробників для свої пет проєктів, або для створення #MVP стартапами.
https://github.com/marketplace/aws-connector-for-github -
Yes! Elastic Beanstalk finally supports Ruby 3.3. Yet another day I can procrastinate on migrating to a Docker workflow for this collection of apps. 😅
-
Yes! Elastic Beanstalk finally supports Ruby 3.3. Yet another day I can procrastinate on migrating to a Docker workflow for this collection of apps. 😅
-
Учора майже весь день витратив на дебаг #AWS #ElasticBeanstalk #nodejs додатка. Розробники, леніві дупи, досі використовують ноду 8 (OMG), в той час, як платформа підтримує мінімально 14+. Тож доводиться на #AmazonLinux ставити nodejs 8 через скрипт nodesource. Проблема зʼявилась нещодавно - скрипт перестав працювати.
Викрутився тим, що з робочого сервера підкинув файли
/etc/yum.repos.d/nodesource-el7.repo та #GPG ключ до нього.
Поки працює, але обматюкав девов та сказав, щоб оновлювали код -
I tried manually deleting the IPs, which works, as long as you don't want to change anything ever again. It seems like #ElasticBeanstalk stores the IP address internally somewhere, so when you try to deploy new versions of the app or make any config changes, it just errs out complaining that it can't find the old IP address. I think it tries to move the IP address across instances and then fails when it can’t.
-
I tried manually deleting the IPs, which works, as long as you don't want to change anything ever again. It seems like #ElasticBeanstalk stores the IP address internally somewhere, so when you try to deploy new versions of the app or make any config changes, it just errs out complaining that it can't find the old IP address. I think it tries to move the IP address across instances and then fails when it can’t.
-
Well this is infuriating 😡, apparently #ElasticBeanstalk Single-Instance Envs are forced to have an Elastic IP even if they are in a private subnet (which means the assigned public ip is useless).
In February, #AWS is going to start charing for ALL EIPs, not just unassigned ones, so unless they update Elastic Beanstalk before then to no longer require the EIPs, it’s just more money out the window.
-
Well this is infuriating 😡, apparently #ElasticBeanstalk Single-Instance Envs are forced to have an Elastic IP even if they are in a private subnet (which means the assigned public ip is useless).
In February, #AWS is going to start charing for ALL EIPs, not just unassigned ones, so unless they update Elastic Beanstalk before then to no longer require the EIPs, it’s just more money out the window.
-
Success! I wonder if I'm the first person to get a #Ruby 3.2 app running on #ElasticBeanstalk Amazon Linux 2023? Surely not, right?
The biggest difference for me was that AL2023 seems to no longer user rbenv for Ruby, the platform just has it installed. I had modify my platform hook that copies the Amazon .rbenv version into my app’s root dir to only do it if the file exists (so I could get that app version deployed on a Ruby 3.0 instance before doing the instance upgrade)
-
Success! I wonder if I'm the first person to get a #Ruby 3.2 app running on #ElasticBeanstalk Amazon Linux 2023? Surely not, right?
The biggest difference for me was that AL2023 seems to no longer user rbenv for Ruby, the platform just has it installed. I had modify my platform hook that copies the Amazon .rbenv version into my app’s root dir to only do it if the file exists (so I could get that app version deployed on a Ruby 3.0 instance before doing the instance upgrade)
-
Apparently #ElasticBeanstalk skipped #Ruby 3.1 and went straight to 3.2 and they also updated to Amazon Linux 2023
https://docs.aws.amazon.com/elasticbeanstalk/latest/relnotes/release-2023-10-19-al2023.html
-
Apparently #ElasticBeanstalk skipped #Ruby 3.1 and went straight to 3.2 and they also updated to Amazon Linux 2023
https://docs.aws.amazon.com/elasticbeanstalk/latest/relnotes/release-2023-10-19-al2023.html
-
Is anyone deploying #Ruby 3.1 or 3.2 apps to #AWS #ElasticBeanstalk? There seems to be no official platform support yet, and I’m not hopeful that it’s coming soon.
https://github.com/aws/elastic-beanstalk-roadmap/issues/232
So what’s the best way to do this now? Is docker the only way to use these latest Ruby versions, and if so, does it make more sense to use ECS instead of Elastic Beanstalk?
-
Is anyone deploying #Ruby 3.1 or 3.2 apps to #AWS #ElasticBeanstalk? There seems to be no official platform support yet, and I’m not hopeful that it’s coming soon.
https://github.com/aws/elastic-beanstalk-roadmap/issues/232
So what’s the best way to do this now? Is docker the only way to use these latest Ruby versions, and if so, does it make more sense to use ECS instead of Elastic Beanstalk?