If the environment has already been setup, you can skip to Send data
Follow these instructions to start your staged development environment.
See the serverless guide on setting up your credentials.
To get an account at the project's AWS namespace, please contact a PM to have an account created for you. You cannot use other AWS accounts created for other projects if you have such.
When you receive your initial credentials for your account related to the project, please do not forget to change your password and enable a MFA following the best practices.
Given you have access to the project's namespace in AWS, bear in mind the following regarding your account:
- We use a shared AWS account with several users. Each user has his own stage variable to separate his work.
- Create an access key for your account to be able to use it programatically.
- Get also your private key, it comes hand in hand with your personal id.
By the end of the process of organizing your account at AWS, you must come up with 2 environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY for managing sessions programatically.
In your terminal application, write the following:
export AWS_ACCESS_KEY_ID=<your_access_key>export AWS_SECRET_ACCESS_KEY=<your_secret_key>
For more information about access key setup, see this serverless guide
Follow these instructions to deploy a project under your name and stage.
Open the demo dashboard: http://eubfr-<your_stage_name>-demo-<producer_name>-dashboard.s3-website.eu-central-1.amazonaws.com/.
This page is a demo of what a producer dashboard could provide. From there, upload a test file (CSV, XLS). Then, hit the "Refresh" button to see if your file appears in the meta index.
Now if you want to see the results of the ETL, you can check http://eubfr-<your_stage_name>-demo-website.s3-website.eu-central-1.amazonaws.com/. This page lists all the projects for the current stage name.