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.

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

Updates to the "Docker On AWS" section #394

Open
thomastuong1231 opened this issue May 23, 2024 · 0 comments
Open

Updates to the "Docker On AWS" section #394

thomastuong1231 opened this issue May 23, 2024 · 0 comments
Assignees
Labels

Comments

@thomastuong1231
Copy link

As described in issues 377, 376, and 374, there is some missing info on how to get the AWS Elastic Beanstalk environment up and running. As noted in issue 374, there were security changes in AWS that forces you to create an instance profile because it no longer makes one automatically. To create the instance profile, you can follow the following link that was provided in issue 374 on how to create the needed profile:

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/iam-instanceprofile.html#iam-instanceprofile-addperms

The instance profile will need to be selected in step 2, "Service Access" section when creating the environment.

Another issue to look out for is noted in issue 376 in which you will need to choose the arm64 architecture and not the default x86 architecture. This option can be found in Step 4, "Configure instance traffic and scaling",
Screenshot 2024-05-23 at 1 59 08 PM

Although these issues have been spoken of in earlier issues, I just wanted to give a heads up since it seems those issues haven't been addressed in the actual tutorial and wanted to give a heads up since it was something I ran into.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants