- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi there,
The ".amzn1" identifier in the version strings that yum is reporting back indicates that you've deployed an EC2 instance using our previous generation Amazon Linux AMI (https://aws.amazon.com/amazon-linux-ami/) which has now reached its end-of-life, while the walkthrough you're referring to is specific to Amazon Linux 2 (https://aws.amazon.com/amazon-linux-2/) instances only.
You'll need to terminate your EB environment and recreate a new one.
Make sure that the new platform you deploy is using a 2.0.* AMI and not one versioned 2018.03.
https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html
I hope you find this advice helpful, otherwise please get in touch with Premium Support for further assistance.
https://aws.amazon.com/premiumsupport/
Regards,
Andrew
Furthermore, if you're using an Elastic Load Balancer in your Elastic Beanstalk environment, you can actually request and deploy a free SSL certificate to it using the AWS Certificate Manager (https://aws.amazon.com/certificate-manager/) instead of going through the extra effort of setting up Let's Encrypt to run within your EC2 instance.
I've considered that, but the extra cost of running the LB seems a bit prohibitive, thanks though!
Contenus pertinents
- demandé il y a un an
- demandé il y a 7 mois
- Réponse acceptéedemandé il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans