CORS on AWS Elastic beanstalk











up vote
0
down vote

favorite
1












I'm new to AWS and used





  • Elastic beanstalk to deploy my rest API (api.example.com) in node

  • and S3 bucket with cloudfront for my static website (example.com) in React.





When calling the API endpoints from website, the browser is giving the CORS error. How can i prevent that?



I'm using following code in the node project for CORS



app.use((req, res, next) => {

  res.header('Access-Control-Allow-Origin', '*')

  res.header('Access-Control-Allow-Credentials', true)

  res.header('Access-Control-Allow-Methods', 'POST, GET, OPTIONS')

  res.header('Access-Control-Allow-Headers', 'Origin, X-Requested-With, Content-Type, Accept')

  next();

});






Edit - based on arudzinska's comment



I also configured CORS in the bucket



<?xml version="1.0" encoding="UTF-8"?>

<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">

<CORSRule>

    <AllowedOrigin>*</AllowedOrigin>

    <AllowedMethod>GET</AllowedMethod>

    <AllowedMethod>POST</AllowedMethod>

</CORSRule>

</CORSConfiguration>



and the server is on nginx







Thanks in advance for any help








P.S - also, i have seen that few posts gives the reason as there would be some bug in the project code but all the endpoints are working correctly on POSTMAN.







amazon-web-services nginx cors amazon-elastic-beanstalk







share|improve this question
























  • Did you configure CORS also on your bucket?
    – arudzinska
    9 hours ago










  • yes i did that in the bucket, please see the updated question
    – Aman
    8 hours ago

















up vote
0
down vote

favorite
1












I'm new to AWS and used





  • Elastic beanstalk to deploy my rest API (api.example.com) in node

  • and S3 bucket with cloudfront for my static website (example.com) in React.





When calling the API endpoints from website, the browser is giving the CORS error. How can i prevent that?



I'm using following code in the node project for CORS



app.use((req, res, next) => {

  res.header('Access-Control-Allow-Origin', '*')

  res.header('Access-Control-Allow-Credentials', true)

  res.header('Access-Control-Allow-Methods', 'POST, GET, OPTIONS')

  res.header('Access-Control-Allow-Headers', 'Origin, X-Requested-With, Content-Type, Accept')

  next();

});






Edit - based on arudzinska's comment



I also configured CORS in the bucket



<?xml version="1.0" encoding="UTF-8"?>

<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">

<CORSRule>

    <AllowedOrigin>*</AllowedOrigin>

    <AllowedMethod>GET</AllowedMethod>

    <AllowedMethod>POST</AllowedMethod>

</CORSRule>

</CORSConfiguration>



and the server is on nginx







Thanks in advance for any help








P.S - also, i have seen that few posts gives the reason as there would be some bug in the project code but all the endpoints are working correctly on POSTMAN.







amazon-web-services nginx cors amazon-elastic-beanstalk







share|improve this question
























  • Did you configure CORS also on your bucket?
    – arudzinska
    9 hours ago










  • yes i did that in the bucket, please see the updated question
    – Aman
    8 hours ago















up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I'm new to AWS and used





  • Elastic beanstalk to deploy my rest API (api.example.com) in node

  • and S3 bucket with cloudfront for my static website (example.com) in React.





When calling the API endpoints from website, the browser is giving the CORS error. How can i prevent that?



I'm using following code in the node project for CORS



app.use((req, res, next) => {

  res.header('Access-Control-Allow-Origin', '*')

  res.header('Access-Control-Allow-Credentials', true)

  res.header('Access-Control-Allow-Methods', 'POST, GET, OPTIONS')

  res.header('Access-Control-Allow-Headers', 'Origin, X-Requested-With, Content-Type, Accept')

  next();

});






Edit - based on arudzinska's comment



I also configured CORS in the bucket



<?xml version="1.0" encoding="UTF-8"?>

<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">

<CORSRule>

    <AllowedOrigin>*</AllowedOrigin>

    <AllowedMethod>GET</AllowedMethod>

    <AllowedMethod>POST</AllowedMethod>

</CORSRule>

</CORSConfiguration>



and the server is on nginx







Thanks in advance for any help








P.S - also, i have seen that few posts gives the reason as there would be some bug in the project code but all the endpoints are working correctly on POSTMAN.







amazon-web-services nginx cors amazon-elastic-beanstalk







share|improve this question















I'm new to AWS and used





  • Elastic beanstalk to deploy my rest API (api.example.com) in node

  • and S3 bucket with cloudfront for my static website (example.com) in React.





When calling the API endpoints from website, the browser is giving the CORS error. How can i prevent that?



I'm using following code in the node project for CORS



app.use((req, res, next) => {

  res.header('Access-Control-Allow-Origin', '*')

  res.header('Access-Control-Allow-Credentials', true)

  res.header('Access-Control-Allow-Methods', 'POST, GET, OPTIONS')

  res.header('Access-Control-Allow-Headers', 'Origin, X-Requested-With, Content-Type, Accept')

  next();

});






Edit - based on arudzinska's comment



I also configured CORS in the bucket



<?xml version="1.0" encoding="UTF-8"?>

<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">

<CORSRule>

    <AllowedOrigin>*</AllowedOrigin>

    <AllowedMethod>GET</AllowedMethod>

    <AllowedMethod>POST</AllowedMethod>

</CORSRule>

</CORSConfiguration>



and the server is on nginx







Thanks in advance for any help








P.S - also, i have seen that few posts gives the reason as there would be some bug in the project code but all the endpoints are working correctly on POSTMAN.







amazon-web-services nginx cors amazon-elastic-beanstalk




amazon-web-services nginx cors amazon-elastic-beanstalk






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 8 hours ago

























asked 9 hours ago









Aman

3917




3917












  • Did you configure CORS also on your bucket?
    – arudzinska
    9 hours ago










  • yes i did that in the bucket, please see the updated question
    – Aman
    8 hours ago




















  • Did you configure CORS also on your bucket?
    – arudzinska
    9 hours ago










  • yes i did that in the bucket, please see the updated question
    – Aman
    8 hours ago


















Did you configure CORS also on your bucket?
– arudzinska
9 hours ago




Did you configure CORS also on your bucket?
– arudzinska
9 hours ago












yes i did that in the bucket, please see the updated question
– Aman
8 hours ago






yes i did that in the bucket, please see the updated question
– Aman
8 hours ago



















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371763%2fcors-on-aws-elastic-beanstalk%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371763%2fcors-on-aws-elastic-beanstalk%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

'app-layout' is not a known element: how to share Component with different Modules

Image
0 My application was working fine until I decided to go with lazy loading: So, my shared component looks like this: import { Component, Renderer2 } from '@angular/core'; export interface FormModel { captcha?: string; } @Component({ selector: 'app-layout', templateUrl: './app-layout.component.html', styleUrls: ['./app-layout.css'] }) export class FullLayoutComponent { } app-layout.component.ts I am using this component in my Another component say school-home.component.html like this: <app-layout> </app-layout> and it was working fine until I created a Module school-home.module.ts like this: import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { SchoolhomeRoutingModule ...
Read more

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d ...
Read more

WPF add header to Image with URL pettitions [duplicate]

Image
up vote 0 down vote favorite This question already has an answer here: Image source URI requiring authorization 3 answers Add header to all* HTTP requests on a machine 1 answer first of all sorry for my english. Recently I added some security in the backend of my project, and now I need to send a validation code(apiKey) inside the headers to retrieve the images. I have a problem with ALL images in my project that I had attached in my UI. For example, before I had: <Image Height="90" Source="{Binding Video.Thumbnail}"/> Now I need to change my code to create a CUSTOM petition add the apiKey in the header:...
Read more