As a DevOps person, I would like this app to support using instance profiles for determining IAM permissions, rather than explicit IAM Role and dynamic and/or static credentials.
I think maybe the app should support both methods, so developers can continue to use Access Keys. But the deployed env should use the instance profile.
Right now the App will not start without the two access key vars populated.
compose-app-1 | Traceback (most recent call last):
compose-app-1 | File "/src/manage.py", line 12, in <module>
compose-app-1 | execute_from_command_line(sys.argv)
compose-app-1 | File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
compose-app-1 | utility.execute()
compose-app-1 | File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 357, in execute
compose-app-1 | django.setup()
compose-app-1 | File "/usr/local/lib/python3.9/site-packages/django/__init__.py", line 24, in setup
compose-app-1 | apps.populate(settings.INSTALLED_APPS)
compose-app-1 | File "/usr/local/lib/python3.9/site-packages/django/apps/registry.py", line 122, in populate
compose-app-1 | app_config.ready()
compose-app-1 | File "/src/ui/apps.py", line 29, in ready
compose-app-1 | raise ImproperlyConfigured(
compose-app-1 | django.core.exceptions.ImproperlyConfigured: The following settings are missing: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
Designs and Mockups
Acceptance Criteria:
Out of Scope
As a DevOps person, I would like this app to support using instance profiles for determining IAM permissions, rather than explicit IAM Role and dynamic and/or static credentials.
I think maybe the app should support both methods, so developers can continue to use Access Keys. But the deployed env should use the instance profile.
Right now the App will not start without the two access key vars populated.
Designs and Mockups
Acceptance Criteria:
Out of Scope